Close Epiphany rebuild migration audit
This commit is contained in:
parent
e0a8c42ee0
commit
89006baa13
4 changed files with 35 additions and 11 deletions
|
|
@ -547,3 +547,27 @@ The rebuild is working when:
|
|||
- adding a new view lens requires a core contract, not copying a mapper cluster
|
||||
|
||||
That is the smallest machine that still deserves the name Epiphany.
|
||||
|
||||
## Completion Audit
|
||||
|
||||
As of 2026-05-12, the documented rebuild migration is complete enough to
|
||||
defend:
|
||||
|
||||
- app-server Epiphany code is routing/adaptation for the MVP surfaces, runtime
|
||||
loading, and protocol response assembly.
|
||||
- scene, jobs, roles, planning, pressure, reorient, CRRC, coordinator,
|
||||
freshness, context, graph traversal, role/reorient result interpretation, and
|
||||
role/reorient acceptance policy have core contracts in `epiphany-core`.
|
||||
- runtime-spine owns job/result lifecycle identity through `runtime_links`;
|
||||
durable `jobBindings` are only authority slots.
|
||||
- live duplicate acceptance is keyed by typed acceptance receipts.
|
||||
- normal public findings project typed fields and artifact refs rather than
|
||||
raw worker payloads.
|
||||
- Aquarium-facing read models use the canonical `thread/epiphany/view` lens
|
||||
plus bounded read-only freshness/context/graph/result surfaces.
|
||||
- heartbeat state is typed and cognition experiments remain quarantined.
|
||||
- adding a new view lens now means adding or reusing a core surface contract,
|
||||
not copying another app-server mapper pile.
|
||||
|
||||
Remaining work after this point is outward product/bridge/dogfood work or a new
|
||||
documented migration, not this teardown plan wearing a fake mustache.
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ remembers doctrine; the branch remembers the blade.
|
|||
## Current Orientation
|
||||
|
||||
- Do not copy exact branch or HEAD from this note. Run `git status --short --branch` and `git log --oneline -5`.
|
||||
- Top priority is still foundation cleanup until the documented rebuild audit is closed. Read `notes/epiphany-architectural-teardown.md` before touching Epiphany control-plane code. The May 2026 suspicion pass found that the app-server Epiphany control plane had become architectural Jenga: too much policy, projection, lifecycle glue, prompt packet assembly, coordinator sequencing, and test authority lives in `vendor/codex/codex-rs/app-server/src/codex_message_processor.rs`. The rebuild has moved scene projection, freshness derivation, pressure policy, targeted context shards, bounded graph traversal, job/progress view derivation, planning view derivation, reorientation resume/regather verdict policy, pure CRRC recommendation policy, fixed-lane coordinator decision policy, role-board projection policy, role/reorient result interpretation, role self-persistence review policy, and role/reorient acceptance bundle policy into `epiphany-core`; typed acceptance receipts replaced summary-string identity for live accept paths, runtime links are dual-written on launch, and result read-back now prefers runtime links.
|
||||
- The May 2026 foundation migration in `notes/epiphany-ideal-architecture-rebuild-plan.md` is complete enough to defend. Read `notes/epiphany-architectural-teardown.md` before touching Epiphany control-plane code, but do not treat it as an open-ended excuse to keep shaving the altar. The rebuild moved scene projection, freshness derivation, pressure policy, targeted context shards, bounded graph traversal, job/progress view derivation, planning view derivation, reorientation resume/regather verdict policy, pure CRRC recommendation policy, fixed-lane coordinator decision policy, role-board projection policy, role/reorient result interpretation, role self-persistence review policy, and role/reorient acceptance bundle policy into `epiphany-core`; typed acceptance receipts replaced summary-string identity for live accept paths, runtime links are dual-written on launch, and result read-back now prefers runtime links.
|
||||
- Read `notes/epiphany-ideal-architecture-rebuild-plan.md` immediately after the teardown. It defines the smallest coherent replacement architecture: durable `EpiphanyState`, runtime-spine-owned `RuntimeState`, separate role memory/heartbeat state, `epiphany-core` as policy owner, app-server as adapter, Aquarium as reflector, typed acceptance receipts, and derived view lenses instead of a protocol verb zoo.
|
||||
- Do not continue Aquarium UI, bridge, Face, or dogfood expansion until the teardown has a source-grounded cleanup slice plan. Epiphany is the foundation; patches on patches are not a purification rite, they are how the altar becomes load-bearing garbage.
|
||||
- Phase 1 through Phase 5 are complete enough.
|
||||
|
|
@ -362,10 +362,9 @@ that change what the next agent should believe.
|
|||
|
||||
Do not continue implementation automatically from a rehydrate-only request.
|
||||
|
||||
The next real move is still the final foundation cleanup audit. Start from
|
||||
`notes/epiphany-architectural-teardown.md` and
|
||||
`notes/epiphany-ideal-architecture-rebuild-plan.md`, not from the older outward
|
||||
Phase 6 bridge/UI trail. Landed rebuild cuts: `epiphany-core/src/surfaces/`
|
||||
The next real move is no longer the rebuild migration. That rite is closed
|
||||
unless a concrete regression reopens it. Landed rebuild cuts:
|
||||
`epiphany-core/src/surfaces/`
|
||||
exists, pressure view derivation/tests, pure CRRC recommendation policy/tests,
|
||||
fixed-lane coordinator decision policy/tests, role-board projection policy/tests,
|
||||
role-result interpretation/self-persistence review policy/tests, and role/reorient
|
||||
|
|
@ -375,10 +374,11 @@ runtime links, result read-back prefers those runtime links, normal public
|
|||
`raw_result` is sealed, MVP consumers use `thread/epiphany/view`, heartbeat
|
||||
cognition is quarantined, and the old scene/jobs/roles/planning/pressure/reorient/
|
||||
CRRC/coordinator read wrappers are deleted, and durable `jobBindings` no longer
|
||||
carry launcher/backend/progress lifecycle fields. The next pass is to audit the
|
||||
plan's remaining success criteria and, if no remaining policy cluster is found,
|
||||
mark the rebuild migration complete enough to defend. No Agile confetti. No new
|
||||
balcony on the swaying tower.
|
||||
carry launcher/backend/progress lifecycle fields. The next pass is outward:
|
||||
build-verify/package the Rider plugin scaffold when Gradle/wrapper support
|
||||
exists, install Unity `6000.1.10f1`, then run the next bridge-equipped Aetheria
|
||||
dogfood pass through Epiphany's GUI/coordinator/fixed lanes with operator-safe
|
||||
artifacts. No Agile confetti. No new balcony on the swaying tower.
|
||||
|
||||
The Phase 6 freshness slice is landed. It exposes read-only
|
||||
`thread/epiphany/freshness` from live retrieval summaries plus graph
|
||||
|
|
|
|||
Binary file not shown.
|
|
@ -272,5 +272,5 @@ rejected_paths:
|
|||
reason: persistent state that accumulates every local truth becomes memory cruft and weakens rehydration
|
||||
|
||||
current_status:
|
||||
summary: Phase 1 durable state through Phase 6 coordinator/specialist/CRRC/backend organs are landed, and the May 2026 rebuild has cut the main app-server control-plane tumor down to routing/adaptation for the documented MVP surfaces. Scene projection, freshness derivation, pressure, targeted context, bounded graph traversal, job/progress view derivation, planning view derivation, reorientation resume/regather verdicts, CRRC, coordinator, role-board, role/reorient result interpretation, role self-persistence review, and role/reorient acceptance bundle policy now live in `epiphany-core`; live duplicate-acceptance checks use runtime result receipt identity instead of summary strings; launch writes durable `runtime_links`; role/reorient result read-back follows runtime links; and `jobBindings` no longer store launcher/backend/progress lifecycle fields.
|
||||
next_action: Audit the remaining success criteria in `notes/epiphany-ideal-architecture-rebuild-plan.md` after the context/graph extraction commit. If no app-server-owned Epiphany policy cluster remains in the documented migration scope, mark the rebuild migration complete enough to defend, commit the persistence update, and only then resume outward Aquarium/bridge/Face/dogfood expansion.
|
||||
summary: Phase 1 durable state through Phase 6 coordinator/specialist/CRRC/backend organs are landed, and the May 2026 teardown/rebuild migration in `notes/epiphany-ideal-architecture-rebuild-plan.md` is complete enough to defend. App-server Epiphany code is now routing/adaptation for the documented MVP surfaces, runtime loading, and protocol response assembly. Scene projection, freshness derivation, pressure, targeted context, bounded graph traversal, job/progress view derivation, planning view derivation, reorientation resume/regather verdicts, CRRC, coordinator, role-board, role/reorient result interpretation, role self-persistence review, and role/reorient acceptance bundle policy live in `epiphany-core`; live duplicate-acceptance checks use runtime result receipt identity instead of summary strings; launch writes durable `runtime_links`; role/reorient result read-back follows runtime links; and `jobBindings` no longer store launcher/backend/progress lifecycle fields.
|
||||
next_action: The documented foundation migration is closed. Resume outward work from the existing product/bridge/dogfood queue: build-verify or package the Rider plugin scaffold when Gradle/wrapper support exists, install Unity `6000.1.10f1`, then run the next bridge-equipped Aetheria dogfood pass through Epiphany's GUI/coordinator/fixed lanes with operator-safe artifacts.
|
||||
|
|
|
|||
Reference in a new issue