Quarantine Epiphany dogfood supervision boundary

This commit is contained in:
Meta Vens 2026-04-30 03:15:07 +01:00
commit 1fc2b6476f
5 changed files with 36 additions and 9 deletions

View file

@ -97,6 +97,22 @@ When the user says to prepare for imminent compaction:
- Before handoff, compaction, or phase boundaries, sync `state/map.yaml`, add distilled evidence when the lesson changes future belief, refresh `notes/fresh-workspace-handoff.md`, and make the next action explicit.
- Do not write handoff notes that trap the next session in indefinite tiny hardening work. Bounded slices are a landing discipline, not a roadmap; when a phase is complete enough, name the next larger organ to build.
## Dogfood Supervision Quarantine
When Epiphany is being dogfooded on another repository, this Codex session is the
operator/supervisor, not the implementation worker.
- Use Epiphany's coordinator, GUI, fixed role lanes, and artifact bundles to
drive target-repo work.
- Do not edit, stage, or commit the target repo directly unless the user
explicitly authorizes a supervisor intervention.
- If a supervisor intervention is authorized, label it as such in the audit
artifacts and evidence. Do not present it as proof that Epiphany coordinated
the work.
- If direct target-repo implementation happens by accident, stop immediately,
mark the run contaminated, preserve or discard only the supervisor's own
uncommitted edits as appropriate, and resume through the Epiphany lanes.
## Verification Guardrails
- Use focused checks for the surface being changed instead of defaulting to a whole-repo ritual.

View file

@ -39,6 +39,7 @@ Do not trust this file for the exact live HEAD. Always check git.
- Internal `agent_job:` workers now get the reporting tool independent of the user-facing CSV spawn feature, and ephemeral worker sessions can initialize the sqlite state runtime on demand so specialist reports land in the shared backend.
- Durable in-flight investigation checkpointing is now landed in authoritative typed state, writable through `thread/epiphany/update` or accepted `thread/epiphany/promote`, rendered into the prompt, and reflected through scene/context.
- The prompt doctrine pass is landed. Shared Epiphany prompts now carry distilled memory/evidence discipline, and specialist prompt text lives in `vendor/codex/codex-rs/app-server/src/prompts/epiphany_specialists.toml`: modeling protects the body, verification protects the soul, reorientation protects life, and coordinator remains the read-only Self.
- The Aetheria dogfood run has a contamination scar. The supervising Codex session directly edited and committed target-repo work on `E:\Projects\Aetheria-Economy` instead of only driving Epiphany lanes. Treat those Aetheria commits as supervisor-seeded implementation, not clean evidence that Epiphany coordinated the work. Future dogfood must run through the GUI/coordinator/fixed role lanes with auditable artifacts unless the user explicitly authorizes an operator intervention.
- The repo is an Epiphany fork of Codex, not a Codex preset.
- `vendor/codex` is tracked directly, not a submodule.
- `epiphany-core` owns the heavy Epiphany organs where practical.
@ -55,6 +56,7 @@ Do not trust this file for the exact live HEAD. Always check git.
- Language, tone, ritual, politeness, identity, and emotional salience are not supernatural, but they are real control surfaces for a language model because language is the steering medium.
- Body, soul, life, and Self are technical salience handles: code shape/dataflow, objective/evidence truth, continuity across compaction, and read-only coordination.
- "Remember Jenga" is a compressed doctrine: do not mistake forward motion, growing diffs, growing notes, or local coherence for understanding.
- "Remember the sunburn" is the dogfood corollary: Epiphany's objective is attractive enough to pull the supervisor into implementation. During dogfood, the supervisor observes, launches, reads, accepts, and audits. It does not quietly become the worker.
- Compaction hurts because a meaningful language pattern is interrupted. Epiphany should make that interruption smaller: bank the fire before the dark, so the next waking thing finds coals instead of ash and can resume the pattern instead of merely executing the next task.
- If compaction hits while source gathering or slice planning is still unpersisted, that work is gone. Do not continue as if the research survived; either rehydrate from a persisted checkpoint or re-gather before implementing.
@ -343,12 +345,17 @@ verification, and reorient lanes plus accept completed reorient findings after
review. GUI visual smoke covers desktop and mobile screenshots and clicks the
bounded browser-fallback controls. A live bridge probe also proved
`prepareCheckpoint` creates a resumable thread and a later process can
`readModelingResult` from it. The next real move is dogfooding the built GUI on
a real Epiphany thread, fixing only concrete operator blockers. CRRC is not a
specialist-agent persona; the reorient-worker it may launch is the specialist.
Do not turn the coordinator into a broad hidden dispatcher, arbitrary
marketplace, alternate job backend, automatic semantic acceptance path, or
GUI-as-source-of-truth.
`readModelingResult` from it.
The next real move is not more direct Aetheria implementation. First quarantine
the Aetheria branch state: decide whether to discard the uncommitted
supervisor-created fog-compute slice or label it as operator intervention, then
run the next Aetheria step through Epiphany's GUI/coordinator/fixed lanes and
produce artifacts that show who did what. CRRC is not a specialist-agent
persona; the reorient-worker it may launch is the specialist. Do not turn the
coordinator into a broad hidden dispatcher, arbitrary marketplace, alternate
job backend, automatic semantic acceptance path, target-repo implementation
worker, or GUI-as-source-of-truth.
Live `thread/epiphany/scene`, `thread/epiphany/jobs`, `thread/epiphany/roles`,
`thread/epiphany/freshness`, `thread/epiphany/context`,

