Record routing cargo hard cut

This commit is contained in:
Meta Vens 2026-08-24 06:27:35 +02:00
commit cec8a0db1c
5 changed files with 53 additions and 18 deletions

View file

@ -350,6 +350,13 @@ Cut in this order:
deleting duplicate effect-event provenance, an always-empty relationship,
and an always-empty raw-result reference. Mind/runtime epochs are v10/v26;
old writable stores refuse without migration.
Exact `ffd91c20` deletes three more derived fields: the fixed Research role
from Eyes packets, the fixed Epiphany Persona agent from queued mentions,
and the unread Resident Self retention timestamp. Their owning request/
context, Persona queue/turn request, and chained retention digest remain.
Eyes packet v2, Persona mention v2, Resident Self state v3/retention head v1,
and runtime v27 form the hard cut. Model Atlas remains intact for its first
live inter-swarm collaboration run; component proofs are not acceptance.
3. **Baseline transaction landed at `9f7b164f`; operator routing at `587c56d2`; Resident continuation and keyed acceptance at `478fb923`:** baseline Body Modeling is now thread-free from unresolved Body obligation through Launch/Wait/Review and exact Mind admission. Resident and operator callers consume the same family projection and acceptance owner. Thread ID remains immutable pass provenance only.
4. **Proposal Modeling landed at `d1b031cb`:** its immutable request, worker launch, runtime attempt/result, and `Modeling.proposal_frontier` commit now own Launch/Wait/Review and admission. The aggregate launcher refuses proposal cargo; the old selector, validator, context builder, and generic-launch hint are deleted. Body and Proposal share only the exact-envelope launch CAS invariant, not a mutable family registry. Exact `b0a4978d` deletes the later duplicate launch-binding document entirely; the worker launch is the sole launch owner.
5. **Continuation vocabulary landed at `e404c105` and was named truthfully at `fc5d1a4a`:** concrete pass families share one pure `EpiphanyAgentPassContinuationAction`; their semantic requests, projections, validators, and admission owners remain separate.