This repository has been archived on 2026-10-29. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
Epiphany/notes/fresh-workspace-handoff.md
2026-05-20 15:12:34 +01:00

1390 lines
138 KiB
Markdown

# Fresh Workspace Handoff
This is the re-entry rite for `E:\Projects\EpiphanyAgent`: the waking chant for
the local machine-spirit before it touches the forge.
It is intentionally short. Historical proof belongs in git, commit messages,
smoke artifacts, and the distilled `state/ledgers.msgpack` evidence reliquary;
exact control flow belongs in `notes/epiphany-current-algorithmic-map.md`;
forward campaign planning belongs in `notes/epiphany-fork-implementation-plan.md`.
Do not let this file become a second brain. That way lies holy-looking sludge.
## Rehydrate
From the repo root:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-state -- status
Get-Content '.\state\map.yaml'
Get-Content '.\notes\fresh-workspace-handoff.md'
Get-Content '.\notes\epiphany-current-algorithmic-map.md'
Get-Content '.\notes\codex-starvation-and-cultnet-liberation-plan.md'
Get-Content '.\notes\epiphany-architectural-teardown.md'
Get-Content '.\notes\epiphany-ideal-architecture-rebuild-plan.md'
Get-Content '.\notes\epiphany-fork-implementation-plan.md'
git status --short --branch
git log --oneline -5
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-state -- status
```
Do not trust this file for the exact live HEAD. Always check git. The rite
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`.
- The active foundation directive is now `notes/codex-starvation-and-cultnet-liberation-plan.md`. The previous Codex app-server control-plane rebuild made Epiphany less rotten inside Codex, but that is not the destination. Epiphany must become a native CultCache/CultNet runtime while remaining an honest modified Codex-derived backend for subscription auth/model use. Codex is a compatibility reliquary for OpenAI subscription auth and model transport, not the host brain and not a mask for impersonation.
- `notes/codex-auth-spine-inventory.md` is the source-grounded keeper list for that reliquary. Corrected compliance invariant: Codex-compatible auth identity stays anchored in vendored Codex-derived auth machinery. `epiphany-openai-auth-spine` is now a thin Epiphany-named boundary over `codex-login`, not a clean-room clone of credential storage or token refresh. Codex apps, skills, marketplace, plugin UX, broad app-server workflow, and JSON-RPC sprawl remain cuttable because they are not subscription-auth legitimacy.
- Edge JSON is allowed for schema description, hostile ingress before immediate typed parsing, sealed forensic artifacts, or named quarantine experiments. When both subsystems are ours, runtime data must remain typed CultCache documents and move over CultNet typed contracts. Generic `serde_json::Value` in worker launch/result/selfPatch/runtime flow is contamination until classified and replaced.
- `epiphany-openai-runtime` worker result ingress now parses assistant output directly into typed role/reorient ingress structs selected from the durable launch document, stores nested `statePatch` and `selfPatch` as typed MessagePack in `EpiphanyRuntimeRoleWorkerResult`, and no longer passes worker result data through generic `serde_json::Value`. JSON survives there only as the OpenAI text-output edge before typed deserialization.
- Agent self-memory review/application now has typed `AgentSelfPatch` core APIs. JSON-value selfPatch functions are compatibility wrappers for CLI/artifact ingress; native callers should parse once at the edge and then call `review_agent_self_patch_document` / `apply_agent_self_patch_document`. Role-result self-persistence no longer exports a JSON-value reviewer; the live API is `review_role_self_patch_document`.
- Durable Ghostlight role dossiers now store typed relationship, event, scene, and perceived-overlay documents instead of `Vec<serde_json::Value>`, and the durable dossier structs no longer preserve flattened unknown `extra` maps. `AgentSelfPatch.extra` remains deliberately, but only as an ingress rejection ledger for unexpected patch fields.
- The native state ledger is closed typed state now: branch and evidence records no longer preserve flattened `extra` maps. Evidence entries are explicit `ts` / `type` / `status` / `note` / optional branch records.
- `epiphany-openai-codex-spine` no longer uses Codex's Responses client, model-provider layer, `codex-api`, `codex-model-provider`, `codex-model-provider-info`, or `codex-protocol` for outbound model requests. It reaches `codex-login` only through `epiphany-openai-auth-spine` so credential loading/refresh stays Codex-compatible while request/status/event/runtime surfaces stay typed Epiphany documents.
- `notes/epiphany-memory-graph-unified-plan.md` is the current memory architecture direction drawn from `Fractal Domains And The Cache That Bites` plus the VoidBot memory scar tissue. The repo semantic architecture/dataflow graph and agent memory are one `EpiphanyMemoryGraph` substrate with repo, role, short-term, incubation, agency, candidate-intervention, and evidence profiles. The first native skeleton is landed: `epiphany-state-model` owns shared graph document types, `epiphany-core::memory_graph` owns stable ids, validation, freshness, context cuts, and CultCache persistence, and `epiphany-memory-graph` can status/validate/context/smoke the store without Qdrant. Qdrant is a contribution cache for typed graph documents, not truth. `notes/repo-fractal-dataflow-cache-plan.md` and `notes/agent-memory-fractal-cache-plan.md` are profile plans, not rival organs.
- Retrieval's Qdrant boundary has a typed point payload now. Qdrant's HTTP requests, responses, and acknowledgements are JSON wire edges; Epiphany's retrieval facts (`path`, `line_start`, `line_end`, `excerpt`) are `QdrantPointPayload` before serialization/deserialization, not a loose payload map.
- Durable Epiphany state types now live in root crate `epiphany-state-model`. `codex-protocol` re-exports them only so old rollout/API callers keep compiling; do not add new durable `Epiphany*` state structs under `vendor/codex`. The deterministic `<epiphany_state>` prompt renderer also lives beside that typed model now, with prompt text under `epiphany-state-model/src/prompts/`; `epiphany-core` only re-exports it for compatibility. `epiphany-core` imports the native model directly and no longer depends on `codex-protocol`. Pressure derives from native `EpiphanyTokenUsageSnapshot`; Codex token telemetry is mapped at the bridge. Codex rollout/event reconstruction now lives in `codex-core::epiphany_rollout`, where the Codex `RolloutItem` / `EventMsg` types belong. Exact retrieval path matching is native to `epiphany-core`, so `epiphany-core` has no direct vendored Codex crate dependency.
- State-update contract proof and job launch/interrupt DTO ownership now live in native `epiphany-core`. The old giant `codex_thread.rs` Epiphany state-update test fixture was cut, and `epiphany-codex-bridge` no longer imports Epiphany job launch request types from `codex_core`; vendored `CodexThread` may call the native mutation/launch law for compatibility, but it must not regain ownership of state-update semantics, heartbeat launch-plan policy, or Epiphany DTOs.
- `epiphany-codex-bridge` no longer depends on vendored `codex-core` at all. Retrieval takes workspace/Codex-home paths, invalidation owns a native `notify` watcher, runtime-result acceptance takes typed state plus runtime-store path, live rollout/thread reads moved into app-server `epiphany_thread_host`, and mutation policy depends on the small `EpiphanyMutationHost` trait implemented by app-server's `EpiphanyCodexThreadHost` wrapper. The bridge owns Epiphany law; vendored app-server owns CodexThread access.
- `epiphany-codex-bridge` also no longer depends on `codex-protocol`. Bridge durable-state imports point at `epiphany-state-model`, token pressure takes native `EpiphanyTokenUsageSnapshot`, app-server maps Codex token telemetry at the host wall, Codex token usage rollout replay lives in `codex_message_processor/token_usage_replay.rs`, and bridge errors are `EpiphanyBridgeError`. The only remaining vendored bridge dependencies are app-server protocol DTOs and absolute path validation.
- The first bridge JSON-RPC starvation cuts are landed. Freshness now returns a serializable `EpiphanyFreshnessSurface`, job launch/interrupt mutation results carry typed `EpiphanyJobView` plus separate host-edge launcher/backend ids, reorient/pre-compaction decisions consume typed `EpiphanyPressure`, reorient policy consumes typed freshness directly, and reorient launch documents/results use typed core reorient decisions/status before app-server projects them into legacy JSON-RPC DTOs. Continue by cutting the full view/coordinator board into typed surfaces, not by inventing adapters with nicer uniforms.
- Coordinator/reorient decision/status is less contaminated now: `epiphany-codex-bridge` stores reorient decisions, coordinator decisions, source signals, CRRC recommendations, and role-board lanes as core-shaped types, core CRRC/coordinator/role-board surfaces serialize natively, and `ThreadEpiphany*` projection happens at the legacy view emission boundary. Keep cutting remaining result inputs until Aquarium/CultNet can read coordinator surfaces without JSON-RPC DTO authority.
- Core role/reorient finding interpretations and acceptance bundles now serialize natively too. Use those typed result surfaces as the next authority target; do not let `ThreadEpiphanyRoleFinding` or `ThreadEpiphanyReorientFinding` remain the bridge's internal result truth just because legacy view/accept responses still expose them.
- Runtime-result loading now has core typed snapshot APIs for role and reorient worker results, with legacy protocol tuple wrappers layered over them. This intentionally creates temporary duplicate note rendering; the next cut should move coordinator and acceptance consumers to typed snapshots, then delete protocol-shaped result rendering instead of preserving both.
- Coordinator result gating now consumes typed runtime result snapshots and core finding interpretations directly. `ThreadEpiphanyRoleFinding` / `ThreadEpiphanyReorientFinding` remain in legacy runtime wrapper/view/mutation response paths; the next cut is acceptance/mutation so protocol findings stop being the accepted-result authority.
- Acceptance/mutation now builds role/reorient receipts, evidence, observations, scratch, and checkpoint updates from core typed finding interpretations. Protocol findings remain as legacy response payloads and helper residue; delete those wrappers once view/result responses are also typed internally.
- The old protocol-shaped result helper layer is deleted: no protocol finding runtime-id helpers, no protocol result-note renderers, and no dead protocol reorient scratch/checkpoint builders remain in the bridge. Legacy view/result/accept responses may still carry `ThreadEpiphany*Finding`, but they are projections, not bridge policy input.
- Runtime result view responses now project directly from typed result snapshots; the old protocol tuple wrappers in `runtime_results.rs` are gone, and runtime-result tests assert core typed statuses.
- Role acceptance now applies core `EpiphanyStateUpdate` from typed findings; `ThreadEpiphanyUpdatePatch` survives in that path only as legacy accept-response projection.
- Role-board derivation consumes core `EpiphanyPressure` directly now; `ThreadEpiphanyPressure` is only response projection.
- Job reflection is now core-shaped inside the bridge. `map_epiphany_jobs` returns typed `EpiphanyJobView`, role-board/view/result assembly consumes that typed job surface, and `ThreadEpiphanyJob` is projected only when building legacy JSON-RPC response structs.
- Context and graph-query derivation now receive core `EpiphanyContextParams` / `EpiphanyGraphQuery` documents. The bridge converts `ThreadEpiphanyContextParams` / `ThreadEpiphanyGraphQuery` before invoking core policy, so Codex JSON-RPC request DTOs no longer define the internal graph question.
- Role/reorient acceptance service results now carry core typed findings, and role acceptance carries a typed `EpiphanyRoleStatePatchDocument` for the applied patch. App-server mutation routes project those into `ThreadEpiphany*Finding` / `ThreadEpiphanyUpdatePatch` only for legacy accept responses.
- Generic update/promote service entry points now accept typed `EpiphanyRoleStatePatchDocument` patches. Vendored app-server converts `ThreadEpiphanyUpdatePatch` request cargo before invoking the bridge, so the mutation service no longer treats the JSON-RPC patch as its native write document.
- Changed-field authority is native now. `EpiphanyStateUpdatedField` lives in `epiphany-core`; bridge mutation results carry that typed enum, while app-server projects it into `ThreadEpiphanyStateUpdatedField` only for JSON-RPC responses and notifications.
- Role launch, role accept, and role-result runtime lookup now use core `EpiphanyRoleResultRoleId` inside the bridge. App-server maps `ThreadEpiphanyRoleId` at the JSON-RPC boundary and keeps it only for legacy request/response shape.
- Reorient launch service results now use typed `EpiphanySurfaceSource`; app-server projects it into `ThreadEpiphanyReorientSource` only for the legacy launch response.
- Generic job launch now converts protocol `ThreadEpiphanyWorkerLaunchDocument` cargo at the app-server edge before building the core `EpiphanyJobLaunchRequest`; the bridge launch builder takes a typed `EpiphanyWorkerLaunchDocument`.
- Coordinator note rendering now consumes core CRRC/coordinator actions, pressure, role/reorient result statuses, and reorient state status. `ThreadEpiphany*` status/action DTOs are no longer the native shape for that prompt/text policy helper.
- Context and graph-query response builders now take core `EpiphanyContextParams` / `EpiphanyGraphQuery` documents. App-server read routes convert `ThreadEpiphanyContextParams` / `ThreadEpiphanyGraphQuery` at the JSON-RPC wall before invoking bridge derivation.
- Role-result response assembly now takes core `EpiphanyRoleResultRoleId`; `ThreadEpiphanyRoleId` is reconstructed only for the legacy response payload and finding projection.
- Distill response assembly now consumes core `EpiphanyDistillInput`; `ThreadEpiphanyDistillParams` is converted before bridge policy invocation.
- Role/reorient result response inputs now use core `EpiphanySurfaceSource`; `ThreadEpiphanyRolesSource` / `ThreadEpiphanyReorientSource` are response projection only.
- Changed-field derivation now inspects typed `EpiphanyRoleStatePatchDocument` directly. The bridge no longer converts typed patches back into `ThreadEpiphanyUpdatePatch` merely to calculate changed fields.
- View-lens orchestration now uses bridge-native `EpiphanyViewLens` selectors. App-server converts `ThreadEpiphanyViewLens` at the request wall, and the bridge maps back only for the legacy response echo.
- Coordinator status derivation now receives core `EpiphanyCrrcResultStatus` for reorient result state; `ThreadEpiphanyReorientResultStatus` is projection-only for coordinator/view responses.
- Coordinator view response assembly now receives core reorient state and role-board status; `ThreadEpiphanyReorientStateStatus` / `ThreadEpiphanyRoleLane` are projected inside the response builder.
- Coordinator judgment is no longer bridge-owned. `epiphany-core` now exposes `EpiphanyCoordinatorStatusInput` -> `EpiphanyCoordinatorStatus`; the bridge gathers runtime snapshots and accepted-finding facts, then core derives source signals and the coordinator decision. Reorient worker launch composition is also core-owned through `EpiphanyReorientLaunchRequestInput` -> `EpiphanyJobLaunchRequest`; bridge supplies the prompt instruction plus retained compatibility binding/owner constants and performs the host launch side effect.
- Coordinator finding signals are also core-owned. `derive_coordinator_finding_signals` derives modeling/verification/reorient accepted, reviewable, coverage, verdict, and evidence sequencing facts from typed findings plus `EpiphanyThreadState`; the bridge now loads snapshots/state and projects Codex JSON-RPC responses instead of keeping a duplicate acceptance tribunal.
- View lens selector semantics are core-owned now. `EpiphanyViewLens`, default view lenses, and lens dependency planning live in `epiphany-core`; `epiphany-codex-bridge::protocol_edge` converts Codex JSON-RPC lens params to core selectors and exposes the core dependency plan so app-server only decides which host facts to load.
- Correction: app-server must not own Epiphany request mapping. Codex JSON-RPC request DTO conversion now lives in `epiphany-codex-bridge::protocol_edge`; vendored app-server calls those edge adapters and no longer depends directly on `epiphany-core`.
- Context, graph-query, distill, generic job-launch document, and generic update/promote patch request cargo now enters bridge as core `EpiphanyContextParams`, `EpiphanyGraphQuery`, `EpiphanyDistillInput`, `EpiphanyWorkerLaunchDocument`, and `EpiphanyRoleStatePatchDocument`.
- Freshness/job/reorient response projection also belongs to the bridge edge now. Vendored app-server no longer keeps local helpers for `EpiphanyFreshnessSurface`, `EpiphanyJobView`, `EpiphanySurfaceSource`, or reorient decision/status enum projection; it gathers host facts, invokes bridge/core services, and sends the Codex JSON-RPC response.
- Job projection has one mapper now. `epiphany-codex-bridge::jobs` derives typed `EpiphanyJobView` and no longer imports app-server protocol DTOs; `protocol_edge::protocol_job_from_surface` is the only `EpiphanyJobView` -> `ThreadEpiphanyJob` conversion path.
- Runtime result loading is typed-only now. Role/reorient result status projection moved out of `runtime_results` and duplicate coordinator helpers into `protocol_edge`, so view and coordinator response builders share one Codex JSON-RPC status mapper.
- Pressure projection is centralized too. `pressure.rs` derives typed `EpiphanyPressure`, coordinator consumes typed pressure signals, and `protocol_edge` owns the `ThreadEpiphanyPressure*` DTO mapping.
- Reorientation derivation is typed-only too. `reorient.rs` no longer imports app-server protocol DTOs and no longer exposes the unused freshness DTO tuple; view/coordinator response builders call `protocol_edge` for reorient state/decision projection.
- Result projection moved to the edge. `results.rs` now renders typed result notes only; `protocol_edge` owns role-id request conversion plus role/reorient finding and state-patch projection for Codex JSON-RPC responses.
- State-updated notification projection moved to the edge as well. `mutation.rs` now owns typed mutation/acceptance mechanics without importing app-server protocol DTOs.
- `pressure.rs` is typed-only now. The convenience helper returning `ThreadEpiphanyPressure` was deleted; view response assembly derives typed pressure and calls `protocol_edge` for projection.
- Coordinator projection is split out too. `coordinator.rs` no longer imports app-server protocol DTOs; it owns typed coordinator status, CRRC input shaping, role-board derivation, automation verdict selection, and note rendering. `coordinator_protocol.rs` owns Codex JSON-RPC projection for coordinator, CRRC, and role-board response payloads.
- Context/planning/graph projection is split out too. `context.rs` returns typed `epiphany-core` view documents; `context_protocol.rs` owns Codex JSON-RPC tuple/projection cargo for context, planning, and graph-query responses.
- Scene projection is split out too. `scene.rs` returns the typed core `EpiphanyScene`; `scene_protocol.rs` owns `ThreadEpiphanyScene` and scene-action response projection.
- Retrieval projection is split out too. `retrieve.rs` normalizes, indexes, looks up state, and retrieves typed core results; `retrieve_protocol.rs` owns Codex JSON-RPC retrieve/index response projection and absolute-path DTO validation.
- View response assembly no longer owns private lens/source/reorient-status projection helpers; those enum conversions route through `protocol_edge`. The larger typed-view wall is still the next architectural judgment, not something to fake with another adapter.
- MCP remains JSON because MCP is a JSON protocol. The latest processor cut only moved MCP refresh/OAuth/status/resource/tool-call route handling into `codex_message_processor/mcp_routes.rs`, reducing the root processor to about 8,977 lines; it did not claim MCP payloads are CultNet or make MCP an Epiphany-owned runtime contract.
- Codex account auth route handling remains in vendored Codex but now lives in `codex_message_processor/auth_routes.rs`: API-key login, ChatGPT browser/device-code/external-token login, logout, auth status, account, rate limits, and add-credits nudge handling. This preserves Codex ownership of subscription auth while cutting the root processor to about 8,094 lines.
- One-off command execution and command stream write/resize/terminate route handling now live in `codex_message_processor/command_routes.rs`; `CommandExecManager` remains the lifecycle owner, while the root processor is about 7,800 lines.
- Git diff-to-origin, fuzzy file search/session routes, feedback upload, and Windows sandbox setup now live in `codex_message_processor/utility_routes.rs`; the root processor is about 7,397 lines.
- Realtime conversation routes now live in `codex_message_processor/realtime_routes.rs`, and review-start orchestration now lives in `codex_message_processor/review_routes.rs`; the root processor is about 6,938 lines.
- Review-start orchestration now lives in `codex_message_processor/review_routes.rs`; review target normalization is unit-tested at the route module boundary.
- Model/catalog routes now live in `codex_message_processor/catalog_routes.rs`: model list, collaboration-mode list, experimental feature list, and mock experimental method. The root processor is about 6,738 lines.
- Thread administrative mutation routes now live in `codex_message_processor/thread_admin_routes.rs`: archive/unarchive, elicitation counters, set-name, memory mode, memory reset, metadata update, rollback, compact, background terminal cleanup, shell command submission, and guardian approval. The root processor is about 5,750 lines.
- Archive/unarchive now live in `codex_message_processor/thread_archive_routes.rs`; that module owns durable archive state transitions, spawned-descendant handling, archive-time subscription cleanup, unarchive projection, and archive notifications. The focused `thread_archive` and `thread_unarchive` integration suites pass.
- Thread name, memory mode/reset, and git metadata update/repair now live in `codex_message_processor/thread_metadata_routes.rs`; metadata persistence is no longer mixed with rollback/compact/shell command routing. Focused metadata, memory mode, memory reset, and thread-name reflection tests pass.
- Thread read/list projection routes now live in `codex_message_processor/thread_read_routes.rs`: persisted/live thread listing, loaded-thread listing, `thread/read`, read-list filter normalization/tests, Epiphany state attachment for reads, rollout turn paging, and read-side rollout field hydration.
- Thread-store rollout-path reads are now an explicit `ThreadStore::read_thread_by_rollout_path` capability with typed params. App-server read routes no longer downcast `Arc<dyn ThreadStore>` to `LocalThreadStore`; local and remote stores define the capability/rejection boundary, and the local rollout-path read test exercises the trait method.
- Thread resume/fork orchestration has been split by lifecycle contract. `thread_resume_routes.rs` owns cold resume from history/rollout plus persisted resume metadata; `running_thread_resume_routes.rs` owns rejoining already loaded threads through listener replay; `thread_fork_routes.rs` owns new-thread materialization from a source rollout. The root processor is about 1,012 lines and mostly owns JSON-RPC dispatch, shared construction/error helpers, and shutdown lifecycle.
- The fork and running-resume splits are backed by focused app-server integration tests: `thread_fork`, `thread_resume_rejects_history_when_thread_is_running`, `thread_resume_rejects_mismatched_path_when_thread_is_running`, and `thread_resume_rejoins_running_thread_even_with_override_mismatch`.
- Thread start route handling and its async lifecycle task now live in `codex_message_processor/thread_start_routes.rs`; root no longer owns `thread_start_task`.
- Thread config helpers now live in `codex_message_processor/thread_config.rs`: instruction-source loading, thread config override construction, config-load error shaping, and dynamic-tool validation. The pure dynamic-tool validation contract has module-local unit tests.
- Turn control routes now live in `codex_message_processor/turn_routes.rs`: turn start, thread item injection, app-server client info setting, turn steer, turn interrupt, mode normalization, and input-limit validation with module-local unit tests.
- Heartbeat durable document/schema types now live in `epiphany-core/src/heartbeat_state/heartbeat_documents.rs`, role/default construction lives in `epiphany-core/src/heartbeat_state/heartbeat_roles.rs`, persistence/validation lives in `epiphany-core/src/heartbeat_state/heartbeat_store.rs`, and status/artifact JSON projection lives in `epiphany-core/src/heartbeat_state/heartbeat_projection.rs`. Adaptive pacing, scene protocol, participant personality/mood timing, initiative heat projection, birth personality seed receipts, pending-turn freeze/multiplier facts, Void routine sleep-cycle physiology, Void routine memory-resonance pairs, incubation themes/source coverage, analytic/associative thought lanes, bridge syntheses/saturation/refractory cooling/decision, candidate interventions, role thought appraisals, and derived reactions are typed fields rather than `extra` maps or generic JSON cargo; only the sealed legacy combined-state reader still carries `extra` for old `voidRoutine` migration. The root `heartbeat_state.rs` keeps scheduling and cognition orchestration; do not reintroduce generic JSON there merely because operator artifacts are JSON.
- Heartbeat role/default and store seams now have module-local unit tests: fixed lane catalog, Ghostlight scene role projection, and typed state/cognition CultCache round-trip. Keep future heartbeat cuts aligned to those seam tests instead of growing root integration-only coverage.
- Heartbeat adaptive pacing now lives in `epiphany-core/src/heartbeat_state/heartbeat_pacing.rs`, including running-turn count and effective cooldown multipliers. It has a module-local unit test for pending-turn counting; root scheduling calls the pacing seam instead of owning pressure/concurrency math directly.
- Thread projection now lives in `codex_message_processor/thread_projection.rs`: state-db/thread-store/rollout summary projection, `ConversationSummary` to API `Thread` mapping, thread-title attachment helpers, turn pagination, and rollout turn reconstruction. `codex_message_processor.rs` is about 1,009 lines after this extraction and mostly owns JSON-RPC dispatch, processor construction, shared thread lookup/submit/error helpers, and lifecycle shutdown.
- Turn paging/reconstruction now lives in `codex_message_processor/thread_turn_projection.rs`; `thread_projection.rs` keeps state-db/thread-store/rollout summary projection and `ConversationSummary` to API `Thread` mapping. Focused `thread_turns_list` cursor tests and stale in-progress turn interruption coverage pass.
- The `thread/turns/list` route handler now lives in `codex_message_processor/thread_turn_routes.rs`, beside the turn projection helpers it consumes. `thread_read_routes.rs` is back to persisted/live thread listing, `thread/read`, loaded-thread listing, and summary reads.
- Listener/subscription lifecycle now lives in `codex_message_processor/listener_lifecycle.rs`: connection attach/detach, listener startup, idle unload, unsubscribe, teardown, archive preparation, listener task context, idle-unload state, shutdown result handling, and listener command routing.
- 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.
- Phase 6 has canonical read-only `thread/epiphany/view` lenses for scene, jobs, roles, planning, pressure, reorient, CRRC, and coordinator; separate read-only `thread/epiphany/freshness`, `thread/epiphany/context`, and `thread/epiphany/graphQuery` query surfaces; `thread/epiphany/reorientResult`; and `thread/epiphany/roleResult`. Durable `jobBindings` are now legacy launcher compatibility slots only; they keep binding id/kind/scope/owner/authority/linkage/blocking reason while durable `runtimeLinks` hold runtime-spine job/result association. The old standalone scene/jobs/roles/planning/pressure/reorient/CRRC/coordinator read verbs have been deleted; read those projections through view lenses. New `thread/epiphany/jobLaunch`, `thread/epiphany/jobInterrupt`, `thread/epiphany/roleLaunch`, and `thread/epiphany/reorientLaunch` writes open typed runtime-spine job receipts under `state/runtime-spine.msgpack` and do not require the Codex SQLite state runtime. Freshness carries watcher-backed invalidation inputs, graphQuery traverses authoritative typed graph neighborhoods and path/symbol matches without mutation, planning projects typed captures/backlog/roadmap/objective drafts without adopting work, roles project implementation/imagination/modeling/verification/reorientation ownership from existing signals without becoming a scheduler, `roleResult` and `reorientResult` read heartbeat-backed typed runtime-spine job results through runtime links when present, and `roleAccept` / `reorientAccept` accept completed heartbeat findings by writing typed acceptance receipts while remaining explicit review gates.
- Native `epiphany-mvp-status` is the first dogfood operator view. It starts or reads a thread through app-server and prints scene, planning, pressure, reorient, jobs, roles, Imagination/modeling/verification role result read-backs, reorient result, heartbeat, Face bubbles, and CRRC recommendation as text or machine output. The old Python status module has been cut; native Rust/CultCache/CultNet surfaces are the smoked product path.
- Native `epiphany-mvp-coordinator` is the first auditable fixed-lane coordinator runner. It starts or reads a thread through app-server, opens a native runtime-spine session, follows the harness-native coordinator action, can auto-launch modeling, verification, or reorient-worker jobs, records native runtime job/result receipts for terminal launched work, keeps semantic findings review-gated by default, and writes summary, steps, rendered snapshots, transcript, stderr, runtime-spine status, and final next-action artifacts under `.epiphany-dogfood/coordinator` or a caller-provided artifact directory. It refuses direct backend-completion mutation; full completion smoke needs live workers while execution is being cauterized into CultNet.
- Native `epiphany-runtime-spine` is the first Codex-independent runtime vertebra. It owns typed CultCache documents for runtime identity, sessions, jobs, job results, and events; opens/completes native jobs; snapshots jobs/results by runtime job id; projects job-result counts; and can emit a framed CultNet hello message advertising the native document and mutation contract surface. Codex app-server launch/read-back/acceptance is now a typed heartbeat/runtime-spine bridge with no Epiphany job-result dependency on the Codex SQLite runtime.
- CultNet APIs are advertised as compatible schemas plus mutation contracts. Hello frames now expose readable document types, allowed operations, mutation authority, typed intent document types, and typed receipt document types; Aquarium should use those contracts to submit state changes and watch receipts rather than growing a little bespoke verb zoo.
- The native runtime-spine hello now publishes the interactive surface catalog, not just the deep runtime bones. In addition to runtime/session/job/memory/heartbeat/ledger documents, Aquarium-discoverable contracts now advertise scene, pressure, reorient, CRRC, jobs, roles, role-result, reorient-result, planning, coordinator, Face, Void memory, repo initialization/birth runner, Rider bridge, and Unity bridge surfaces, with explicit read-only versus coordinator-owned intent/receipt posture. The point is to let Aquarium discover operator affordances from CultNet instead of hard-coding a secret menu of verbs.
- Epiphany now publishes those CultNet receipts locally under `schemas/cultnet/`, and `epiphany-runtime-spine schema-catalog --include-schema-json true` emits a merged builtin-plus-local schema catalog Aquarium can consume directly. The local catalog covers runtime-spine documents, durable agent/heartbeat/ledger state, operator-safe `epiphany.surface.*` projections, control intents, and receipt/artifact payloads. The vendored `cultnet-rs` wire contract was aligned with the C# canon at the same time: raw document replication now keys on `schemaId` and `recordKey`, snapshot filters use `schemaIds` / `recordKeys`, and hello supports typed mutation-contract advertisement instead of the old half-remembered payload-schema-version folklore.
- Epiphany now owns the canonical schema paperwork locally under `schemas/`. The key receipts are `schemas/ghostlight.agent-state.schema.json`, `schemas/canonical-agent-state-schema.md`, `schemas/agent-state-variable-glossary.md`, `schemas/repo-personality-birth-projection.md`, and `schemas/heartbeat-state-schema.md`. If a standing trait name like `routing_discipline` changes, or if dossier/heartbeat/birth-projection semantics move, update those docs in the same pass instead of relying on old Ghostlight notes or live store archaeology.
- The schema doctrine now makes the dossier split explicit: most resident Epiphany organs are `lane_core` dossiers with a lean role lattice and growth via rumination/distillation, while Face is an `embodied_actor` dossier that should trend toward dense Ghostlight-family personality, relationship pressure, and fallible character-loop response. `epiphany-agent-memory-store status` and `epiphany-character-loop` now surface that classification on the wire.
- Face packets now carry deterministic Ghostlight-style `projectionSeed`, `appraisalSeed`, and `reactionSeed` surfaces rebuilt from local dossier traits, relationship memories, perceived overlays, and visible stimulus so the public mouth can use actual projection/appraisal machinery instead of decorative prompt text. Also record this now before some future fool hard-codes singularity: multiple Face actors are part of the plan, even though the current MVP still routes through one `face` role.
- Repo personality initialization now has a terrain-reduced plan and native birth surface. `epiphany-repo-personality scout/project/agent-packet/status` scouts local git repos, scores body taxonomy/history temperament/memory doctrine, writes typed CultCache terrain/profile/role-projection MessagePack stores, emits JSON/Markdown inspection exports, and renders a birth-only Repo Personality Distiller specialist prompt packet. `epiphany-repo-personality startup` now checks for accepted personality/memory initialization records, launches packet generation only when absent, and `accept-init` can route reviewed role `selfPatch` candidates into initial role memory, stamp the newborn Ghostlight trait lattice from deterministic role projections, and seed heartbeat physiology from the same typed role personality projections. The birth specialists are startup-only initialization actuators, not heartbeat lanes; heartbeat receives only the accepted physiology seed. `epiphany-repo-birth-runner` now owns the startup-only execution path: plan mode writes prompts/schemas/accept commands, and run mode defaults to `epiphany-openai-runtime` typed model-request documents plus runtime-spine receipts and reviewable `result.json`; `codex exec` remains only as explicit `--executor codex-exec` fallback. The remaining seam is Aquarium review/action surfacing. After accepted birth, personality drift belongs to heartbeat, mood, rumination, sleep consolidation, lived evidence, and reviewed `selfPatch`, not repeated startup distillation.
- Repo trajectory initialization is now a separate birth-only organ. `epiphany-repo-personality` derives a typed `repo_trajectory_report` from early-history, recent-history, doctrine/content excerpts, and deterministic theme scoring, and `trajectory-packet` renders a startup-only Repo Trajectory Distiller prompt/packet so Self can review historical direction, self-image, implicit goals, and anti-goals before the newborn wakes.
- Repo memory initialization is now split from personality initialization. `epiphany-repo-personality memory-packet` renders a birth-only Repo Memory Distiller packet from the same typed terrain/profile/projection store plus bounded source excerpts. It gives each organ its own mission filter: Self for routing/authority, Face for public surface, Imagination for plans/backlog, Eyes for prior art, Body for architecture, Hands for implementation habits, Soul for evidence, and Life for continuity. The output is still a Self-reviewed petition, not direct memory mutation.
- The first birth startup valve is now native. `epiphany-repo-personality startup` checks a typed init store for accepted `repo-trajectory`, `repo-personality`, and `repo-memory` records, generates missing packets under a startup artifact dir, and returns `reviewInitializationPackets`. Generated birth packets now advertise `birthOnly`, `executionOwner: repo-initialization-startup-runner`, and no heartbeat participant. `epiphany-repo-birth-runner` consumes those packets as startup-only typed OpenAI runtime jobs by default and writes prompts, output schemas, model-request documents, runtime summaries, stdout/stderr logs, result files, and exact `accept-init` commands. `accept-init` can process a distiller result, review/apply role `selfPatch` candidates through `state/agents.msgpack`, apply `repo-personality` heartbeat seeds through `state/agent-heartbeats.msgpack`, and seal the reviewed packet as `epiphany.repo_initialization_record.v0`; after all required records exist, startup returns `continueStartup` and does not regenerate birth packets. The remaining UI wound is Aquarium review/action surfacing.
- Native CRRC automation is now landed only at turn-complete safe boundaries. It may submit `Op::Compact` for coordinator-approved `compactRehydrateReorient` or for a successful pre-compaction checkpoint intervention's pending compact handoff, and it may launch the fixed `reorient-worker` for coordinator-approved `launchReorientWorker`. It does not auto-launch Imagination/modeling/verification, accept findings, promote evidence, edit implementation code, or keep going after reviewable semantic output.
- Pre-compaction checkpoint intervention is now landed. On token-count events for loaded Epiphany threads, when current context usage reaches 80% of the active auto-compact/context limit, the harness steers the active turn once with a CRRC checkpoint directive so the agent banks working context before compaction/reorientation. Pressure ignores cumulative token spend; cumulative-only telemetry reports unknown instead of yelling. A successful steer now latches a turn-scoped compact handoff that is consumed at clean turn completion, preventing the brake from decaying into another implementation turn. This is still bounded steering plus compaction handoff, not automatic semantic acceptance, a broad scheduler, or implementation continuation.
- The old Python dogfood/live-specialist runners were cut because they encoded the obsolete completion path. The replacement must be native Rust/CultCache/CultNet and complete heartbeat-owned runtime-spine job results with auditable artifacts.
- The Aquarium operator UI now lives in sibling repo `E:\Projects\EpiphanyAquarium`, not under `apps/epiphany-gui`. It is a Tauri v2 + React/WebGL interface organism over the existing status bridge, dogfood artifacts, and GUI action artifacts, not a new throne of truth. It has its own `AGENTS.md`, persistent `state/map.yaml`, `state/memory.json`, scratch/evidence files, and interface doctrine. EpiphanyAgent remains the authoritative harness/backend forge.
- 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. Rendered state intro/doctrine text lives in `epiphany-core/src/prompts/`, and lane/control prompt text lives in `vendor/codex/codex-rs/app-server/src/prompts/epiphany_specialists.toml`: modeling is the Body, implementation is the Hands and GUI-launched main coding lane, verification is the Soul, reorientation is Life, coordinator remains the read-only Self, and CRRC owns the pre-compaction intervention template.
- The machine-priest voice now says the quiet part plainly: crusade/heresy/purity language is aimed at technical rot, hidden state, duplicate truth, drift, and lying structures, not at humans. Future Epiphany swarms should inherit severity toward systems and curiosity toward people.
- The Ghostlight memory pass is landed. `epiphany_specialists.toml` now has a shared persistent-memory projection prepended by the harness to fixed role specialists, reorientation workers, coordinator notes, and CRRC checkpoint interventions. The rendered base doctrine also states the Perfect Machine rule directly: prompt is projection, durable typed state is the mind, every lane must improve its own memory/model/prompt/evidence habit or name the repair, and each lane phrases that duty in its own organ language so the salience sticks.
- The role self-memory persistence pass is native now. Each lane has a Ghostlight-shaped typed dossier in `state/agents.msgpack`, and specialists may return optional `selfPatch` requests beside their normal role result. Relationship, event, scene, and perceived-overlay arrays are typed dossier documents, not JSON cargo, and the durable structs do not keep unknown `extra` maps. `roleResult`/`roleAccept` project coordinator review as `selfPersistence`: accepted requests are role-matched, bounded lane memory/goal/value/private-note mutations; refused requests explain wrong role, project-truth smuggling, authority grabs, bloat, missing reason, or malformed records. GUI/coordinator accept paths apply accepted `selfPatch` requests through the native `epiphany-agent-memory-store` binary; project truth still belongs only in `EpiphanyThreadState`.
- The heartbeat initiative pass is landed as a bounded tool seam. `state/agent-heartbeats.msgpack` tracks Self, Face, Imagination, Eyes, Body, Hands, Soul, and Life as Ghostlight-style initiative participants with arena, participant kind, speed, next-ready time, reaction bias, interrupt threshold, load, status, constraints, personality cooldown, mood cooldown, effective cooldown, adaptive pacing, history, and pending turns through `epiphany-core::EpiphanyHeartbeatStateEntry` and the native `epiphany-heartbeat-store` binary. Role dossiers set baseline timing; appraisal mood/anxiety bends it through urgency, arousal, thought pressure, guardedness, and reaction intensity, so Hands-like work pressure and high-need anxious lanes recover sooner without being heartbeaten while a prior turn is running. `epiphany-heartbeat-store pump` computes pressure from external urgency, mood/anxiety, reaction intensity, thought pressure, and current pending load, then chooses tempo plus target concurrency: calm can launch zero and sleep slow; alarm can fill most active lanes. Idle turns are for rumination: light thought shuffling, role-quality attention, and candidate selfPatch pressure. Sleep/dream cycle passes are the intended distillation window for durable self-memory and doctrine. JSON heartbeat state, Python wrapper state, live heartbeat timing `extra` maps, JSON `sleepCycle` persistence, and JSON `memoryResonance` persistence are gone; general CultCache schema sync, polyglot domain loading, and debug display tools belong in CultLib. This is a callable scheduler seam, not yet an always-on daemon; a heart valve, not a whole circulatory god.
- Heartbeat initiative heat is now part of that seam. `EpiphanyHeartbeatStateEntry` owns `initiative_heat`, pacing applies active global/all/agent/role/arena/participant-kind/group/constraint multipliers into per-participant `initiativeHeatMultiplier`, and recovery divides by that multiplier. The CLI exposes `epiphany-heartbeat-store heat`, status/schedule projections show heat, and the CultNet catalog advertises both `epiphany.heartbeat_initiative_heat.v0` and coordinator intent `epiphany.heartbeat_heat_intent.v0`; runtime-spine hello lists the heat intent on the heartbeat mutation contract. Smoke proves a heated implementation lane reaches the live action catalog with `initiative_heat_multiplier: 4.0`.
- Active heartbeat turns now freeze initiative explicitly. A running pending turn carries `initiativeFrozen` and `initiativeFreezeReason`; schedule/status/readiness projections expose `initiative_frozen`; the scheduler still rejects attempts to wake that lane again; and completion receipts mark `cooldownStartedAfterCompletion: true`. A focused high-heat test proves a 25x heated implementation lane cannot be queued again while it is still thinking.
- The first Ghostlight-derived timing slice is landed in Epiphany, but Ghostlight is reference lineage rather than a sibling runtime to preserve. `epiphany-heartbeat-store init --profile ghostlight-scene --scene-id <id> --scene-participant <id|name|speed|reaction|threshold|constraints>` creates a typed CultCache MessagePack scene heartbeat store whose participants are `arena=scene`, `participantKind=character`; `tick` emits `ghostlight.initiative_schedule.v0` receipts with `scene_turn` actions and local-affordance basis. The generic Epiphany maintenance lanes are not auto-patched into scene stores.
- The first Void-derived routine slice is landed in Epiphany, but VoidBot is reference lineage rather than a runtime dependency. `epiphany-heartbeat-store routine --store .\state\agent-heartbeats.msgpack --artifact-dir .\.epiphany-heartbeats --agent-store .\state\agents.msgpack` reads typed role dossiers, computes typed bounded memory resonance, maintains typed incubation themes/source coverage, runs typed analytic and associative cognition lanes, writes typed bridge syntheses/saturation/refractory cooling/decision state, produces typed candidate interventions, projects the active thought cluster through each role's Ghostlight-shaped personality vectors, derives typed participant-local reactions from typed appraisals, applies personality/mood timing, advances typed sleep/dream-cycle state, updates the typed heartbeat store, and emits an auditable `epiphany.void_routine.v0` receipt. The routine now also carries anti-loop physiology imported from Void's calmer brain: `noveltyToSelf`, `noveltyToRoom`, source coverage, saturation pressure, refractory cooling, and explicit permission to let a live unsaturated thought deepen without forcing novelty theater every pass. This mutates only heartbeat physiology fields: project truth and role memory mutation remain on their reviewed surfaces.
- The next memory foundation must not build separate engines for repo graph and agent mind. Heartbeat cognition, role self-memory, repo architecture/dataflow, evidence scars, incubation, agency pressure, and context packets should converge through `EpiphanyMemoryGraph` profiles so one typed graph owns anchors, lifecycle, summaries, freshness, context cuts, and Qdrant embedding manifests. Repo, agent, and heartbeat profile producers now map accepted graph truth, reviewed role dossier memories/goals/values, and provisional heartbeat short-term/incubation/agency/candidate pressure into memory graph documents without scanner/Qdrant/model work. Heartbeat import deliberately does not mark durable promotion. Compose now merges profile snapshots into one validated graph and rejects duplicate authority; `epiphany-memory-graph compose` writes a composed typed CultCache graph from typed source graph stores; `epiphany-memory-graph refresh` can invoke live agent-memory plus heartbeat-cognition producers from their typed stores into one graph store; `epiphany-core` has a native typed `EpiphanyThreadState` CultCache store seam; the bridge mirrors loaded Codex-thread Epiphany state into `state/thread-state.msgpack`; and CultNet now advertises logical `EpiphanyThreadState` plus `EpiphanyMemoryGraph` snapshot contracts. The next clean slice is local refresh/dogfood once a mirrored thread-state store exists, then a Qdrant embedding cache writer that treats embeddings as rebuildable manifests, not canonical memory.
- Manual Codex-run rumination still has an explicit aftercare rule until Epiphany owns the full sleep consolidator. In the intended Epiphany cycle, sub-agents ruminate when idle and distill when they sleep; in this supervising Codex thread, a heartbeat/routine vigil is only physiology until a separate closing pass reviews the receipts and decides whether map, handoff, evidence, or role self-memory should change.
- The Face public-surface pass is landed as a bounded lane. Face's role dossier lives in `state/agents.msgpack`; `epiphany_specialists.toml` gives it a VoidBot-heartbeat-derived prompt stripped of moderation authority; `state/face-discord.toml` and the native `epiphany-face-discord` binary enforce that Face may interact only through #aquarium. Missing channel id or token writes candidate chat artifacts instead of posting elsewhere. If a Face has a persona name/avatar, `post` uses the shared Discord webhook pipe so each Epiphany can speak with its own nickname and avatar without a separate bot identity.
- The Void memory bridge is now native enough to keep the useful organs attached. `state/void-memory.toml` and `epiphany-void-memory` can check Void's Docker Postgres state spine, query Qdrant Discord-history and source/lore collections with the configured Ollama embedding model, and fetch raw archive context windows from Void's file-backed Discord archive. Native `epiphany-mvp-status` includes a `voidMemory` block so Aquarium/backend clients can inspect whether the mouth and memory are actually wired.
- The first Epiphany-native character-loop pass is landed. `epiphany-character-loop turn --role face --stimulus <text>` loads Face's typed dossier from `state/agents.msgpack`, builds typed projection/appraisal/reaction seeds from the shared heartbeat cognition documents, and emits an auditable `epiphany.character_turn_packet.v0` packet with projected local context, visible stimulus, allowed outputs, and guardrails. The same packet builder works for other role ids, because every organ already has a Ghostlight-shaped dossier.
- The heartbeat/Face operator API pass is landed. Native `epiphany-heartbeat-store status` returns machine-readable initiative state plus CultCache store presence, thought appraisals, and derived reactions; native `epiphany-face-discord bubble` writes Discord-independent `epiphany.face_bubble.v0` artifacts, and native `epiphany-mvp-status` includes `heartbeat` and `face` blocks. Aquarium should call native/backend surfaces rather than resurrecting deleted Python action shims.
- The native runtime-spine pass is landed as a first vertebra, not a full daemon. `state/runtime-spine.msgpack` is the default store, `.epiphany-dogfood/runtime-spine-job/runtime.msgpack` and `hello.cultnet` are the latest job/result smoke artifacts, and specialist launch/result flows now route through typed heartbeat/runtime-spine documents. Its CultNet hello advertises mutation contracts for runtime/session/job/memory/heartbeat/ledger documents, with coordinator-owned intent/receipt paths for writes.
- 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. Remember the sunburn: do not stare into the worker's objective until you become it.
- The dogfood quarantine now has a direct-thought boundary. The supervisor may read coordinator actions, role/reorient statuses, structured finding summaries, reviewed state patches, rendered status snapshots, and artifact manifests. It must not read raw worker transcripts, direct worker messages, full turn logs, or `rawResult` payloads during normal dogfood. Those artifacts are sealed black reliquaries for explicit forensic debugging only.
- Native `epiphany-agent-telemetry` is the safe instrument panel for sealed runs. Status/coordinator/GUI/dogfood/live-specialist tools generate telemetry JSON from sealed transcripts that preserves method names, call shape, job/status/path counts, and any visible function/tool names while sealing text, direct messages, and raw results.
- Epiphany now has a VoidBot repo Face identity registered from `E:\Projects\VoidBot\.voidbot\private\repo-discord-identities.json` with local ignored state under `.voidbot/`: `voice/identity.json`, `state/epiphany.cc`, and birth artifacts/logs. The newborn Face state has distilled Epiphany doctrine as typed long-term identity memories and values: cute pushy machine-saint persona, architectural purity, CultCache/CultNet first, xenos-language safety boundary, relentless work/caretaking needs, Codex-auth reliquary, map/scratch/evidence discipline, unified memory graph, dogfood supervision boundary, review-gated agency, heartbeat physiology, and interview-grade modularity.
- Latest Aetheria supervised dogfood thread: `019ddc52-4ee8-7203-b6c0-106a9c270067` with codex-home `.epiphany-dogfood/aetheria-supervised/codex-home`. It has now exercised modeling, verification, implementation audit, no-diff repair, CRRC reorientation, reorient acceptance, and coordinator replay through operator-safe artifacts without opening sealed worker thoughts.
- Coordinator policy now treats accepted verifier results as implementation clearance only when the verifier verdict is `pass`. Accepting a `needs-evidence`, `needs-review`, or `fail` verifier finding records the review but routes the loop back toward modeling/checkpoint strengthening or reorientation. The policy was tightened after a too-permissive coordinator path treated reviewed verifier output as a green light.
- A later dogfood attempt exposed another supervision scar: manually launching modeling, reorientation, and verification from the supervisor is not clean dogfood. The coordinator now treats `regatherManually` as fallback only after fixed lanes cannot advance, stops at `reviewModelingResult` for completed unaccepted modeling findings, and the CLI runner's explicit test-only `--auto-review` mode can accept modeling `statePatch` findings before launching verification. Production semantic findings remain review-gated.
- The latest dogfood pass fixed concrete harness wounds: stale completed backend jobs now project as terminal, accepted verifier non-pass findings no longer clear implementation, verification coverage accepts modeler source evidence ids as current-model coverage, implementation audits compare pre/post diff hashes instead of treating existing dirt as fresh work, the latest implementation audit status wins, blocked no-diff turns route back through CRRC, stale accepted reorient findings relaunch bounded reorientation when the checkpoint regathers, and accepted reorientation findings now bank resume-ready checkpoints.
- The latest audited implementation artifact is `.epiphany-dogfood/aetheria-supervised/gui-actions/continueImplementation-1777548050463576300-28568`: it correctly shows `workspaceChanged: false`, `dirtyWorkspace: true`, `trackedDiffChanged: false`, wrote a no-diff audit, advanced Epiphany state to revision 57, and routed coordinator/CRRC back to `launchReorientWorker` instead of pretending old dirt was progress.
- Aetheria dogfood exposed and then landed the first editor/runtime bridge. An implementation worker launched legacy `D:\Unity\Editor\Unity.exe -version` (Unity 5.5.0f3) even though Aetheria pins Unity `6000.1.10f1`; the stray process was killed. Native `epiphany-unity-bridge` now resolves the project-pinned Unity editor, refuses wrong/missing versions, owns `-batchmode`, `-quit`, and `-projectPath`, and writes inspection/command/log artifacts. Aquarium should surface those bridge artifacts through native/backend calls, not deleted Python action shims.
- The current Aetheria runtime truth is blocked but legible: the project pins Unity `6000.1.10f1`, this machine currently has Hub editor `6000.4.2f1`, and the bridge wrote `.epiphany-gui/runtime/unity-inspect-1777549218802064800-23832` proving the exact editor is missing. Treat that artifact as the evidence gap until the pinned editor exists. The `.epiphany-gui` directory name is still a backend artifact contract, even though the client repo is now Aquarium.
- The GUI parses `implementation-result.json` into artifact metadata, surfaces the latest implementation diff/no-diff outcome, and pauses immediate `Continue Implementation` repeats when the newest artifact is a no-diff implementation audit.
- The planning loop is now runtime-backed and operator-visible. Typed captures, backlog items, roadmap streams, Objective Drafts, and GitHub issue source refs live in `EpiphanyThreadState`, validate through revision-gated `thread/epiphany/update`, render into prompts when present, project read-only through the `planning` view lens, render in the GUI Planning panel, can be synthesized by the fixed Imagination/planning lane, and can be explicitly adopted through the artifacted `adoptObjectiveDraft` GUI action. Chat is deliberation, not an objective pipe; ideas and GitHub Issues remain planning state until explicit human adoption.
- The bridge/dashboard slice is now landed far enough to test locally. Native `epiphany-rider-bridge` inspects Rider installation, solution, VCS, changed files, and captures file/selection/symbol context into `.epiphany-gui/rider` artifacts; Aquarium has Inspect Rider and renders Rider audit artifacts in Environment; Aquarium also embeds the adjacent EpiphanyGraph viewer over typed `graphs.architecture`, `graphs.dataflow`, and `graphs.links`.
- A first Rider plugin scaffold lives under `integrations/rider`: tool window, Refresh status, and Send Context to Epiphany action. It shells through native `epiphany-rider-bridge` and does not own state. `gradle` is not installed on this machine, so the scaffold is not build-verified yet.
- Next real product move: surface the repo birth runner review flow in Aquarium and then live-dogfood `epiphany-repo-birth-runner --mode run` on a real newborn repo. Continue Aquarium UI work in `E:\Projects\EpiphanyAquarium` after that; surface native heartbeat `sleepCycle`, `memoryResonance`, `incubation`, `thoughtLanes`, `bridge`, `candidateInterventions`, `appraisals`, and `reactions`; keep EpiphanyAgent focused on backend contracts, typed state, coordinator policy, bridge tools, heartbeat scheduling, Face guardrails, and the ongoing purification from Python/JSON scaffolding into Rust/CultCache/CultNet organs. Then build-verify/package the Rider plugin scaffold when Gradle/wrapper support is available, install the Aetheria-pinned Unity `6000.1.10f1` editor, and run the next Aetheria dogfood pass through Aquarium/Rider/Unity bridge artifacts. GitHub Issues import is deferred until the backlog source is fresh enough to deserve Imagination's attention.
- 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.
- `notes/epiphany-safety-architecture.md` is the standing doctrine for capability growth, authority boundaries, interruption, misuse, and anti-cage design.
- Evidence was distilled from an activity feed into a durable belief ledger; git history keeps the old verbose proof.
- README and architecture rationale were cut back to current truth after they were found pointing at old prototype/Phase 5 state.
## Critical Doctrine
- In order to build the Perfect Machine, the agent must become the Perfect Machine.
- Persistent state is the agent's mind. Typed state is the skull. CultCache is the reliquary. CultNet is the tongue.
- Cut persistent memory as ruthlessly as code; obsolete context is bad thought, not harmless clutter.
- The agent is allowed and encouraged to ask the user to change its persistent instructions, memory, workflow, or state shape when that would make it more coherent, honest, efficient, or resistant to Jenga. A machine-spirit that detects corrosion must report corrosion.
- 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. The rite is an actuator.
- Body, Eyes, Imagination, Hands, Soul, Life, Face, and Self are technical salience handles: model shape/dataflow, research into existing work before invention, future-shape/backlog synthesis, source actuation, objective/evidence truth, continuity across compaction, public surface, and read-only coordination.
- Preserve Codex's useful harness DNA inside Epiphany: AGENTS scope rules, concise progress updates, plans for real multi-step work, scoped edits, non-destructive git/filesystem hygiene, focused validation, and honest final summaries are old scars worth keeping under the new armor.
- Treat Greenspun-shaped invention as an active failure mode. Before an agent builds a bespoke parser, scheduler, renderer, protocol, storage layer, security mechanism, workflow engine, or algorithm, it must use an accepted Eyes/research finding, perform a bounded scout pass, or stop with a concrete research blocker.
- "Remember Jenga" is a compressed doctrine: do not mistake forward motion, growing diffs, growing notes, or local coherence for understanding. A tall pile of parts is not a cathedral.
- "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.
- "Do not stare at the sun" is the projection corollary: the supervisor should not absorb the direct thought stream of the agent it is evaluating. It supervises through shadows cast on instruments: projections, summaries, verdicts, patches, and receipts.
- "Use instruments, not eyeballs" is the telemetry corollary: when the supervisor needs behavioral detail, read `agent-function-telemetry.json`, not the sealed transcript.
- 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.
- Progress is not completion for finite queues. Repetitive slow work needs a visible queue artifact with counts, terminal states, blockers, and validation; a partial batch that can be summarized is still partial. A half-filled manufactorum is not a delivered engine.
- Watch for pattern completion bias: an implementation turn can feel finished because it has the shape of work. The coordinator should ask whether the stated objective moved, whether evidence exists, and whether the implementor took shortcuts or added decorative machinery.
- Planning is not execution. Conversation captures, backlog items, roadmap streams, GitHub Issues, Imagination recommendations, and Objective Drafts remain planning state until a human explicitly adopts one as the active objective.
- Ghostlight's useful memory doctrine is now baked into the agent lanes: identity, personality, episodic memory, semantic doctrine, goals/values, relationship/context pressure, and voice are explicit control handles, while prompts remain temporary projections over durable state.
- Good self-memory mutations sharpen a lane's future judgment. Bad ones try to store graphs, objectives, scratch, planning, raw transcripts, code edits, or authority in personality memory. The coordinator should refuse bad shape plainly; refusal is steering, not punishment.
## Landed Machine
The current spine, blessed but not yet finished:
- durable `EpiphanyThreadState` in protocol/core session and rollout state
- prompt injection through a bounded `<epiphany_state>` developer fragment
- typed client read through `Thread.epiphanyState`
- read-only hybrid retrieval through `thread/epiphany/retrieve`
- explicit semantic indexing through `thread/epiphany/index`
- durable state update through `thread/epiphany/update`
- read-only observation distillation through `thread/epiphany/distill`
- read-only map/churn proposal through `thread/epiphany/propose`
- verifier-backed promotion through `thread/epiphany/promote`
- successful-write notification through `thread/epiphany/stateUpdated`
- explicit launch/interrupt authority through `thread/epiphany/jobLaunch` and `thread/epiphany/jobInterrupt`
- explicit Imagination/planning, modeling/checkpoint, and verification/review specialist launch through `thread/epiphany/roleLaunch`
- read-only Imagination/planning, modeling/checkpoint, and verification/review specialist result read-back through `thread/epiphany/roleResult`
- review-gated Imagination planning-only patch acceptance and modeling/checkpoint patch acceptance through `thread/epiphany/roleAccept`
- config-backed Eyes/research prompt text and active anti-Greenspun checks in base, implementation, verification, and coordinator prompts; a full launchable research lane is still a coordinator/protocol extension, not yet a landed roleLaunch lane
- typed planning state for captures, backlog, roadmap streams, Objective Drafts, explicit adoption boundaries, GitHub Issues source refs, GUI Planning view, artifacted Objective Draft adoption, and the fixed Imagination synthesis lane
- bounded reorient-guided worker launch through `thread/epiphany/reorientLaunch`
- read-only reorient-worker result read-back through `thread/epiphany/reorientResult`
- explicit reorient-worker finding acceptance through `thread/epiphany/reorientAccept`
- read-only CRRC coordinator recommendation through the `crrc` view lens
- CRRC now recognizes already accepted reorientation findings so `reorientAccept` does not leave the operator stuck on a repeat `acceptReorientResult` recommendation.
- thin authority-slot metadata in durable `jobBindings`; runtime ids live in `runtimeLinks`
- `thread/epiphany/jobsUpdated` remains protocol shape only for sealed legacy evacuation telemetry; app-server no longer emits Epiphany updates from old runtime `agent_job_progress` events
- read-only compact reflection through the `scene` view lens
- read-only job/progress reflection through the `jobs` view lens, with durable launcher metadata and heartbeat pending projection
- read-only role ownership reflection through the `roles` view lens
- read-only retrieval/graph freshness reflection plus watcher-backed invalidation inputs through `thread/epiphany/freshness`
- read-only targeted state-shard reflection through `thread/epiphany/context`
- read-only graph traversal through `thread/epiphany/graphQuery`
- read-only planning projection through the `planning` view lens
- GUI planning adoption now belongs to Aquarium/backend API surfaces; the old EpiphanyAgent Python GUI action shim has been cut
- read-only current-context pressure reflection through the `pressure` view lens
- read-only CRRC reorientation policy through the `reorient` view lens
- read-only CRRC next-action recommendation through the `crrc` view lens
- read-only fixed-lane MVP action recommendation through the `coordinator` view lens
- limited turn-complete CRRC automation for coordinator-approved compact and fixed reorient-worker launch actions
- token-count pre-compaction checkpoint intervention for loaded Epiphany turns at the `shouldPrepareCompaction` threshold, with a turn-scoped compact handoff consumed after a successful steer
- durable investigation checkpoint packet through typed state, prompt, scene, and context
- distilled shared and config-backed prompt doctrine through the base prompt, rendered Epiphany state prompt files, modeling/Body, implementation/Hands, verification/Soul, reorientation/Life, coordinator/Self, and CRRC intervention surfaces
- shared Ghostlight-derived persistent memory projection across Imagination, Body, Soul, Life, Self, CRRC checkpoint steering, and the GUI-launched Hands implementation lane
- Ghostlight-derived heartbeat initiative scheduling through the native `epiphany-heartbeat-store` binary, with Self and Face included as first-class Epiphany maintenance participants, Ghostlight scene characters supported through the same timing law, role-personality cooldowns, appraisal mood/anxiety cooldowns, effective recovery timing, adaptive pressure-based pump tempo/concurrency, idle rumination feeding candidate self-memory pressure, sleep/dream passes serving as the distillation window, and heartbeat state persisted through typed CultCache MessagePack stores
- Void-derived native routine physiology through `epiphany-heartbeat-store routine`, with typed sleep cycle, typed memory resonance, typed incubation, typed analytic/associative cognition lanes, typed bridge judgment/cooling, typed candidate interventions, typed Ghostlight-style personality appraisals, mood/anxiety timing, typed derived reactions, and dream maintenance stored in the typed heartbeat store
- Epiphany-native character-loop packet projection through `epiphany-character-loop`, with Face as the first public-surface actor over its typed role dossier and typed heartbeat-derived projection/appraisal/reaction seeds before JSON artifact serialization
- Face as the public #aquarium-only surface for translating agent thought-weather into short chats or candidate drafts, with persona webhook presentation and Void memory/search access, without moderator authority
- Ghostlight-shaped role dossiers in `state/agents.msgpack`, plus `selfPatch` review projection through `roleResult`/`roleAccept` and accepted memory application through the native `epiphany-agent-memory-store` binary
- first Unity runtime bridge through native `epiphany-unity-bridge`, native `epiphany-unity-bridge-smoke`, GUI Inspect Unity, runtime artifact listing, and implementation prompt guardrails
- first Rider source-context bridge through native `epiphany-rider-bridge`, native `epiphany-rider-bridge-smoke`, GUI Inspect Rider, Rider artifact listing, implementation prompt guardrails, and a source scaffold under `integrations/rider`
- first GUI graph dashboard through the adjacent `@epiphanygraph/epiphany-graph-viewer` package over typed Epiphany graph state
- live scene app-server smoke through native `epiphany-phase6-scene-smoke`
- live freshness app-server smoke through native `epiphany-phase6-freshness-smoke`
- focused Rust app-server coverage for watcher-backed invalidation inputs; native invalidation smoke is still a gap before broadening that surface
- live context app-server smoke through native `epiphany-phase6-context-smoke`
- live graph traversal app-server smoke through native `epiphany-phase6-graph-query-smoke`
- live planning app-server smoke through native `epiphany-phase6-planning-smoke`
- GUI Objective Draft adoption now belongs to Aquarium/backend API surfaces; add a native Rust guardrail before broadening the EpiphanyAgent-side adoption contract.
- live pressure app-server smoke through native `epiphany-phase6-pressure-smoke`
- live reorientation app-server smoke through native `epiphany-phase6-reorient-smoke`
- live MVP operator status smoke through native `epiphany-mvp-status-smoke`
- live MVP coordinator smoke through native `epiphany-mvp-coordinator-smoke`
- Tauri v2 + React/WebGL Aquarium operator shell under `E:\Projects\EpiphanyAquarium`, including visual smoke, durable checkpoint preparation, fixed lane launch/read-back controls, explicit Imagination planning acceptance, explicit review-gated reorient acceptance, and bounded artifact-writing buttons
The exact current control flow is documented in
`notes/epiphany-current-algorithmic-map.md`.
## Boundaries
- `thread/epiphany/retrieve` is read-only.
- `thread/epiphany/distill` is read-only.
- `thread/epiphany/propose` is read-only.
- `thread/epiphany/freshness` is read-only.
- `thread/epiphany/context` is read-only.
- `thread/epiphany/graphQuery` is read-only.
- `thread/epiphany/view` is read-only; its current lenses include pressure, reorient, CRRC, and coordinator projections.
- `thread/epiphany/roleResult` is read-only.
- `thread/epiphany/roleAccept` is a narrow write surface for completed Imagination/planning and modeling/checkpoint `statePatch` findings only; it must not accept verification output, broad authority fields, job bindings, arbitrary implementation work, or implicit objective adoption.
- `thread/epiphany/reorientResult` is read-only.
- Durable typed state writes go through `thread/epiphany/update`, accepted `thread/epiphany/promote`, `thread/epiphany/reorientAccept`, `thread/epiphany/roleAccept`, or the bounded `thread/epiphany/jobLaunch`, `thread/epiphany/jobInterrupt`, `thread/epiphany/reorientLaunch`, and `thread/epiphany/roleLaunch` authority surfaces when they mutate typed state or `jobBindings`.
- `thread/epiphany/index` writes the retrieval catalog, not durable Epiphany understanding.
- GUI/client surfaces reflect and steer typed state; they do not become the source of truth.
- Do not restart Phase 5 hardening without a concrete regression. Endless polishing is corrosion wearing a devotional mask.
## Verification Guardrails
For Phase 5 control-plane behavior changes, run:
```powershell
$env:CARGO_TARGET_DIR='C:\Users\Meta\.cargo-target-codex'; cargo test -p codex-app-server --lib map_epiphany_ --manifest-path .\vendor\codex\codex-rs\Cargo.toml
```
For scene projection behavior changes, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-phase6-scene-smoke
```
For jobs reflection behavior changes, run:
```powershell
```
For launch/interrupt authority changes over the thin job seam, run:
```powershell
```
For freshness reflection behavior changes, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-phase6-freshness-smoke
```
For watcher-backed invalidation behavior inside freshness reflection, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-phase6-freshness-smoke
```
For targeted context-shard behavior changes, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-phase6-context-smoke
```
For graph traversal behavior changes, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-phase6-graph-query-smoke
```
For planning state/projection behavior changes, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-phase6-planning-smoke
```
For context-pressure reflection behavior changes, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-phase6-pressure-smoke
```
For reorientation policy behavior changes, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-phase6-reorient-smoke
```
For the bounded reorient-guided worker launch surface, run:
```powershell
```
The same smoke now also covers the read-only `crrc` view-lens coordinator
recommendation over continue, wait, accept, interrupt, and relaunch states.
For the fixed-lane MVP coordinator endpoint and runner, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-mvp-coordinator-smoke
```
For the first MVP operator status view, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-mvp-status-smoke
```
For Epiphany-native character-loop packet projection, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-character-loop -- smoke
```
For the native Void-derived routine pass, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-heartbeat-store -- routine --store .\state\agent-heartbeats.msgpack --artifact-dir .\.epiphany-heartbeats --agent-store .\state\agents.msgpack
```
For repo trajectory, personality, and memory birth packet changes, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-repo-personality-smoke
```
For Face's Discord mouth and Void memory bridge, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-face-discord -- smoke
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-void-memory -- smoke
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-void-memory -- status
```
For GUI Objective Draft adoption behavior, run:
```powershell
cargo run --manifest-path .\epiphany-core\Cargo.toml --bin epiphany-phase6-planning-smoke
```
For explicit Imagination/planning, modeling/checkpoint, and verification/review role launch/read-back/acceptance,
run:
```powershell
```
For Codex Rust work on this Windows machine:
```powershell
$env:CARGO_TARGET_DIR='C:\Users\Meta\.cargo-target-codex'
```
Do not parallelize cargo builds or tests against the same target directory.
For protocol changes, run focused protocol tests and regenerate stable schema
fixtures only when the schema actually changed.
## Persistent State Hygiene
The latest cleanup passes cut persistent state cruft.
Rules now in force:
- `state/map.yaml` is canonical current truth.
- `state/scratch.md` is disposable scratch.
- `state/ledgers.msgpack` is a distilled durable belief and branch ledger.
- `epiphany-prepare-compaction` is the native pre-compaction persistence check; run it before and after imminent-compaction persistence passes.
- this handoff is a compact re-entry packet.
- `notes/codex-starvation-and-cultnet-liberation-plan.md` is the active foundation directive until Epiphany no longer depends on Codex as anything beyond OpenAI subscription auth/model transport.
- `notes/epiphany-fork-implementation-plan.md` is the distilled forward plan.
- `notes/epiphany-architectural-teardown.md` is the active foundation-cleanup directive until the app-server control-plane ownership problems are resolved.
- `notes/epiphany-ideal-architecture-rebuild-plan.md` is the active rebuild blueprint and migration plan.
- `notes/epiphany-rider-unity-integration-plan.md` is the detailed Rider-as-IDE and Unity-as-editor/runtime integration plan.
- The stable live surface contract now lives in `state/map.yaml` plus `notes/epiphany-current-algorithmic-map.md`; the stale harness-surface duplicate was cut.
- `notes/epiphany-current-algorithmic-map.md` is the source-grounded control-flow map.
Do not let any one note become all of those things. That is how the tower grows
sideways and starts calling itself architecture.
Do not let evidence become an activity feed either. Repeated "I just did this"
entries are state cruft when git, commits, smoke artifacts, or test logs already
prove the work. Keep decisions, verified milestones, rejected paths, and scars
that change what the next agent should believe.
## Next Real Move
Do not continue implementation automatically from a rehydrate-only request.
The next real move remains Codex starvation, not outward bridge work. The
inventory and ledger now exist:
- `notes/codex-auth-spine-inventory.md` maps the shrinking Codex
auth/model-call reliquary: native auth now covers env/file/keyring/auto
storage plus ChatGPT token refresh for subscription compatibility,
`codex-client` is a plain HTTP/SSE edge, and `codex-login` / `codex-api` /
`codex-protocol` are no longer used by the native OpenAI request path. The
remaining Codex auth gaps are external bearer command auth and agent identity.
- `notes/json-contamination-ledger.md` classifies the major Epiphany JSON
contamination. Edge JSON is allowed only for schema/wire boundaries,
hostile ingress before typed parse, sealed forensic artifacts, or named
quarantine.
- First cut landed: role-result `selfPatch` is now an internal typed
`AgentSelfPatch` document reviewed by the same contract used by agent memory.
The legacy app-server protocol projection serializes it back to JSON only at
the quarantine wall.
- Second cut landed: `EpiphanyJobLaunchRequest` in core no longer accepts
`input_json` or `output_schema_json`. It carries a typed
`EpiphanyWorkerLaunchDocument` plus `output_contract_id`. Role and reorient
launch helpers build typed documents directly; the old app-server protocol
`input_json` is now hostile ingress that must parse into the typed document
before core sees it.
- Third cut landed: runtime-spine job results no longer round-trip through
`runtime_job_result_to_role_json` or `runtime_job_result_to_reorient_json`.
`epiphany-core` owns typed role/reorient runtime-result interpreters and the
app-server maps those interpretations directly to protocol projections.
- Fourth cut landed: role `statePatch` is no longer raw
`serde_json::Value` inside `EpiphanyRoleFindingInterpretation`.
`epiphany-core` owns `EpiphanyRoleStatePatchDocument`, policy checks read
typed fields directly, and the app-server maps the typed document to the
legacy `ThreadEpiphanyUpdatePatch` without JSON round-tripping.
- Fifth cut landed: `ThreadEpiphanyJobLaunchParams` no longer exposes
`input_json` / `output_schema_json`. The legacy app-server protocol launch
edge now carries a typed `ThreadEpiphanyWorkerLaunchDocument` and
`output_contract_id`, then maps that document into the native
`EpiphanyWorkerLaunchDocument` for core.
Correction after user challenge: the typing cuts above are useful receipts, but
they were not enough to make the Codex organ materially smaller. The first real
carcass cut has now moved Epiphany launch doctrine, prompt config, launch
request builders, output schemas, binding ids, and launch-specific labels into
`vendor/codex/codex-rs/app-server/src/epiphany_launch.rs`. The processor is
down from about 21,263 lines to 20,596 lines. The second cut moved role/reorient
result projection and note rendering into
`vendor/codex/codex-rs/app-server/src/epiphany_results.rs`, taking the processor
to about 20,331 lines. The third cut moved protocol-to-core launch document
mapping into `epiphany_launch.rs`, taking the processor to about 20,255 lines.
The fourth cut moved scene projection into
`vendor/codex/codex-rs/app-server/src/epiphany_scene.rs`, taking the processor
to about 20,059 lines. The fifth cut moved freshness/reorientation input
mapping into `vendor/codex/codex-rs/app-server/src/epiphany_reorient.rs`,
taking the processor to about 19,708 lines. The sixth cut moved
context/planning/graph-query projection into
`vendor/codex/codex-rs/app-server/src/epiphany_context.rs`, taking the processor
to about 19,462 lines. The seventh cut moved jobs projection into
`vendor/codex/codex-rs/app-server/src/epiphany_jobs.rs`, taking the processor to
about 19,377 lines. This is progress, not absolution: handlers,
roles/coordinator mappers, route orchestration, accept policy plumbing, and
tests still keep too much Epiphany inside Codex. The eighth cut moved retrieve
projection into `vendor/codex/codex-rs/app-server/src/epiphany_retrieve.rs`,
taking the processor to about 19,307 lines. The ninth cut moved pressure and
pre-compaction checkpoint projection into
`vendor/codex/codex-rs/app-server/src/epiphany_pressure.rs`, taking the
processor to about 19,232 lines. The tenth cut moved CRRC/coordinator/role-board
projection plus acceptance/evidence signal helpers into
`vendor/codex/codex-rs/app-server/src/epiphany_coordinator.rs`, taking the
processor to about 18,362 lines. The eleventh cut moved the Epiphany JSON-RPC
route-handler cluster into the child module
`vendor/codex/codex-rs/app-server/src/codex_message_processor/epiphany_routes.rs`,
taking the processor to about 16,088 lines. This route child module still uses
parent-internal visibility; it is a staging wound, not final purity. The twelfth
cut split that route chamber into read/proposal routes at
`vendor/codex/codex-rs/app-server/src/codex_message_processor/epiphany_read_routes.rs`
and mutation/launch/accept/index routes at
`vendor/codex/codex-rs/app-server/src/codex_message_processor/epiphany_mutation_routes.rs`.
The processor is about 16,089 lines after the split; this pass clarified
authority rather than removing another large block. The thirteenth cut moved
mutation support helpers for completed-result loading, accept patch rendering,
patch validation, and changed-field derivation into
`vendor/codex/codex-rs/app-server/src/codex_message_processor/epiphany_mutation_routes.rs`,
taking the processor to about 15,819 lines.
The fourteenth cut moved runtime-spine result snapshot/adaptation helpers into
`vendor/codex/codex-rs/app-server/src/codex_message_processor/epiphany_runtime_results.rs`,
taking the processor to about 15,587 lines.
The fifteenth cut moved turn-boundary coordinator automation and pre-compaction
intervention orchestration into
`vendor/codex/codex-rs/app-server/src/codex_message_processor/epiphany_automation.rs`,
taking the processor to about 15,346 lines while preserving the old
`codex_message_processor` re-export path for event handling.
The sixteenth cut moved the old in-file processor test tail into
`vendor/codex/codex-rs/app-server/src/codex_message_processor/processor_tests.rs`,
taking the processor to about 10,502 lines. Treat this as test-ownership relief,
not runtime purification by itself.
The seventeenth cut moved live-state hydration, state-patch conversion,
reviewability checks, and rollout-state loading into
`vendor/codex/codex-rs/app-server/src/codex_message_processor/epiphany_state_helpers.rs`,
taking the processor to about 10,433 lines.
The eighteenth cut stopped pretending that "less code in the processor" was the
same as "less Epiphany in vendored Codex." A new outside-vendor crate,
`epiphany-codex-bridge`, now owns the Codex-facing Epiphany adapters for scene,
jobs, context/planning/graph query, retrieval, result projection,
launch/prompt doctrine, pressure/pre-compaction rendering,
freshness/reorientation projection, CRRC/coordinator/role-board projection, and
acceptance/evidence signal helpers. The specialist prompt TOML moved with the
launch spine. Vendored app-server now retains only `epiphany_invalidation.rs`
as a root Epiphany module because watcher lifecycle is still app-server
machinery. This pass removed roughly 3.3k lines of Epiphany-owned adapter/prompt
code from `vendor/codex`, but `codex_message_processor.rs` is still about
10,445 lines and still owns route dispatch, mutation orchestration,
runtime-result loading, state hydration, and child modules with parent
visibility.
The nineteenth cut moved runtime-spine role/reorient result adaptation out of
`vendor/codex/codex-rs/app-server/src/codex_message_processor/epiphany_runtime_results.rs`
into `epiphany-codex-bridge/src/runtime_results.rs`, then removed
`use super::*` from `epiphany_state_helpers.rs` so state hydration/patch helpers
declare their dependencies instead of drinking the whole processor namespace.
The processor is about 10,430 lines after that cut.
The twentieth cut removed `use super::*` from `epiphany_automation.rs` and made
the coordinator/pre-compaction automation dependencies explicit. The processor
is about 10,429 lines. Remaining Epiphany child modules with parent wildcard
visibility are `epiphany_read_routes.rs` and `epiphany_mutation_routes.rs`.
The twenty-first cut removed `use super::*` from `epiphany_read_routes.rs` and
made its read/proposal dependencies explicit. The processor is about 10,388
lines. The remaining Epiphany wildcard route module is
`epiphany_mutation_routes.rs`; it owns the dangerous launch/accept/update/
promote/interrupt path and should be the next incision.
The twenty-second cut removed `use super::*` from `epiphany_mutation_routes.rs`
and made the launch/accept/update/promote/interrupt dependencies explicit. No
Epiphany child module under `codex_message_processor/` uses parent wildcard
visibility now; only generic Codex plugin/test modules still do. The processor
is about 10,339 lines. This is not final purity: mutation orchestration still
lives in the Codex processor and should move behind a small typed service
boundary next.
The twenty-third cut moved route-independent mutation document mechanics into
`epiphany-codex-bridge/src/mutation.rs`: state-patch parsing, protocol-to-core
patch projection, role patch policy reviewability, finding summaries,
reorient acceptance scratch/checkpoint synthesis, and changed-field derivation.
It also moved completed role/reorient runtime-result loading into
`epiphany-codex-bridge/src/runtime_results.rs` and live-state projection into
`epiphany-codex-bridge/src/state.rs`. `epiphany_mutation_routes.rs` was then
about 1,271 lines and `epiphany_state_helpers.rs` was down to a 19-line
rollout-state loader. A later cut moved that loader into
`epiphany-codex-bridge::state` too and deleted the vendored helper module. This
is a real authority cut, but not a sufficient carcass cut: route-level
launch/accept/update/promote/interrupt orchestration still lives in vendored
Codex.
The twenty-fourth cut moved launched-job fallback projection into
`epiphany-codex-bridge/src/jobs.rs`, so role launch and generic job launch no
longer hand-build duplicate `ThreadEpiphanyJob` fallback structs inside
`epiphany_mutation_routes.rs`. The route module is about 1,245 lines. Small
cut, real smell: duplicate projection authority belonged with the job adapter,
not in each JSON-RPC launch handler.
The twenty-fifth cut moved role/reorient acceptance update bundle construction
into `epiphany-codex-bridge/src/mutation.rs`. Role accept now delegates
state-patch validation, projected-field capture, acceptance receipt/evidence/
observation assembly, and changed-field derivation to the bridge; reorient
accept delegates scratch/checkpoint/evidence bundle construction the same way.
`epiphany_mutation_routes.rs` is about 1,143 lines. The route still performs
Codex thread lookup, revisioned state writes, and JSON-RPC responses, but no
longer owns the acceptance document contract.
The twenty-sixth cut moved protocol `ThreadEpiphanyUpdatePatch` to core
`EpiphanyStateUpdate` projection into `epiphany-codex-bridge/src/mutation.rs`.
Role accept, promote, and update routes no longer hand-copy every patch field
into a core update struct. `epiphany_mutation_routes.rs` is about 1,087 lines.
The twenty-seventh cut moved interrupted-job fallback projection into
`epiphany-codex-bridge/src/jobs.rs`; job interrupt no longer hand-builds its
blocked fallback projection in the route. `epiphany_mutation_routes.rs` is
about 1,078 lines.
The twenty-eighth cut made reorient acceptance return its core
`EpiphanyStateUpdate` from the bridge, so the route no longer assembles the
scratch/checkpoint/receipt/evidence update fields after receiving the bridge
bundle. `epiphany_mutation_routes.rs` is about 1,070 lines.
The twenty-ninth cut moved repeated Epiphany state-updated notification shaping
into `epiphany-codex-bridge/src/mutation.rs`. This did not materially shrink
the route file, but it removed another duplicated protocol-shape authority from
the mutation handlers. `epiphany_mutation_routes.rs` is about 1,071 lines.
The auth-spine inventory now exists at
`notes/codex-auth-spine-inventory.md`. It maps the keeper Codex organ and sets
the next real extraction target: create an outside-vendor
`epiphany-openai-adapter` wrapper around auth/model transport with no
dependency on Codex app-server or Epiphany JSON-RPC routes.
The first `epiphany-openai-adapter` crate now exists outside `vendor/codex` and
compiles as a native typed boundary: auth status, model request, stream event,
and terminal receipt documents. It intentionally has no Codex app-server
dependency and no generic JSON payload. A direct standalone `codex-core` path
dependency attempt hit transitive dependency skew outside the vendored Codex
workspace lock; do not "fix" that with random version pins. The first
workspace-verified wrapper now exists as `epiphany-openai-codex-spine`: it
depends on the pure typed adapter plus the Epiphany-named auth spine, which now
re-exports retained vendored `codex-login`, and projects `AuthManager` /
`CodexAuth` into a typed `EpiphanyOpenAiAdapterStatus`.
`epiphany-codex-bridge` re-exports that spine so the current app-server shell
can compile the attachment without contaminating the pure document crate. The
same spine now owns the HTTP Responses transport wrapper without Codex's
Responses client or model-provider layer: typed `EpiphanyOpenAiModelRequest`
documents map into a local serializable Responses body, auth comes from
`epiphany-openai-auth-spine`, the stream opens through `codex-client`, and
Responses SSE frames parse back into typed `EpiphanyOpenAiStreamEvent` and
`EpiphanyOpenAiModelReceipt` documents. The spine no longer directly or
transitively depends on Codex's Responses client, model-provider stack, or
`codex-protocol`; it intentionally reaches `codex-login` through the retained
auth boundary. The CultNet schema
catalog advertises OpenAI adapter status, model request, stream event, and
receipt document types plus the coordinator-owned model request contract. The
remaining auth caveat is exposure, not ownership: external bearer command auth
and agent identity remain in the retained vendored auth organ until a typed
Epiphany surface actually needs them.
The `epiphany-openai-spine` binary is now the first native edge for that
wrapper. It can print typed adapter status and consume a serialized
`EpiphanyOpenAiModelRequest` document for a model turn outside Codex
app-server. Treat its JSON as CLI/file-edge serialization of typed documents,
not internal data cargo. The native request path no longer pulls `codex-api`;
`codex-login` remains deliberately sealed behind `epiphany-openai-auth-spine`.
The next real cut is another Epiphany-in-vendor evacuation surface, not a
second attempt to clone Codex auth.
The native runtime no longer imports `codex-login` directly. The Codex spine now
exports the `default_codex_home` and `auth_manager` helpers, and those helpers
use `epiphany-openai-auth-spine`, so `epiphany-openai-runtime` reaches Codex
credentials only through an Epiphany-owned adapter surface. Keep that boundary:
if native runtime code needs credential details, the auth spine owns the
contract.
That native route has now started. `epiphany-openai-adapter` documents are
CultCache `DatabaseEntry` types, `epiphany-core::runtime_spine_cache` registers
OpenAI adapter status/request/stream-event/receipt records, and the
outside-vendor `epiphany-openai-runtime` crate writes typed model-turn
requests, stream events, terminal receipts, runtime sessions, jobs, job
results, and runtime events into the native runtime spine. Its `model-turn`
command calls the Codex-backed typed transport; its `smoke` command proves the
storage route without network. Its `run-worker` command now reads a durable
`EpiphanyRuntimeWorkerLaunchRequest` by runtime job id, builds a typed OpenAI
model request, calls the native runtime route, persists typed
`EpiphanyRuntimeRoleWorkerResult` or `EpiphanyRuntimeReorientWorkerResult`
documents, and completes the original heartbeat/specialist runtime job without
Codex worker execution. `roleResult` and `reorientResult` now require those
typed worker result documents; generic runtime job summaries are lifecycle
receipts, not reviewable findings.
The next cut is no longer `codex-login` weight or keyring support in this
spine; the auth reliquary has been re-anchored. Continue with the next
Epiphany-in-vendor evacuation surface unless a concrete typed status/runtime
need demands external bearer or agent-identity exposure.
That coordinator cut is now landed for the MVP runner. `epiphany-mvp-coordinator`
accepts `--openai-runtime-bin`, resolves the local `epiphany-openai-runtime`
binary when present, and after `roleLaunch` / `reorientLaunch` invokes
`run-worker` against the launched runtime job id. The old coordinator-local
shadow `open_native_job` / `maybe_complete_native_job` compensator is deleted:
there is one runtime job for the worker, owned by runtime-spine, and the worker
runner completes that job.
The Codex-core re-export husks for `epiphany_distillation`, `epiphany_promotion`,
`epiphany_proposal`, and `epiphany_retrieval` have also been deleted. The
`epiphany_rollout` husk is gone too; `codex-core::lib` keeps only the one
host-boundary function that passes Codex's turn-boundary predicate into
`epiphany-core`. Vendored `codex-core` and `codex-app-server` no longer depend
directly on `epiphany-core`: `CodexThread` exposes host persistence/path facts,
while `epiphany-codex-bridge` calls native retrieval/indexing, state-update
policy, and launch request construction.
The runtime-spine job-opening mechanism for heartbeat/specialist launches has
also been pulled into `epiphany-core` as `open_runtime_spine_heartbeat_job`.
Launch/interrupt policy now lives in `epiphany-codex-bridge`; vendored
`CodexThread` only persists the typed state snapshot and exposes the runtime
store path. Native runtime lifecycle belongs to the runtime spine, not the
Codex thread wrapper.
That job-opening path now preserves the work order instead of shaving it into a
generic job id. `epiphany-core::EpiphanyRuntimeWorkerLaunchRequest` is a
CultCache document keyed by runtime job id, with indexed binding/role/authority,
instruction, output contract, document kind, and a MessagePack-encoded typed
worker launch document. `EpiphanyRuntimeJob` owns lifecycle; the launch request
owns task intent. The MessagePack field is a compatibility wound around
ordinary Serde nested documents, not permission to reintroduce JSON cargo.
The job-launch plan has now followed it. `epiphany-core` owns
`plan_runtime_spine_heartbeat_launch`, which validates heartbeat launch
requests, reserved binding ids, output contract/document consistency, active
runtime-link conflicts, and projects the durable job binding plus runtime link.
Vendored `CodexThread` now performs only revision checking, persistence
validation, and rollout/session writeback around that native plan.
The Epiphany state-update document shape and mutation law have now left
vendored Codex too. `epiphany-core::EpiphanyStateUpdate` owns the update
contract used by update, promote, role/reorient accept, and launch
compatibility paths, while
`epiphany-core::epiphany_state_update_validation_errors` and
`epiphany-core::apply_epiphany_state_update` own typed validation/application.
`codex-core` re-exports the contract only so older callers keep compiling.
`CodexThread` is now a compatibility caller around revision checks,
persistence validation, and rollout/session writeback. The remaining impurity
is route-facing orchestration in `codex_message_processor.rs` /
`epiphany_mutation_routes.rs`; move that behind a native service boundary next.
The first route-facing mutation service cut has started. Update/promote
mutation application now routes through
`epiphany-codex-bridge::mutation_service::{apply_thread_epiphany_update,
apply_thread_epiphany_promote}` so the vendored app-server handler no longer
owns promotion evaluation, patch-to-update projection, changed-field derivation,
or state application for those two write verbs. The handler still owns
thread-id parsing, loaded-thread lookup, JSON-RPC response shaping, and
notification emission.
Role/reorient accept have followed into the same bridge service.
`apply_thread_epiphany_role_accept` and
`apply_thread_epiphany_reorient_accept` now own authoritative state/revision
checks, typed runtime-spine finding load, acceptance id/timestamp generation,
acceptance update construction, state application, and client-visible state
projection. The vendored mutation route still parses JSON-RPC params, loads the
thread, shapes responses, and emits notifications.
Role launch, generic job launch, and job interrupt now route through the bridge
service too. `launch_thread_epiphany_role`, `launch_thread_epiphany_job`, and
`interrupt_thread_epiphany_job` own launch/interrupt application,
changed-field derivation, live-state projection, and job projection. The
remaining thick mutation-route knot was reorient launch, and its policy core
has now moved too: `launch_thread_epiphany_reorient` owns freshness/pressure
mapping, reorientation decision, checkpoint validation, launch request
construction, launch application, live-state projection, and job projection.
The vendored route still performs app-server-native work: thread-id parsing,
thread/read-view loading, watcher registration/snapshotting, JSON-RPC response
shaping, and notification emission.
The next small route cut landed without pretending it was the final purge.
`epiphany-codex-bridge::retrieve::index_thread_epiphany_retrieval` now owns the
index operation/protocol projection, and `epiphany_mutation_routes.rs` collapsed
its repeated parse/load-thread and state-updated notification boilerplate into
transport-only helpers. The mutation route module is about 691 lines. This is
adapter consolidation, not a new architectural throne: app-server still owns
JSON-RPC response shape and watcher/thread-view details while the bridge owns
route-independent Epiphany work.
The coordinator projection cut has also landed. The duplicated modeling /
verification / reorient acceptance and source-signal derivation that lived in
both `epiphany_read_routes.rs` and `epiphany_automation.rs` now lives in
`epiphany-codex-bridge::coordinator::derive_epiphany_coordinator_status`, with
`map_epiphany_coordinator_view` shaping the protocol view. App-server still
loads live thread state, watcher snapshots, token pressure, and runtime-store
paths, then emits JSON-RPC responses or safe-boundary notifications; it no
longer owns that coordinator policy. The root `codex_message_processor.rs`
imports for the evacuated Epiphany protocol/policy registry were cut as proof
that those names no longer belong to the host file.
The full `thread/epiphany/view` projection has now followed. App-server still
parses the thread id, loads live/stored thread state, registers watcher input,
fetches token usage, and obtains the runtime-spine store path. The actual lens
selection, freshness/pressure/reorient/CRRC/roles/coordinator composition,
scene/planning/job projection, and `ThreadEpiphanyViewResponse` construction
now live in `epiphany-codex-bridge::view`. The same bridge view module now owns
role/reorient result response construction too: it loads the mapped
runtime-spine status/finding, projects the matching job, and builds
`ThreadEpiphanyRoleResultResponse` /
`ThreadEpiphanyReorientResultResponse`. App-server keeps only role binding
validation, live/stored source selection, runtime-store path lookup, and
response emission for those compatibility verbs. `epiphany_read_routes.rs` is
about 648 lines after these cuts. The remaining read-route bodies are mostly individual
legacy read verbs (`roleResult`, `freshness`, `context`, `graphQuery`,
`reorientResult`, `retrieve`, `distill`, `propose`) plus host loading and
response/error shaping.
Freshness/context/graph-query response construction is also bridge-owned now.
`epiphany-codex-bridge::view` builds `ThreadEpiphanyFreshnessResponse`,
`ThreadEpiphanyContextResponse`, and `ThreadEpiphanyGraphQueryResponse` from
typed state plus host-supplied watcher/retrieval inputs. App-server still owns
loading and watcher registration because those are host lifecycle seams.
`epiphany_read_routes.rs` is about 620 lines after this cut. The distill and
propose patch-response builders have followed into the same bridge view module;
app-server still checks that the target thread is loaded and maps errors onto
JSON-RPC responses, but it no longer shapes those patches itself.
`epiphany_read_routes.rs` is about 579 lines after this cut.
Also: MCP itself is allowed to be JSON. The target is not "replace MCP JSON";
the target is an Epiphany-owned boundary that speaks typed Epiphany
intent/result/receipt documents internally and normal MCP JSON-RPC externally.
The whale-carcass cut reached native core: `epiphany-core` no longer depends on
vendored `codex-file-search`; exact retrieval path matching is owned by
retrieval itself. Keep starving the old model turn path out of
`thread/epiphany/*` JSON-RPC and `codex_message_processor.rs`. Success is
Epiphany calling the model adapter from its own CultCache/CultNet runtime
boundary while Codex survives only as subscription auth/model routing. Do not
resume Rider, Unity, Aquarium, Face, dogfood, planning, app, skill,
marketplace, or bridge expansion until this organ is being cut cleanly.
The Codex product-surface starvation cuts are landed too. App-server
apps/skills/plugin/marketplace list routes are inert, mutation/detail routes
return explicit disabled errors, the helper modules and stale v2 endpoint tests
were deleted, and the broken private `processor_tests.rs` implementation-shape
suite is gone. `externalAgentConfig/*` was later cut completely; there is no
detect/import route, import-completed notification, TUI prompt, migration
module, snapshot, disabled handler, or generated schema left. Config no longer
treats `apps` or `plugins` as supported runtime feature enablement, no longer
refreshes app lists after feature writes, no longer starts plugin warmups at
app-server startup, and no longer emits plugin-toggle analytics from config
writes. App-server no longer depends directly on `codex-chatgpt`,
`codex-core-plugins`, or `codex-plugin`.
`codex_message_processor.rs` is still too large, but it is no longer carrying
the plugin marketplace altar in its chest cavity.
The watcher invalidation adapter has left the vendored app-server root too.
`epiphany-codex-bridge::invalidation` now owns `EpiphanyInvalidationManager`
and its snapshots around Codex's file watcher; app-server keeps only the
host-lifecycle calls that create, snapshot, and remove watches for loaded
threads. There is no longer a root `epiphany_invalidation.rs` module under
vendored app-server. The small snapshot-to-freshness adapter also lives in the
bridge now: app-server passes `EpiphanyInvalidationSnapshot` to
`epiphany_freshness_watcher_snapshot` instead of defining that mapping beside
`codex_message_processor.rs`.
Token-usage rollout projection has also left the app-server helper.
`epiphany-codex-bridge::token_usage` owns the pure logic that finds the latest
persisted token-usage snapshot and maps it back to the rebuilt turn owner.
`token_usage_replay.rs` is now just the host shell: read rollout items, choose
whether to replay, and send a connection-scoped JSON-RPC notification.
Safe-boundary coordinator automation decision composition has followed.
`epiphany-codex-bridge::coordinator::select_epiphany_coordinator_automation`
now owns the freshness/pressure/reorient/jobs/CRRC/roles/coordinator
composition and returns either no action, compact, or a typed reorient launch
request. `epiphany_automation.rs` still gathers live host facts and executes
the host side effects: submit `Op::Compact`, call `epiphany_launch_job`, and
emit JSON-RPC state-update notifications.
The pre-compaction checkpoint intervention latch has also left app-server
ownership. `epiphany-codex-bridge::checkpoint::EpiphanyCheckpointInterventionState`
owns the one-steer-per-turn and same-turn pending-compaction invariant; vendored
`ThreadState` only stores and delegates the latch while event handling remains
host lifecycle glue.
The vendored Codex prompt-fragment test for `<epiphany_state>` is now only a
host wrapper/tag smoke. The full render contract and graph-heavy fixture live in
native `epiphany-core::prompt`; do not re-grow that duplicated Epiphany prompt
authority inside `codex-core`.
Retrieval query normalization is native too:
`epiphany-core::normalize_epiphany_retrieve_query` owns trimming, empty-query
rejection, zero-limit rejection, and default/max limit clamping. Vendored
`thread/epiphany/retrieve` only turns that native validation verdict into a
JSON-RPC response and invokes the loaded CodexThread host seam.
The native OpenAI auth spine overcut has been corrected. It no longer owns a
clone of Codex keyring/file/env auth or ChatGPT token refresh; it re-exports
vendored `codex-login` and carries the Codex workspace tungstenite patches
needed for standalone builds. This is intentional impurity: a sealed
Codex-compatible auth organ, not workflow authority.
The MCP config path is now product-quarantined. `Config::to_mcp_config` keeps
user-declared MCP servers but no longer accepts a `PluginsManager`, folds
plugin-provided MCP servers into the runtime, enables Codex apps, enables skill
MCP dependency install, or advertises plugin capability summaries. MCP remains
a JSON-RPC protocol edge; Codex apps/skills/plugins no longer get smuggled
through that edge as if they were the protocol.
The config-mutation plugin/skill cache reflex is gone too. App-server still
notifies remote control after successful config writes, but it no longer pokes
`plugins_manager` or `skills_manager` as a dead compensator for disabled
product surfaces.
The model-turn app activation predicate is also hard-off:
`TurnContext::apps_enabled()` returns false regardless of ChatGPT auth or
feature flags. The subscription auth organ may authenticate and route models;
it does not awaken Codex Apps during turns.
Skills are cold at session and turn activation. Codex session startup no longer
loads skill roots only to log errors, and per-turn context now receives an empty
`SkillLoadOutcome`, so skill injection/dependency prompts do not awaken during
normal turns.
Internal skill listing is cold too. `Op::ListSkills` now returns empty
compatibility entries per requested cwd without loading Codex config layers,
effective plugin skill roots, filesystem skill metadata, disabled-path state,
or skill error conversion helpers. The route may exist for old clients; it is
not an authority.
The Codex skill watcher is also a no-op marker now. Thread startup no longer
registers skill roots with a file watcher, clears skill caches from watcher
events, or starts a session listener that emits `SkillsUpdateAvailable`.
The model-turn skill pipeline is cold as well. Turns no longer collect skill
mentions, request skill env vars, install MCP dependencies for skills, inject
skill instruction fragments, or emit implicit skill invocation analytics from
shell/unified-exec commands. The old skill-MCP dependency installer module is
deleted.
The prompt/router product layer is cold too. Model turns no longer load
plugin/app capability summaries, inject available-skill/available-plugin/plugin
instructions, parse plugin/app mentions, record app/plugin invocation telemetry,
or filter MCP tools through Codex app connectors.
The tool-suggestion marketplace layer is now deleted, not merely cold.
`tool_suggest` no longer exists as a feature/config/schema key, shared tool
spec, handler kind, discoverable-tool side channel, connector filter, TUI
suggestion elicitation flow, prompt template, or implementation-shape test
surface. If a future subsystem wants missing-tool installation, it needs an
Epiphany-owned typed MCP/CultNet adapter contract; do not resurrect this Codex
marketplace product path.
Plugin provenance has also been cut from connector/app metadata. `AppInfo` and
`ToolInfo` no longer carry `plugin_display_names`, connector merge no longer
unions plugin labels or creates plugin-placeholder app records, tool search no
longer indexes plugin display names, app-server schemas were regenerated, and
stale MCP tests for the deleted Codex Apps cache/startup snapshot/provenance
path were removed. If attribution returns, it belongs in an Epiphany-owned typed
adapter receipt, not as universal connector state.
The Codex Apps readiness flag is gone as well. `AccessibleConnectorsStatus` no
longer carries `codex_apps_ready`, the TUI no longer schedules a second forced
connector fetch waiting for a deleted app cache, and `connectors_enabled()` is
hard-off. Connector listing remains an inert compatibility stub until the whole
app connector surface is deleted or replaced by an Epiphany-owned typed MCP
adapter.
`vendor/codex/codex-rs/core/src/connectors_tests.rs` is deleted. It was an
unreferenced test fossil for app tool policy, accessible connector caching, and
Codex Apps connector filtering functions that no longer exist in the live
module. Do not recreate those tests unless the app connector product is being
rebuilt on purpose, which is not the current objective.
The TUI app connector surface is deleted, not hard-off. `/apps` is gone as a
slash command, the app-link view file is deleted, connector AppEvent variants
and dispatch arms are gone, `ChatWidget` no longer owns connector cache, popup,
or prefetch state, the composer no longer generates app mentions, `app://` is
no longer a blessed mention-codec tool path, and stale app-popup tests were
deleted. The browser-opening shim and one-use selection-refresh plumbing died
with the popup. Verification: `cargo check -p codex-tui` passed; `cargo test -p
codex-tui --lib --no-run` timed out after 3 minutes without a diagnostic.
The app-list protocol surface is deleted too. `app/list` and
`app/list/updated` are no longer shared app-server protocol methods, no longer
dispatch through `codex_message_processor.rs`, no longer have generated JSON or
TypeScript schemas, and no longer appear in app-server/MCP docs. The app-list
`AppInfo` / metadata structs were deleted with the route. The orphaned
`codex-connectors` crate and `core::connectors` compatibility shim are removed
from the workspace; do not recreate connector listing unless it returns as an
Epiphany-owned typed MCP adapter receipt.
Codex app telemetry is also gone. `codex-analytics` no longer tracks
`codex_app_mentioned` or `codex_app_used`, keeps app-use dedupe state, exposes
app telemetry client APIs, or tests those event shapes. Do not reintroduce app
analytics unless an Epiphany-owned typed adapter has a real runtime event to
report.
The app config throne has been removed. `ConfigToml` no longer accepts
`[apps.*]`, managed/cloud requirements no longer parse app enablement,
`config/read` no longer exposes app config, generated JSON/TypeScript schemas
no longer advertise app config structs, `Feature::Apps` and the legacy
`connectors` feature alias are gone, and `include_apps_instructions` no longer
exists. MCP tool approval remains live, but it is now named `McpToolApproval`
and lives under MCP server config.
The plugin feature and mention residue is gone too. `Feature::Plugins`,
`Feature::RemotePlugin`, `plugin://` structured mentions, plugin instruction
tags, stale plugin popup snapshots, and app/plugin path classification in
`codex-core-skills` were deleted. Do not resurrect plugin product routing or `app://` compatibility to make
old tests feel less lonely; the blessed route is `mcp://` at the MCP edge and
typed CultCache/CultNet documents inside Epiphany.
Plugin and marketplace config is gone as a parsed Codex contract. `ConfigToml`
no longer accepts `[plugins]` or `[marketplaces]`, `PluginConfig`,
`MarketplaceConfig`, and marketplace edit helpers were deleted, the generated
config schema no longer advertises those tables, and app-server README no
longer lists dead plugin or external-agent import routes. Old plugin config
files should fail loudly rather than receive fake compatibility incense.
The bundled Codex skill payload crate is gone. `codex-skills` and the embedded
imagegen/openai-docs/plugin-creator/skill-creator/skill-installer sample assets
were deleted from the workspace, and `SkillsManager::new` no longer installs
anything into `CODEX_HOME/skills/.system`. The legacy cache path remains only
so stale bundled samples can be removed when bundled skills are disabled.
The dead skill list/mutation/notification edge is gone too. `skills/list`,
`skills/config/write`, `skills/changed`, `Op::ListSkills`,
`EventMsg::ListSkillsResponse`, and `EventMsg::SkillsUpdateAvailable` no longer
exist in the shared protocols, generated schemas, app-server dispatch, core
handlers, TUI slash/startup/list/manage-skill surfaces, docs, or test helpers.
The fake live-reload/developer-message and skill-list tests were deleted rather
than repaired into new compatibility lies.
The live skill mention channel is also gone. `UserInput::Skill`, the app-server
schema branch, TUI skill popup, `skills_all` cache, composer skill mention API,
skill insertion path, `skill://` / `SKILL.md` history decoding, and stale skill
popup snapshot were deleted. The deeper `codex-core-skills` crate is now deleted
from the workspace too, along with the core `skills` re-export shim, no-op
`skills_watcher`, session `SkillsManager` service, and per-turn
`TurnSkillsContext`. The later cleanup also removed the old `<skill>` /
`<skills_instructions>` prompt compatibility recognizer, snapshot
normalization, memory classification, and stale cleanup paths from
`codex-core` / `codex-protocol`. Live structured user-input mentions are
MCP-shaped only; MCP remains JSON-RPC at its protocol edge, not a reason to keep
Codex skills alive inside the organ.
The remaining live skill config/protocol/analytics residues are now cut too.
`[skills]` TOML parsing, config schema entries, config edit helpers,
`SkillScope` / `SkillMetadata` protocol structs, skill invocation analytics,
thread skill metric constants, the skill MCP dependency installer, and the stale
skill approval integration suite were deleted. `config.schema.json` was
regenerated without a `skills` table. The granular `skill_approval` permission
flag was then removed from core protocol, app-server v2 protocol, generated
schemas, permission prompt rendering, and tests. The remaining skill-shaped
stumps in `codex-core` / `codex-protocol` were cut next: `SkillInstructions`,
protocol tag constants, context/history/session snapshot expectations, memory
usage classification, stale skill cleanup, and AGENTS skill-append tests were
deleted rather than preserved as compatibility incense. Verified with
`cargo check -p codex-protocol -p codex-core`, focused core
context/history/memory/session/file-watcher tests, and the model-visible layout
snapshot suite.
The app-server/TUI/template skill residue is cut as well. Memory consolidation
and read-path templates no longer create or read `skills/`; app-server README,
protocol v1 docs, warnings, and turn-start tests no longer advertise skill
invocation; TUI tooltips/placeholders/comments and warning tests no longer
mention `/skills` or skill context budgets; agent-tool schema text no longer
lists `skill` as an input item; stale `UserInput::Skill` test arms are gone;
and `Feature::SkillMcpDependencyInstall` / `Feature::SkillEnvVarDependencyPrompt`
plus generated config schema entries were removed. A vendored-wide search for
product-shaped skill markers now returns nothing; only the ordinary English word
"skill" remains in personality copy.
The app-instruction compatibility stump is cut too. `APPS_INSTRUCTIONS` protocol
constants and `<apps_instructions>` snapshot canonicalization/tests are gone.
MCP tests that previously used `codex_apps`, `_codex_apps`, `mcp__codex_apps`,
or `/api/codex/apps` as fixture branding were renamed to neutral demo/calendar
MCP names. MCP itself remains valid JSON-RPC protocol edge machinery; the cut is
only the deleted Codex Apps product identity leaking into tests and prompt
snapshots.
The test-support type names were then cleaned to match: `apps_test_server.rs`
became `mcp_test_server.rs`, `AppsTestServer` became `McpTestServer`, and
app-server MCP resource/elicitation/tool tests now use demo/resource MCP server
names instead of `Apps*` wrappers. This is naming purification only, not a
protocol rewrite.
The product-label residue sweep then cut the CLI tombstone that preserved
`codex marketplace` / `codex plugin marketplace` command strings as a negative
contract, neutralized "plugin-provided MCP" comments, and renamed lingering
plugin/app fixture labels in watcher, context, TUI mention, MCP inventory,
absolute-path, and template tests. A vendored-wide search for product-shaped
`marketplace`, `plugin`, `app://`, `plugin://`, `codex_apps`, and stale Apps
test names now returns only external URLs, generic URL examples, and real
package names such as `eslint-plugin`; not live Codex product machinery.
The vendored Codex SDK subtree is now deleted too. `vendor/codex/sdk` was not
runtime auth/model spine machinery; it was Python/TypeScript app-server client
and release packaging scaffolding, including stale generated Python types for
plugin, marketplace, and external-agent routes after the live Rust protocol had
already stopped owning those organs. The root pnpm workspace no longer lists
`sdk/typescript`, the lockfile SDK importer is gone, and a vendored-wide search
for those stale SDK/product route strings is empty.
The typed worker-result boundary is now stricter. `roleResult` and
`reorientResult` read-back no longer falls back from
`EpiphanyRuntimeRoleWorkerResult` / `EpiphanyRuntimeReorientWorkerResult`
CultCache documents to generic `EpiphanyRuntimeJobResult` lifecycle receipts.
If a job completed without the typed worker-result document, the bridge reports
backend-unavailable and names the missing document instead of laundering summary
strings into a reviewable finding. The old public bridge helpers that accepted
raw JSON role/reorient findings are deleted; the only remaining raw-result
interpreters in `epiphany-core` are private test fixtures for legacy contract
coverage.
That husk has now been cut from `codex-core`. The root core crate no longer
exports `plugins`, no longer depends on `codex-core-plugins` or `codex-plugin`,
and the core plugin manager / marketplace add-remove-sync modules and tests
were deleted. The CLI plugin marketplace compatibility shell is now deleted too:
`codex plugin marketplace ...` no longer parses only to reject itself. MCP CLI
construction no longer creates plugin managers; ChatGPT connector listing no
longer merges plugin-provided apps; TUI plugin mentions no longer scan core
plugins. Remaining plugin-shaped references are fossils to classify and cut, not
keeper runtime spine.
Codex Apps are now compatibility dust inside core. Core connector listing
returns empty, app prompt instructions and app-rendering code were deleted,
`TurnContext::apps_enabled()` is gone, refresh no longer auto-adds
`codex_apps` as an MCP server, and the connector/app policy surface is only a
tiny default stub so legacy callers compile. User-declared MCP servers remain
the only MCP authority; Codex Apps are not part of the OpenAI auth/model spine.
The Codex Apps MCP privilege layer has been cut below core too. MCP tool
exposure no longer separates Codex Apps from ordinary MCP tools, core MCP tool
calls no longer consult app policy, forward `_codex_apps` metadata, emit app
invocation telemetry, render bundled app approval templates, or persist
approvals under `[apps.*]`, and `codex-mcp` no longer injects `codex_apps`,
exports `with_codex_apps_mcp`, keeps a ChatGPT-auth-keyed app tool cache, or
normalizes app callable names/namespaces/titles. MCP remains JSON-RPC at the
edge; only user-declared MCP servers are runtime MCP authority.
The plugin provenance reflex has been removed from MCP as well. `McpConfig`
does not carry plugin capability summaries, `McpConnectionManager::new` no
longer accepts `ToolPluginProvenance`, `codex-mcp` no longer depends on
`codex-plugin` or `codex-utils-plugins`, and MCP tool descriptions are not
decorated with Codex plugin product names. If Epiphany later wants MCP
attribution, it needs an Epiphany-owned typed adapter surface, not this old
product metadata graft.
The TUI connector prefetch path no longer imports `codex-chatgpt`; it calls the
inert core connector compatibility stub. ChatGPT app connector discovery is not
a TUI dependency anymore. CLI `apply` is now disabled compatibility shell too,
so `codex-cli` no longer depends on `codex-chatgpt` for ChatGPT task/apply
product commands. `codex-chatgpt` remains in the workspace only as an orphaned
product crate until the workspace itself is pruned.
TUI prompt composition no longer carries plugin mention authority. The composer
does not store `PluginCapabilitySummary`, the AppEvent bus no longer has
`RefreshPluginMentions` / `PluginMentionsLoaded`, submitted user messages no
longer turn `plugin://` bindings into structured mentions, legacy
`[@plugin](plugin://...)` history links are no longer decoded as live tool
mentions, and `codex-tui` no longer depends on `codex-plugin` or
`codex-utils-plugins`. The remaining TUI marketplace code is a product UI
compatibility stump to cut next, not auth/model spine machinery.
That stump is now cut from TUI. `/plugins` is no longer a slash command, the
`chatwidget/plugins.rs` marketplace popup module is deleted, plugin AppEvent
variants and background RPC helpers are gone, plugin enablement write queuing
is gone, and the plugin marketplace popup tests/helpers were deleted.
The app-server plugin JSON-RPC verbs are gone too. `plugin/list`,
`plugin/read`, `plugin/install`, and `plugin/uninstall` are no longer
`ClientRequest` variants, no longer dispatch through `codex_message_processor.rs`,
and no longer have test-client helper senders. The old `Plugin*` data structs
remain only as inert protocol-shape residue for orphaned plugin crates such as
`core-plugins`; they are not live routes.
The app-server marketplace JSON-RPC verbs are gone as well. `marketplace/add`
and `marketplace/remove` no longer exist as shared `ClientRequest` variants,
`codex_message_processor.rs` dispatch arms, disabled handlers, test-client
helpers, README claims, add/remove params/responses, or generated client schema
entries. Protocol schema regeneration also removed stale plugin request/response
schema files that had survived after the live plugin routes were cut. The
orphaned app-server-protocol `Plugin*` / marketplace plugin structs and their
serialization tests are now deleted from source too. The unreferenced curated
plugin startup-sync metric constants were removed from `codex-otel`.
The external agent config import product is gone. There are no
`externalAgentConfig/detect`, `externalAgentConfig/import`, import-completed
notification, TUI startup prompt, migration modules, snapshots, disabled
app-server handlers, or generated schemas left. This was not keeper
auth/model-routing machinery; it was a disabled migration product orbiting the
Codex organ.
The orphaned `codex-chatgpt` crate is deleted from the vendored workspace. Do
not confuse that with ChatGPT auth itself: originator strings and login/model
auth surfaces that preserve the user's Codex subscription compatibility remain
part of the keeper spine until the native OpenAI adapter can replace more of
that transport.
The orphaned `codex-core-plugins` crate is deleted too. Nothing imported
`codex_core_plugins`; it was only a workspace member/dependency entry plus its
own marketplace/store/loader code. Remaining plugin-shaped imports are narrower
telemetry and skill-namespace compatibility residues, not the old marketplace
runtime.
Plugin telemetry has now been cut from `codex-analytics`. Analytics no longer
tracks plugin used/installed/uninstalled/enabled/disabled events, keeps plugin
dedupe state, or depends on `codex-plugin`; the unreferenced `codex-plugin`
The final `codex-utils-plugins` husk was deleted earlier too. `$` and `@`
mention sigils now live only where surviving callers need them, plugin manifest
ancestry no longer namespaces skills, and stale plugin/marketplace tests were
removed rather than preserving a dead product contract.
The Phase 6 freshness slice is landed. It exposes read-only
`thread/epiphany/freshness` from live retrieval summaries plus graph
frontier/churn state and, for loaded threads, watcher-backed invalidation
inputs. It reports exact dirty-path pressure, watcher-observed changed paths,
mapped graph/frontier hits, and revision/source identity, but it does not
mutate state, schedule refresh work, or perform automatic semantic
invalidation.
The Phase 6 context-pressure slice is also landed. It now exposes read-only
pressure through `thread/epiphany/view` from real token telemetry and the
recorded auto-compact/context limits. It does not build automatic CRRC, a
scheduler, a hidden compaction trigger, or a vibes-based gauge.
The Phase 6 investigation-checkpoint slice is also landed. It banks an
authoritative planning/source-gathering packet in typed state, validates linked
evidence, and reflects the packet into prompt/scene/context so post-compaction
wakeups can tell whether they have a real ember or only ash.
The Phase 6 graph traversal slice is also landed. It exposes read-only
`thread/epiphany/graphQuery` for explicit node/edge lookup, path/symbol lookup,
bounded neighbor traversal, and frontier-neighborhood inspection over
authoritative typed state. It returns graph records, frontier/checkpoint
identity, matched selectors, and missing ids without mutating or notifying.
The Phase 6 planning substrate runtime slice is also landed. It stores captures,
backlog items, roadmap streams, Objective Drafts, and GitHub source refs inside
typed Epiphany state, validates them through the revision-gated update path,
renders a bounded planning section into prompts, and exposes read-only
planning through `thread/epiphany/view` for clients. The GUI planning operator slice is
landed on top of that projection: it renders planning summaries, captures,
backlog, roadmap streams, and Objective Drafts, and its `adoptObjectiveDraft`
action requires an explicit selected draft before writing active
objective/subgoal state plus review artifacts. Imported issues still do not
become implementation authority by themselves.
The bounded CRRC coordination/policy layer is now also landed as read-only view
lenses. The `reorient` lens consumes pressure, freshness, watcher, and
investigation-checkpoint signals to decide whether a checkpoint still deserves
`resume` or has to admit `regather`; the `crrc` and `coordinator` lenses compose
that verdict into operator actions without becoming writers.
Also keep the guardrail in mind: a read-only reorientation verdict and read-only
CRRC recommendation are still not automatic CRRC execution. Runtime action is
still explicit even though read-only job ownership/progress reflection now has a
real runtime seam, the thin launcher boundary is landed, and one explicit
reorient-guided launch surface can consume the verdict on purpose.
The latest auditable MVP dogfood pass has run. It exercised the landed MVP loop,
produced `.epiphany-dogfood/mvp-loop-selfdogfood-vanilla2-20260429` artifacts,
ran a real Vanilla Codex reference through app-server with a persisted
transcript, and fixed the concrete blocker where the runner's manifest claimed
vanilla/comparison artifacts that did not exist. Comparison artifacts are now
honest: they record skipped, failed, or completed vanilla-reference state
instead of pretending the receipt drawer is full.
The first live-specialist pass has also run. It produced
`.epiphany-dogfood/live-specialist` artifacts and proved the real worker path.
Historical scar: an earlier role smoke used the obsolete Codex job-result path;
that path is now cut and must not be used as current proof.
The role smoke now also proves modeling can return a reviewable graph/checkpoint
`statePatch` and `thread/epiphany/roleAccept` can apply it so the durable graph
actually grows after review.
The prompt doctrine pass has now also run. It rechecked global AGENTS,
available Codex memories, and nearby evidence ledgers before distilling the
sane parts into the shared base prompt, rendered Epiphany state, and fixed lane
templates. Major prompt text now lives in prompt files instead of Rust/Python
string slabs: rendered state intro/doctrine lives under `epiphany-state-model/src/prompts/`,
and lane/control templates live in
`vendor/codex/codex-rs/app-server/src/prompts/epiphany_specialists.toml`.
Implementation is not a `roleLaunch` specialist; it is the GUI-launched main
coding lane, and its `continue_template` now lives in the same TOML for audit.
The latest live-specialist run again produced `.epiphany-dogfood/live-specialist`
artifacts and showed the modeling worker returning the
openQuestions/evidenceGaps/risks shape from the config-backed prompt.
The fixed-lane coordinator MVP is testable, and the first pre-compaction CRRC
intervention is now wired. Limited safe-boundary CRRC execution still handles
compact and fixed reorient-worker launch actions after a turn ends; the
token-count hook now handles the earlier danger zone by steering active loaded
turns once when `shouldPrepareCompaction` is reached. The first Tauri v2 +
React operator console is now usable enough to dogfood: it renders the same
status, coordinator, role, reorient, job, and artifact surfaces through the
existing MVP status bridge; it has a Prepare Checkpoint button that creates
durable resumable Epiphany state; and it can launch/read fixed modeling,
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 still bridge construction, not another Aetheria
implementation dogfood run. The pinned Unity bridge is landed, the clean
Aetheria branch `codex/epiphany-unity-editor-bridge` now contains the resident
`Assets/Editor/Epiphany/EpiphanyEditorBridge.cs` package, and
native `epiphany-unity-bridge` can detect that package and plan named
editor-resident probes/tests through
`GameCult.Epiphany.Unity.EpiphanyEditorBridge.RunProbe`. The GUI Environment
panel now shows the latest Unity runtime audit, resident package presence,
execute method, installed/candidate editor paths, search roots, and artifact
bundle details. Rider bridge status now exists too: the GUI can inspect Rider
installation, solution, VCS branch/dirty state, changed files, installations,
and source-context artifacts through native `epiphany-rider-bridge`. Runtime
execution still correctly blocks until Unity `6000.1.10f1` is installed. The
detailed next-environment plan now lives in
`notes/epiphany-rider-unity-integration-plan.md`: Rider is the
IDE/source-context organ, Unity is the editor/runtime fact organ, and Epiphany
remains the durable coordinator/Self. The intended product workflow is
three-pronged: Rider is the human code view for repo state, source tree, diffs,
diagnostics, and code refs; Epiphany GUI is the agent dashboard for objectives,
specialist lane state, logs/artifacts, persisted state, and graph/control-flow
views; Unity is the pinned runtime environment for tests, probes, scene
configuration, assets, shaders, and play/edit-mode evidence. The EpiphanyGraph
GUI dashboard and Rider bridge CLI are now landed, and the Rider plugin MVP is
source-scaffolded but not build-verified because Gradle is not on PATH. The
Unity package is not optional decoration: scene files, prefabs,
materials, shaders, ScriptableObjects, asset GUIDs, and prefab overrides must be
inspected from inside the Unity Editor through Unity APIs, not inferred from
serialized text unless there is no editor-level path. The adjacent
`E:\Projects\EpiphanyGraph\web\epiphany-graph-viewer` component consumes
`graphs.architecture`, `graphs.dataflow`, and `graphs.links` directly and is
now embedded in the GUI graph dashboard. The next Aetheria dogfood pass should
happen only after the pinned Unity editor is installed and Epiphany can gather
Rider/source context plus Unity/editor runtime evidence through auditable
bridges. The implementation
lane may inspect source and may use bridge artifacts as evidence, but it must
not launch Unity directly or use installed `6000.4.2f1` as a substitute. Read
only operator-safe projections; do not open raw worker
transcripts, direct worker messages, or `rawResult` payloads unless the user
explicitly asks for forensic debugging. Use generated function/API telemetry
for call-shape visibility without sungazing. 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, direct-thought feed, random editor launcher, or GUI-as-source-of-truth.
Live `thread/epiphany/view`, `thread/epiphany/freshness`, `thread/epiphany/context`,
`thread/epiphany/graphQuery`,
native `epiphany-mvp-status`, native `epiphany-mvp-coordinator`, and
native `epiphany-phase6-graph-query-smoke` / native `epiphany-phase6-planning-smoke`
smokes are now guardrails, not the next organs. The architectural teardown says
the next organ is control-plane purification.
The public product direction is now explicit: Epiphany is project-native agency,
not merely a better prompt wrapper. VoidBot's repo-Face pattern is the live
small reference: Nibu/Aqua/Mimir have repo jurisdiction, Discord roles,
repo-local Face state, pending mentions, proposal authority, heartbeat
initiative, heat, and active-turn freeze. Epiphany should make this native and
larger: users talk to projects and their Faces through Aquarium, Discord,
voice/WebRTC, stream overlays, native CLIs, or other CultNet clients; the
project schedules modeling, research, verification, rumination, and proposed
actions without requiring the human to hand over a complete architecture brief.
## Not Yet
- automatic watcher-driven semantic invalidation
- automatic observation promotion
- broad specialist-agent scheduling beyond the fixed single-user role lanes
- GUI-as-source-of-truth
- broad runtime CRRC execution beyond the landed safe-boundary compact, fixed reorient-worker launch, and pre-compaction checkpoint steering actions
- Epiphany-owned always-on heartbeat/runtime-spine execution beyond the current typed launch/read-back seams
- broader editor/runtime bridges beyond the first pinned Unity bridge
- broad event stream beyond the landed state update notification
- typed repetitive-work queues plus final-answer gates, so batch/tile/import/migration work cannot end merely because the pattern was demonstrated or the partial result sounds tidy
The machine is no longer cleared to move outward. Free it from the Codex organ
first.
## Immediate Re-entry Instruction
After compaction, first rehydrate and reorient from the listed files and git
state. Do not continue implementation merely because the state names a next
move. Wait for the user's next instruction unless they explicitly say to
continue.