Record keyed Verification ownership cut
This commit is contained in:
Meta Vens
parent
fc5d1a4a84
commit
7501564f0a
5 changed files with 85 additions and 24 deletions
|
|
@ -4984,8 +4984,9 @@ gone. Verification proves concurrent launch convergence, exact Wait/Review,
|
|||
keyed admission, no thread-state envelope, core 564/564, Self policy 26/26, and
|
||||
the coordinator-runtime feature build.
|
||||
|
||||
Exact `e404c105` collapses the duplicated Body and Proposal Launch/Wait/Review
|
||||
enums into `EpiphanyModelingContinuationAction`. This type owns only the common
|
||||
Exact `e404c105` collapsed the duplicated Body and Proposal Launch/Wait/Review
|
||||
enums; exact `fc5d1a4a` names the now-shared vocabulary truthfully as
|
||||
`EpiphanyAgentPassContinuationAction`. This type owns only the common
|
||||
attempt-continuation vocabulary. It does not own request selection, result
|
||||
validity, mutation shape, or admission; those remain with the concrete Body and
|
||||
Proposal families. The shared vocabulary is therefore DRY without becoming a
|
||||
|
|
@ -5097,3 +5098,42 @@ omitted: later fields can occupy the wrong schema positions. CultCache exact
|
|||
named maps. `prepare_mind_document` is the single Mind boundary, and objective,
|
||||
Body, and Research writers use it. This is an encoding owner, not a second state
|
||||
format or compatibility path.
|
||||
|
||||
## Keyed frontier Verification lifecycle (2026-08-18)
|
||||
|
||||
Exact `fc5d1a4a` removes Verification from aggregate coordinator behavior. A
|
||||
successful exact Hands commit publishes its `HandsCommitReceipt` and derived
|
||||
`RepoFrontierVerificationRequest` in one CAS transaction. The request seals the
|
||||
route, exact frontier document, Hands authority, intent, review, patch receipt,
|
||||
command receipt, and commit receipt. The full RepoModel projection remains
|
||||
audit cargo and cannot turn unrelated graph work into a conflict.
|
||||
|
||||
- Owner: `project_current_work` derives Verification Launch/Wait/Review;
|
||||
`launch_current_frontier_verification_work` publishes the deterministic
|
||||
attempt; `accept_frontier_verification_result` alone admits the decision under
|
||||
`Soul.verification`.
|
||||
- Inputs: one exact routed frontier, one complete authorized Hands consequence,
|
||||
immutable Verification request and launch, terminal runtime result, sealed
|
||||
reasoning basis, and exact decision context.
|
||||
- Outputs: one keyed `EpiphanyMindVerificationAuditDocument`, one typed
|
||||
`SoulVerdictReceipt`, one deterministic `RepoFrontierModelingRequest`, and one
|
||||
atomic `EpiphanyMindCommitReceipt`.
|
||||
- Derived state: role boards, events, accepted-at timestamps, latest result
|
||||
slots, generic Verification status, and coordinator thread are display or
|
||||
transport projections only.
|
||||
- Forbidden writers: generic role launch/acceptance, aggregate thread updates,
|
||||
accepted-at comparisons, dynamic Hands telemetry prompt appenders, and the
|
||||
model cannot create, suppress, review, or admit Verification. The runtime,
|
||||
not model JSON, supplies request and route identity from the sealed launch.
|
||||
- Shared paths: operator, status, and Resident consume the same current-work
|
||||
projection and the same admission owner. Runtime fulfillment and archival use
|
||||
the same typed `FrontierVerification` request reference.
|
||||
- Cut line: the aggregate Soul-verdict acceptance prerequisite, latest Hands
|
||||
consequence selector, prompt-time request writer, and generic Verification
|
||||
launch/acceptance fallback are deleted. `EpiphanyAgentPassContinuationAction`
|
||||
shares only Launch/Wait/Review vocabulary across concrete pass families.
|
||||
- Verification: exact replay returns the original commit receipt; an unrelated
|
||||
keyed node commit between inference and admission merges; an exact-frontier
|
||||
change refuses admission with the copied store byte-identical. Core 559/559,
|
||||
OpenAI runtime 23/23, coordinator runtime 18/18, and both all-target checks
|
||||
pass.
|
||||
|
|
|
|||
|
|
@ -18,9 +18,9 @@ earned OpenAI-compatible authentication or model-transport capability.
|
|||
heartbeat physiology, Persona, and CultMesh integration. Its coordinator and
|
||||
status surfaces still retain a legacy persisted `EpiphanyThreadStateEntry`;
|
||||
that aggregate is an obsolete live authority and currently blocks fresh keyed
|
||||
stores from coordinating. Body, Proposal, and frontier-verdict Modeling have
|
||||
been removed from that authority; Research acceptance, Verification,
|
||||
planning, reorientation, and generic coordinator presence remain.
|
||||
stores from coordinating. Body, Proposal, frontier-verdict Modeling,
|
||||
Research, and Verification have been removed from that authority; planning,
|
||||
reorientation, and generic coordinator presence remain.
|
||||
- Native binaries expose coordinator, status, state, runtime, memory, daemon,
|
||||
Persona, repo-work, and Verse operations.
|
||||
- CultCache stores typed state and receipts; CultMesh/CultNet carry typed local
|
||||
|
|
@ -230,7 +230,7 @@ Cut in this order:
|
|||
status consumes the shared projection.
|
||||
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.
|
||||
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.
|
||||
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. **Frontier-verdict Modeling landed at `d367e525`:** one exact Soul verdict
|
||||
atomically creates its deterministic request; the sealed role projection,
|
||||
|
|
@ -248,14 +248,22 @@ Cut in this order:
|
|||
writes merge. Accepted Eyes, role lanes, timestamps, generic regather, and
|
||||
Modeling hints cannot launch Eyes or gate Modeling. CultCache `ba6a487`
|
||||
supplies the shared named nested-document encoding boundary used by Mind.
|
||||
Migrate Verification, planning, and reorientation next from
|
||||
9. **Frontier Verification landed at `fc5d1a4a`:** one exact Hands commit and
|
||||
its deterministic Verification request publish atomically. The sealed
|
||||
request/launch/result/context lifecycle owns Launch/Wait/Review; admission
|
||||
writes the keyed audit, Soul verdict, frontier-Modeling request, and Mind
|
||||
commit receipt atomically. Disjoint keyed writes merge, exact-frontier drift
|
||||
refuses byte-identically, and replay is stable. Generic launch/acceptance,
|
||||
accepted-at/latest-result selection, dynamic telemetry prompts, and
|
||||
model-authored causal IDs no longer own this family.
|
||||
Migrate planning and reorientation next from
|
||||
aggregate state patches and generic role lanes to family-owned current-work
|
||||
projections, exact job identities, `MindMutation` plans, and exact commit
|
||||
receipts. Reuse pure invariant primitives, not a generic mutable registry.
|
||||
9. Delete `EpiphanyThreadStateEntry`, `coordinator_state_transaction`, global
|
||||
10. Delete `EpiphanyThreadStateEntry`, `coordinator_state_transaction`, global
|
||||
expected revisions, aggregate update APIs, and all source references from
|
||||
production. Refuse old writable stores; add no dual reader or migrator.
|
||||
10. Replay fresh-store concurrency and decision-context acceptance. Only then
|
||||
11. Replay fresh-store concurrency and decision-context acceptance. Only then
|
||||
restart Model Atlas Gate 1 from a new external root.
|
||||
|
||||
Do not preserve the aggregate for compatibility, manufacture a bootstrap
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ effects, receipts, Mind admission, brakes, external consequence gates, and
|
|||
terminal commit. Focused core and OpenAI-runtime Persona suites pass.
|
||||
|
||||
The five-day shakedown remains paused. The active branch includes exact
|
||||
`c7412998` on `codex/epiphany-shakedown-live`: the keyed Mind foundation, federated Model Atlas
|
||||
`fc5d1a4a` on `codex/epiphany-shakedown-live`: the keyed Mind foundation, federated Model Atlas
|
||||
vertical slice, ordinary Modeling authoring path, durable publisher identity,
|
||||
fresh seven-organ Mind bootstrap, and atomic RepoModel projection bootstrap are
|
||||
landed. Historical aggregate RepoModel and partial Gate stores are evidence
|
||||
|
|
@ -22,7 +22,8 @@ or repair path can restore their authority.
|
|||
This is not yet the full Concurrent Mind cut. Persisted
|
||||
`EpiphanyThreadStateEntry`, its coordinator transaction, and multiple
|
||||
unmigrated launch/acceptance/status readers remain live production authorities.
|
||||
Baseline Body, Proposal, frontier-verdict Modeling, and frontier Research are no longer among them:
|
||||
Baseline Body, Proposal, frontier-verdict Modeling, frontier Research, and
|
||||
frontier Verification are no longer among them:
|
||||
keyed Mind owns their work projections, operator and Resident launch, exact job-bound
|
||||
continuation, review, and semantic admission. Research is driven only by an explicit
|
||||
external-evidence obligation; accepted Eyes state, timestamps, generic regather, and
|
||||
|
|
@ -56,7 +57,8 @@ canonical Eve schema IDs without dependency semantics. Eve exact `b597dab` and
|
|||
`gamecult.eve.surface.v1` retained tree for GUI and TUI.
|
||||
|
||||
Verification is green at the latest ownership cut: Epiphany core library
|
||||
561/561, OpenAI runtime 43/43, Self policy 26/26, and coordinator runtime 18/18.
|
||||
559/559, OpenAI runtime 23/23, coordinator runtime 18/18, and core/OpenAI
|
||||
all-target checks pass.
|
||||
An unfiltered core package run also exposed two pre-existing
|
||||
`epiphany-hands-action` fixture failures: those fixtures omit the exact
|
||||
`RepoFrontierHandsAuthority` already required by production. The gate was not
|
||||
|
|
@ -67,7 +69,8 @@ still reaches an older feature-gated workspace-coverage recovery smoke whose
|
|||
already-absent API predates this slice; no compatibility shim was added.
|
||||
|
||||
These are implementation and isolated proof claims. They are not sustained
|
||||
Starfire dogfood. Gate 1 is the next rite: use separate real stores and
|
||||
Starfire dogfood. Planning, reorientation, and final aggregate deletion are the
|
||||
next source rites; only then may Gate 1 use separate real stores and
|
||||
identities; keep impact ingress absent while ordinary Modeling seeds facts and
|
||||
publishers/projector establish signed sight; then engage all three Atlas brakes
|
||||
and prove later organ cycles are held while the last Eve projection remains
|
||||
|
|
@ -362,8 +365,9 @@ deleted. A shared exact-envelope launch CAS remains because it protects the
|
|||
same atomic publication invariant for Body and Proposal, not because it owns
|
||||
family policy.
|
||||
|
||||
Exact `e404c105` removes the duplicate Body/Proposal continuation enums. One
|
||||
`EpiphanyModelingContinuationAction` now names Launch, Wait, and Review; each
|
||||
Exact `e404c105` removed the duplicate Body/Proposal continuation enums; exact
|
||||
`fc5d1a4a` names the shared vocabulary `EpiphanyAgentPassContinuationAction`.
|
||||
It names Launch, Wait, and Review; each
|
||||
family retains its own request, projection, validity rules, and admission owner.
|
||||
|
||||
Exact `20dd66c8` deletes claim-repair's request/binding/context schemas, runtime
|
||||
|
|
@ -404,11 +408,20 @@ omitted middle optionals. CultCache exact `ba6a487` adds named nested preparatio
|
|||
Mind envelopes retain their typed numeric slots while nested document fields remain named.
|
||||
Objective, Body, and Research Mind writers now share that boundary.
|
||||
|
||||
Map and migrate Verification next onto its exact Hands consequence, request/launch,
|
||||
terminal decision context, typed audit, Soul verdict, and family-owned Mind commit. Delete
|
||||
generic role launch/acceptance, latest-result, accepted-at, and thread-state authority for
|
||||
that family. Continue with planning and reorientation, then delete the aggregate
|
||||
schema/transaction. Run the source
|
||||
Exact `fc5d1a4a` completes that Verification cut. The exact Hands commit and
|
||||
derived `RepoFrontierVerificationRequest` publish atomically; current-work owns
|
||||
Launch/Wait/Review; the sealed role projection carries the exact route,
|
||||
frontier, Hands authority and receipts; and `Soul.verification` admission writes
|
||||
the keyed audit, Soul verdict, deterministic frontier-Modeling request, and
|
||||
Mind commit receipt in one transaction. A disjoint keyed node commit merges,
|
||||
an exact-frontier change refuses byte-identically, and replay returns the
|
||||
original receipt. Generic Verification launch/acceptance, accepted-at/latest
|
||||
selection, dynamic telemetry prompt mutation, and model-authored causal IDs are
|
||||
gone.
|
||||
|
||||
Map and migrate frontier Planning and PlanMind next onto their exact frontier,
|
||||
candidate, decision-context, and keyed Mind authorities. Continue with
|
||||
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
|
||||
partial roots read-only; do not release scheduling, register operational
|
||||
|
|
|
|||
Reference in a new issue