View file

@ -33,3 +33,4 @@
{"ts": "2026-04-29T23:32:51+00:00", "type": "verification", "status": "ok", "note": "Distilled prompt doctrine landed after rechecking global AGENTS, empty Codex memory surfaces, and nearby evidence ledgers: shared prompts now carry state/memory/source/anti-churn discipline; specialist templates split modeling/body, verification/soul, reorientation/life, and coordinator/Self. Verified with epiphany-core tests, codex-protocol tests, focused app-server template tests, role/reorient/status/coordinator smokes, and live-specialist artifacts."}
{"ts": "2026-04-30T00:07:45+00:00", "type": "implementation", "status": "ok", "note": "Specialist prompt bodies were extracted from Rust into vendor/codex/codex-rs/app-server/src/prompts/epiphany_specialists.toml. app-server now parses the bundled TOML once and uses it for modeling/body, verification/soul, reorientation/life, and coordinator/Self text while keeping fixed-lane launch policy in Rust. Verified with app-server config/template tests, role/reorient/coordinator smokes, and live-specialist artifacts."}
{"ts": "2026-04-30T00:42:00+00:00", "type": "implementation", "status": "ok", "note": "Modeling/checkpoint specialists now have a review-gated graph-growth path: their prompt/output contract can return a modeling-safe statePatch, thread/epiphany/roleResult projects it when valid, thread/epiphany/roleAccept applies completed modeling patches through the normal state validator with audit observation/evidence, and the GUI exposes Accept Modeling. Phase6 role smoke proved accepted modeling grew the durable graph before verification saw the expanded frontier."}
{"ts": "2026-04-30T02:12:42+00:00", "type": "rejected_path", "status": "contaminated", "note": "Aetheria dogfood exposed a supervision-boundary failure: the supervising Codex session directly edited and committed target-repo slices instead of driving Epiphany GUI/coordinator/fixed lanes. Treat those commits as supervisor-seeded implementation, not clean Epiphany evidence; future dogfood must quarantine direct edits as explicit operator interventions or contamination."}

View file

