diff --git a/protocol/controller-actions.md b/protocol/controller-actions.md deleted file mode 100644 index 7d501944..00000000 --- a/protocol/controller-actions.md +++ /dev/null @@ -1,124 +0,0 @@ -# Controller Actions - -This is the legacy/manual controller discipline from the first external-state -prototype. The live fork now has typed Codex/app-server surfaces, but these -rules are still useful when maintaining repo-local state files by hand. - -The controller chooses exactly one primary action per step. This is meant to reduce the classic failure mode where the model is "thinking", rewriting the plan, editing files, and rationalizing the edits all at once. - -## Actions - -### `update_map` - -Purpose: -Write stable understanding into `state/map.yaml`. - -Allowed writes: -- objectives -- constraints -- invariants -- accepted design -- rejected paths -- current status - -Rules: -- Do not copy raw scratch into the map. -- Do not write guesses as settled architecture. -- If the map changes, say why. - -### `think_subgoal` - -Purpose: -Use `state/scratch.md` for one bounded problem only. - -Allowed writes: -- temporary decomposition -- open questions -- candidate checks -- local reasoning that may be wrong - -Rules: -- Scope it to one subgoal. -- Prefer deletion or summarization over accumulation. -- Scratch is disposable by design. - -### `propose_patch` - -Purpose: -Make one bounded code or document change tied to a clear hypothesis. - -Allowed writes: -- workspace files -- `state/branches.json` - -Rules: -- Name the hypothesis. -- Keep the patch narrow enough to verify. -- Do not silently redefine the map through code. - -### `run_verify` - -Purpose: -Check whether the proposed change actually improved the thing we care about. - -Allowed writes: -- distilled records in `state/evidence.jsonl` -- `state/branches.json` - -Checks may include: -- tests -- lints -- benchmark deltas -- invariant checks -- coherence review against `state/map.yaml` -- simplicity review - -### `compare_branches` - -Purpose: -Choose between competing changes or kill all of them. - -Allowed writes: -- `state/branches.json` -- distilled records in `state/evidence.jsonl` - -Rules: -- Prefer the smallest branch that clearly satisfies the objective. -- If two branches both feel dubious, reject both. - -### `backtrack` - -Purpose: -Abandon a bad line of attack instead of decorating it further. - -Allowed writes: -- `state/branches.json` -- distilled records in `state/evidence.jsonl` -- `state/map.yaml` - -Rules: -- Record why the branch was rejected. -- Preserve lessons that belong in the map. -- Do not record routine command inventories or "I just did this" proof as live evidence. -- Do not keep dead machinery out of sentiment. - -### `speak` - -Purpose: -Produce user-visible output. - -Rules: -- Speak after verification when possible. -- If speaking before verification, be explicit that the result is provisional. - -## Promotion Rule - -Information moves from scratch to map only if it survives verification, comparison, or repeated re-use without contradiction. - -## Stop Conditions - -Stop implementation and switch back to diagnosis when: -- the diff is growing and understanding is shrinking -- tests are green but the map and code disagree -- the agent cannot explain the data flow stage by stage -- new abstraction is compensating for confusion instead of reducing it diff --git a/state/scratch-compaction-17cd64d8-da88-4642-a871-4cf1b768c20a.md b/state/scratch-compaction-17cd64d8-da88-4642-a871-4cf1b768c20a.md deleted file mode 100644 index 8ceedcf0..00000000 --- a/state/scratch-compaction-17cd64d8-da88-4642-a871-4cf1b768c20a.md +++ /dev/null @@ -1,51 +0,0 @@ -# Scratch Compaction - -Hot context, written immediately from memory before inspection. - -Current user request before compaction: user asked to inspect adjacent pseudo-Epiphany repos and produce a self-contained prompt for a sandboxed sub-agent to convert/distill their persisted pseudo-Epiphany state into True-Epiphany typed role memory. - -What was done: -- Rehydrated EpiphanyAgent state/status. -- Scanned E:\Projects for adjacent AGENTS/state/memory/evidence/handoff surfaces. -- Identified primary pseudo-Epiphany state repos: - - E:\Projects\EpiphanyAquarium - - E:\Projects\Ghostlight - - E:\Projects\Heimdall - - E:\Projects\LunaMosaic - - E:\Projects\repixelizer - - E:\Projects\StreamPixels - - E:\Projects\Eusocial Interbeing - - E:\Projects\VibeGeometry - - E:\Projects\VoidBot -- Identified secondary AGENTS-only/lower-confidence doctrine sources: - - E:\Projects\AetheriaLore - - E:\Projects\Bifrost - - E:\Projects\CultLib - - E:\Projects\GameCult-Quartz - - E:\Projects\gamecult-ops - - E:\Projects\gamecult-site -- Read/sampled each primary repo's AGENTS/map/evidence/handoff/scratch where present and secondary AGENTS files. -- Inspected EpiphanyAgent's Ghostlight role memory schema and patch validator: - - state/agents/README.md - - state/agents/modeling.agent-state.json - - native epiphany-agent-memory-store binary -- Added new documentation file: - - notes/true-epiphany-memory-migration-sandbox-prompt.md - -Important content of the new prompt: -- It is a self-contained sandbox-agent prompt. -- It instructs the sandbox agent to produce reviewable migration artifacts under `.epiphany-imports/pseudo-repo-memory-migration-`. -- It explicitly forbids direct mutation by default. -- It maps adjacent repo lessons into role-specific memory targets for Self, Persona, Imagination, Eyes, Modeling, Hands, Soul, and Life. -- It requires source-inventory.json, distillation-report.md, role-selfpatches/*.json, review-results.json, and apply-plan.md. -- It requires each proposed memory patch to validate via native epiphany-agent-memory-store review-patch. -- It emphasizes project truth versus role memory separation. - -Potential remaining work after compaction: -1. Inspect git status. -2. Review the new prompt doc quickly for obvious typos or missing requirements. -3. Optionally run no code tests; this is docs-only, but maybe run `git diff --check` if desired. -4. Update state/map.yaml or evidence only if this prompt becomes durable enough to record. A short evidence entry may be justified. -5. Commit and push the documentation pass unless user says not to. - -No commit has been made yet for the prompt doc as of this scratch note.