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

Move Epiphany acceptance bundles to bridge

Browse source
This commit is contained in:
Meta Vens 2026-05-13 03:46:48 +01:00
commit 9fcf2004e6
5 changed files with 204 additions and 132 deletions
Download patch file Download diff file Expand all files Collapse all files

15
notes/fresh-workspace-handoff.md
View file

@ -515,14 +515,23 @@ 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.
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.
Continue with the actual whale-carcass cut: carve route-level mutation
orchestration into explicit typed bridge/service calls, starting with launch
response/notification construction and acceptance update bundles. Success is a
Continue with the actual whale-carcass cut: carve remaining route-level mutation
orchestration into explicit typed bridge/service calls, starting with generic
update/promote patch-to-state-update construction and launch response/
notification shaping. Success is a
visibly smaller processor and less mutation authority in Codex, not merely
nicer payload names or another adapter reliquary. Do not resume Rider, Unity,
Aquarium, Face, dogfood, planning, app, skill, marketplace, or bridge expansion