From 6dab234769805c992fa0b04119c315d4dbfbfa33 Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Mon, 17 Aug 2026 22:24:11 +0200 Subject: [PATCH] Record dormant authority deletion --- notes/epiphany-current-algorithmic-map.md | 23 +++++++++++++++------ notes/epiphany-fork-implementation-plan.md | 2 +- notes/fresh-workspace-handoff.md | 19 +++++++++++------ state/ledgers.msgpack | Bin 628039 -> 628606 bytes state/map.yaml | 6 +++--- 5 files changed, 34 insertions(+), 16 deletions(-) diff --git a/notes/epiphany-current-algorithmic-map.md b/notes/epiphany-current-algorithmic-map.md index 1196cf76..3346341a 100644 --- a/notes/epiphany-current-algorithmic-map.md +++ b/notes/epiphany-current-algorithmic-map.md @@ -4991,12 +4991,23 @@ validity, mutation shape, or admission; those remain with the concrete Body and Proposal families. The shared vocabulary is therefore DRY without becoming a generic work registry. -The next source audit found that claim-repair is not a live request family. +The next source audit found that claim-repair was not a live request family. `commit_repo_model_claim_challenge` and `commit_repo_model_claim_repair_request` have no production caller, no source constructs a `RepoModelClaimChallenge`, and no acceptance test proves the chain. -Its aggregate-thread launch branch is dormant scaffolding. The deletion line is -the repair request/binding/context/export and their carrier fields; a future -Eyes contradiction must earn a new typed external-evidence obligation through a -real producer, current-work projection, terminal context, and Mind admission -proof rather than inheriting this unowned anatomy. +Its aggregate-thread launch branch was dormant scaffolding. Exact `20dd66c8` +deletes the repair request/binding/context contracts, runtime registration and +carriers, coordinator validation/binding writer, reasoning projection, result +cargo, exports, and OpenAI lowering. A source guard over Rust/TOML paths finds no +surviving family symbol. The Eyes claim-challenge document remains because its +exact claim hash independently suppresses unsafe planning. A future Eyes +contradiction must earn a typed external-evidence obligation through a real +producer, current-work projection, terminal context, and Mind admission proof. + +That deletion pass also falsified the initial launch-CAS proof. Body and +Proposal launchers first projected work, then opened a second cache snapshot; +the latter could observe a just-committed binding, increment the attempt +ordinal, and launch a second live worker. The owner now derives launchability +and ordinal from the same pulled cache snapshot used to construct its exact CAS. +Concurrent Proposal launch convergence passes 20/20 stress iterations; a live +attempt cannot be converted into retry authority by a convenience preflight. diff --git a/notes/epiphany-fork-implementation-plan.md b/notes/epiphany-fork-implementation-plan.md index 9d57127c..c479494e 100644 --- a/notes/epiphany-fork-implementation-plan.md +++ b/notes/epiphany-fork-implementation-plan.md @@ -231,7 +231,7 @@ Cut in this order: 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, exact launch binding, 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. 5. **Continuation vocabulary landed at `e404c105`:** Body and Proposal share one pure `EpiphanyModelingContinuationAction`; their semantic requests, projections, validators, and admission owners remain separate. -6. Delete the dormant claim-repair request/launch scaffold. It has no production challenge producer, request caller, or acceptance proof, so migrating it would manufacture authority. Reintroduce repair only from a real typed external-evidence obligation. +6. **Dormant claim-repair authority deleted at `20dd66c8`:** no request/binding/context schema, runtime carrier, coordinator branch, result cargo, export, or model lowering survives. The independent Eyes challenge fact remains. The same pass fixed two-snapshot Body/Proposal launch derivation and stress-proved single Proposal launch 20/20. 7. Migrate frontier-verdict, Research, Verification, planning, and reorientation acceptance from aggregate state patches and generic role lanes to family-owned current-work projections, exact job identities, diff --git a/notes/fresh-workspace-handoff.md b/notes/fresh-workspace-handoff.md index 0919b133..49712659 100644 --- a/notes/fresh-workspace-handoff.md +++ b/notes/fresh-workspace-handoff.md @@ -360,12 +360,19 @@ Exact `e404c105` removes the duplicate Body/Proposal continuation enums. One `EpiphanyModelingContinuationAction` now names Launch, Wait, and Review; each family retains its own request, projection, validity rules, and admission owner. -Source inspection then falsified the assumption that claim-repair is a live -family: its exported request/launch surface has no production challenge -producer, request caller, or acceptance proof. Delete that dormant aggregate- -thread scaffold rather than migrating it. Then migrate the live frontier- -verdict Modeling chain onto exact Soul/route/request authority and the shared -continuation vocabulary. Continue with Research, Verification, +Exact `20dd66c8` deletes claim-repair's request/binding/context schemas, runtime +carriers, coordinator launch branch, reasoning projection, result cargo, +exports, and OpenAI lowering. The Eyes claim-challenge fact remains because it +still blocks unsafe planning. No Rust/TOML production symbol for the dormant +family survives. During verification, the concurrent Proposal launch test +exposed two-snapshot attempt derivation; Body and Proposal launchers now +revalidate launchability and ordinal from the exact cache snapshot used by the +CAS. Proposal convergence passes 20/20 stress iterations. + +Migrate the live frontier-verdict Modeling chain next onto exact +Soul/route/request authority and the shared continuation vocabulary. Delete its +accepted-at ordering, aggregate prompt construction, and role-lane review path. +Continue with Research, Verification, planning, and reorientation; then delete the aggregate schema/transaction. Run the source guards and fresh-store concurrency/decision-context suite. Only after that may Model Atlas Gate 1 restart from a new external root. Keep the current fresh and diff --git a/state/ledgers.msgpack b/state/ledgers.msgpack index 7af2600ba2662d1ce79f7b83affa64e21cca1f47..0db3659c0ec5012decc0eb39f68624786e2ee4c0 100644 GIT binary patch delta 574 zcmX|-ziSjh6vy3*KXRnAP|F8Gs=M30&1MZ35MoFnL=yBWE#zh9-R;2a%w}fx;#OB! zSPJUp{s#*QrVz2$|4Mut7K`r;%rKwt=gpt5+kd}pUp!|NiOzm!D~p=EG!fIDRrslS!JbuO^!h*5$|k z)^g+M9f|;HB4wV7J&>d+kc3bWNb5>80fa_X4jomf95_0!$%j~DZA1YxER}BHqEMRn zE}$~X%x|76BdH=@7;)5)?>M4Bt;x)Z--=}z!ONO)(~}p+;BD;$!MsK%VP}cjFl9-PB|(MWb9*b;x?k9#H(2??26$#=6Q4R;S&tezYe`NmFetk; zT-u%DnbImW1F%jigL(kS0*42$z!&HUtRWC6+RhHX5C6f!ngzKz8TM~&SR+m1GyxwR zv78Fz+CszHhn8u(c^2>H53>QB@FyKS2UnY*c$RD@&UV&sKljt8zC(>bB;)aoj;%Tl Y4^ug7XTVEnhcEf-xs@rlW=T2v2d{X@f&c&j delta 69 zcmeyjPVM+AwG9%C+y;hL#uib>7&xb>Y*uD0WMtgcJe8?^Dib3RgJ@