GameCult/Epiphany
Archived
Watch
9
0
Fork
You've already forked Epiphany
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Keep AGENTS stable

Browse source
This commit is contained in:
Meta Vens 2026-04-24 21:06:18 +01:00
commit cecf0c676c
2 changed files with 2 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

18
AGENTS.md
View file

@ -14,23 +14,7 @@ The motivating failure mode is that an agent can make many plausible local edits
- Treat `notes/epiphany-fork-implementation-plan.md` as the current implementation plan for the Epiphany fork architecture.
- Update `state/map.yaml` when project understanding changes.
- Append evidence after meaningful research, implementation, verification, or rejected paths.
## Current Status
The old preset-backed TUI experiment is no longer the active path.
What is already landed across vendored Codex and `epiphany-core`:
- Phase 1 durable Epiphany thread state
- Phase 2 prompt integration
- a minimal Phase 3 typed app-server/client read surface via `Thread.epiphanyState`
- Phase 4 hybrid retrieval/indexing with explicit Qdrant-backed indexing and BM25 fallback
- Phase 5 typed state update, read-only distillation, verifier-backed promotion, and structural map/churn promotion validation
Current phase:
- Phase 5 semantic distillation and promotion is active.
- Next bounded move: build richer observation-to-map/churn proposal machinery above `thread/epiphany/distill`, `thread/epiphany/promote`, and `thread/epiphany/update`, while keeping retrieval/distillation read-only and avoiding watcher, GUI, or specialist-agent machinery.
- Do not store volatile current phase/status blocks in this file; keep current status in `state/map.yaml`, `state/evidence.jsonl`, and `notes/fresh-workspace-handoff.md`.
## Important Paths

1
state/evidence.jsonl
View file

@ -98,3 +98,4 @@
{"ts": "2026-04-24T19:38:51+00:00", "type": "implementation", "status": "ok", "note": "Moved the anti-Jenga regression/benchmark discipline from repo prose into runtime Epiphany prompt pressure. epiphany-core::render_epiphany_state now renders an Operating Discipline section in the developer-state block: one measured hypothesis at a time, revert failed regression/benchmark fixes before the next hypothesis, and stop when diff grows while understanding shrinks. Verified with epiphany-core tests and codex-core epiphany tests."}
{"ts": "2026-04-24T19:48:44+00:00", "type": "documentation", "status": "ok", "note": "Source-grounded pass over notes/epiphany-current-algorithmic-map.md. Re-read protocol state, session resume/prompt/persistence, app-server thread hydration and Epiphany RPC handlers, CodexThread update/retrieval host methods, and epiphany-core prompt/rollout/retrieval/distillation/promotion code. Updated the map to include the runtime anti-Jenga operating-discipline prompt section, removed the stale no-update-surface invariant, refreshed moved code anchors, corrected the handoff's outdated Phase 3 no-update-RPC note, and mechanically checked 98 local map links with line anchors."}
{"ts": "2026-04-24T21:02:31+01:00", "type": "documentation", "status": "ok", "note": "Corrected persisted phase memory after rechecking the harness roadmap and evidence log. Phase 4 is the landed retrieval/indexing/core-extraction baseline; Phase 5 is the current semantic distillation/promotion/proposal phase. Updated AGENTS.md, state/map.yaml, state/scratch.md, notes/fresh-workspace-handoff.md, and notes/epiphany-fork-implementation-plan.md so rehydrate/status no longer imply the current work is still a Phase 4 tail or a Qdrant live-smoke follow-up."}
{"ts": "2026-04-24T21:10:00+01:00", "type": "decision", "status": "ok", "note": "Kept AGENTS.md as durable operating/bootstrap policy rather than volatile status memory. Current phase, next action, and handoff details belong in state/map.yaml, state/evidence.jsonl, and notes/fresh-workspace-handoff.md; AGENTS.md should only point agents to those canonical stores and state stable discipline."}