Add two non-overlapping Hackmode Auto-RAGE development workers #136

Closed
nsaspy wants to merge 7 commits from feature/30-auto-rage-profiles into master
Owner

Outcome

Continues #30 after the RAGE scope substrate merged in #36.

This moves the live Agent Zero autonomous-development worker profiles into Hackmode and gives the initial two workers disjoint ownership so they can run concurrently without grabbing the same subsystem.

hackmode-rage-database

Owns Hackmode database / execution-graph / KB persistence work:

  • typed execution graph persistence;
  • operation-scoped provenance;
  • operational and long-term KB storage;
  • global KB export/looting plumbing;
  • persistence/replay/conflict-safe multi-worker semantics.

hackmode-rage-hackpert

Owns Hackpert / expert-engine work:

  • passive/active engine behavior;
  • typed active actions/state deltas;
  • provider orchestration;
  • plans/playbooks and expert rules;
  • LISH expert/run controls;
  • later Prolog-RLM and possible ZeroForge integration through the same loop.

No stepping on each other

Each profile has an explicit path/domain ownership fence. Shared manifest/package files are minimum-wiring only and require checking the sibling worker's open PR before editing. Cross-domain needs should become typed interface handoffs, not one worker absorbing the other's implementation area.

StarIntel boundary

These are Hackmode workers. Neither profile may use StarIntel issue queues as a product backlog or implement ordinary StarIntel features/refactors/runtime/UI/infrastructure/bugs.

StarIntel is permitted only for explicitly authorized cyber/BBP work: source-assisted security review, attack-surface/recon analysis, authorized testing, security integration validation, or security finding/evidence projection. Product defects found that way are handed off as security findings.

Recovery marker

README.org now records c64ae3f244c200a0e6fceaa28a9ebff1a8dfbdb4 as the known-good Auto-RAGE starting point. If autonomous work goes bad, branch/worktree from that reference and reconcile forward; never rewrite master.

Install

Adds agent-zero/install.sh and profile documentation.

Related: #24 #27 #28 #30

## Outcome Continues #30 after the RAGE scope substrate merged in #36. This moves the live Agent Zero autonomous-development worker profiles into Hackmode and gives the initial two workers disjoint ownership so they can run concurrently without grabbing the same subsystem. ### `hackmode-rage-database` Owns Hackmode database / execution-graph / KB persistence work: - typed execution graph persistence; - operation-scoped provenance; - operational and long-term KB storage; - global KB export/looting plumbing; - persistence/replay/conflict-safe multi-worker semantics. ### `hackmode-rage-hackpert` Owns Hackpert / expert-engine work: - passive/active engine behavior; - typed active actions/state deltas; - provider orchestration; - plans/playbooks and expert rules; - LISH expert/run controls; - later Prolog-RLM and possible ZeroForge integration through the same loop. ## No stepping on each other Each profile has an explicit path/domain ownership fence. Shared manifest/package files are minimum-wiring only and require checking the sibling worker's open PR before editing. Cross-domain needs should become typed interface handoffs, not one worker absorbing the other's implementation area. ## StarIntel boundary These are Hackmode workers. Neither profile may use StarIntel issue queues as a product backlog or implement ordinary StarIntel features/refactors/runtime/UI/infrastructure/bugs. StarIntel is permitted only for explicitly authorized cyber/BBP work: source-assisted security review, attack-surface/recon analysis, authorized testing, security integration validation, or security finding/evidence projection. Product defects found that way are handed off as security findings. ## Recovery marker `README.org` now records `c64ae3f244c200a0e6fceaa28a9ebff1a8dfbdb4` as the known-good Auto-RAGE starting point. If autonomous work goes bad, branch/worktree from that reference and reconcile forward; never rewrite master. ## Install Adds `agent-zero/install.sh` and profile documentation. Related: #24 #27 #28 #30
nsaspy closed this pull request 2026-09-04 20:50:21 +00:00
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 1s
core / common-lisp-core (pull_request) Failing after 46s
monorepo / hygiene (pull_request) Successful in 4m15s

Pull request closed

Sign in to join this conversation.
No description provided.