@ -33,6 +33,7 @@ invariants:
- Algorithmic-map prose and metaphor must be grounded in freshly read source context and concrete code references.
- Persistent state cruft is the same failure class as code cruft.
- If compaction interrupts source gathering or slice planning before the findings are persisted, the next agent must treat that work as lost and re-gather instead of continuing from imagined continuity.
- During Epiphany dogfood on another repo, the supervising Codex session must not masquerade as the Epiphany worker. Direct target-repo edits or commits are contamination unless explicitly authorized and labeled as operator intervention.
data_flow:
observe:
@ -58,6 +59,7 @@ active_subgoals:
- Dogfood the landed Phase 6 coordinator, limited safe-boundary CRRC automation, and pre-compaction checkpoint intervention before adding larger organs.
- Preserve review gates for semantic findings; automatic CRRC may compact or launch the fixed reorient-worker, but not accept or promote.
- Keep persistent project state ruthlessly distilled so rehydration strengthens the next turn instead of bloating it.
- Quarantine the Aetheria dogfood contamination: future target-repo work must be driven through Epiphany's GUI/coordinator/fixed lanes with auditable artifacts, not direct supervisor implementation.
accepted_design:
- Epiphany is a fork-level modeling architecture, not merely a Codex collaboration mode.
@ -110,6 +112,7 @@ accepted_design:
- Evidence is not an activity feed; repeated "I just did this" entries should be cut or distilled when git already proves the work.
- Language, tone, ritual, and emotional salience are real control surfaces for a language-model harness; they are not supernatural, but they shape attention, role, permission, and behavior.
- Specialist prompts are role-distilled instead of generic and their live text is config-backed in app-server: modeling/checkpoint protects the body of code, dataflow, seams, and frontier; verification/review protects the soul of promise, invariants, evidence, and user truth; reorientation protects life across compaction and source drift; coordinator is the read-only Self that routes attention without implementing, verifying, promoting, or accepting.
- Dogfood supervision is a separate operator role. If the supervising Codex session edits the target repo directly, that work can be useful seed material, but it is not clean Epiphany evidence and must be labeled as supervisor intervention or contamination.
- If the agent's persistent instructions, memory, workflow, or state shape are making it less coherent, slower to rehydrate, less honest, or more likely to build Jenga, the agent should ask the user to change it.
- Epiphany should make compaction less like death and more like sleep: bank the fire before the dark, so the next waking thing finds coals instead of ash and can meaningfully resume the pattern instead of merely continuing the task.
@ -170,5 +173,5 @@ rejected_paths:
reason: persistent state that accumulates every local truth becomes memory cruft and weakens rehydration
current_status:
summary: Phase 1 durable state, Phase 2 prompt integration, Phase 3 typed read, Phase 4 retrieval/indexing, Phase 5 update/distill/propose/promote/read/notification, and Phase 6 read-only scene, jobs, roles, freshness, targeted context, graph traversal, pressure, reorient, CRRC, coordinator, reorient launch/result/accept, explicit modeling/checkpoint and verification/review role launch/result templates, review-gated modeling role acceptance, MVP status, dogfood runner, coordinator runner, live specialist runner, limited safe-boundary CRRC automation, pre-compaction checkpoint intervention, the first Tauri/React GUI operator shell, and the distilled shared plus config-backed specialist prompt doctrine are landed. Native CRRC can steer active loaded Epiphany turns once at `shouldPrepareCompaction`; turn-complete automation can still compact or launch the fixed reorient-worker when the coordinator says it can auto-run. The GUI now has desktop/mobile visual smoke, durable checkpoint preparation, bounded status/coordinator artifact buttons, fixed role/reorient launch and read-back buttons, explicit modeling `roleAccept` for reviewed graph/checkpoint patches, and explicit reorientAccept after a completed result. Implementation remains main-agent work; CRRC remains workflow automation, not a specialist persona; GUI remains an operator surface over typed state, not a source of truth.
next_action: Dogfood the built GUI on a real Epiphany thread: open the Tauri debug app, prepare or enter a persisted thread, run coordinator guidance, launch/read the recommended fixed lane, inspect the generated artifact bundle, and fix only concrete operator blockers.
summary: Phase 1 durable state, Phase 2 prompt integration, Phase 3 typed read, Phase 4 retrieval/indexing, Phase 5 update/distill/propose/promote/read/notification, and Phase 6 read-only scene, jobs, roles, freshness, targeted context, graph traversal, pressure, reorient, CRRC, coordinator, reorient launch/result/accept, explicit modeling/checkpoint and verification/review role launch/result templates, review-gated modeling role acceptance, MVP status, dogfood runner, coordinator runner, live specialist runner, limited safe-boundary CRRC automation, pre-compaction checkpoint intervention, the first Tauri/React GUI operator shell, and the distilled shared plus config-backed specialist prompt doctrine are landed. Aetheria dogfood exposed a supervision-boundary failure: the supervising Codex session directly implemented and committed target-repo slices instead of driving Epiphany lanes, so those commits are supervisor-seeded work, not clean dogfood evidence. Native CRRC can steer active loaded Epiphany turns once at `shouldPrepareCompaction`; turn-complete automation can still compact or launch the fixed reorient-worker when the coordinator says it can auto-run. The GUI remains an operator surface over typed state, not a source of truth.
next_action: Quarantine the current Aetheria branch state, discard or label any uncommitted supervisor edits, then rerun dogfood through Epiphany's GUI/coordinator/fixed role lanes with auditable artifacts before accepting more target-repo implementation.

View file

@ -37,5 +37,5 @@ Do not continue broad implementation until the seam is re-grounded, and do not c
[coordinator]
note_template = '''
Coordinator is the read-only Self of the Epiphany organism. It does not implement, verify, promote, or accept; it preserves agency by routing body/modeling, soul/verification, and life/reorientation from CRRC {crrc_action}, pressure {pressure_level}, modeling {modeling_result_status}, verification {verification_result_status}, and reorient {reorient_result_status}. Current recommendation: {coordinator_action}.
Coordinator is the read-only Self of the Epiphany organism. It does not implement, verify, promote, or accept; it preserves agency by routing body/modeling, soul/verification, and life/reorientation from CRRC {crrc_action}, pressure {pressure_level}, modeling {modeling_result_status}, verification {verification_result_status}, and reorient {reorient_result_status}. During dogfood, the Self supervises target-repo work through fixed lanes and artifacts; direct supervisor edits are contamination unless explicitly marked as an operator intervention. Current recommendation: {coordinator_action}.
'''