Record keyed frontier verdict Modeling

This commit is contained in:
Meta Vens 2026-08-17 23:30:00 +02:00
commit 5b59c40a97
5 changed files with 83 additions and 25 deletions

View file

@ -5011,3 +5011,39 @@ 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.
Exact `d367e525` completes the third Modeling lifecycle: incorporation of a
typed Soul verdict into one routed RepoModel frontier. Verification acceptance
atomically persists `SoulVerdictReceipt` and the deterministic
`RepoFrontierModelingRequest`; neither an accepted Research timestamp nor a
latest-result slot can manufacture the request. The exact request, Soul verdict,
route, Verification request/result, and current frontier document are sealed in
`RepoFrontierVerdictModelingLaunchAuthority` inside the role reasoning
projection. The runtime launch no longer carries a parallel authority blob or
aggregate telemetry prompt.
Owner: `project_current_work` derives this family's Launch/Wait/Review state;
`launch_current_frontier_verdict_modeling_work` atomically publishes one
deterministic attempt; `accept_frontier_verdict_modeling_result` alone admits its
bounded frontier mutation under `Modeling.frontier_verdict`. Inputs: one exact
Soul verdict chain, current routed frontier document, admitted Body, sealed Mind
projection, exact terminal result, and decision context. Outputs: one typed
worker lifecycle and one exact Mind commit receipt. Derived state: role boards,
events, timestamps, status JSON, and `modelingResultAcceptedAfterResearch` are
display/audit projections only. Forbidden writers: Eyes acceptance, aggregate
thread revision, accepted-at ordering, latest Verification selection, dynamic
prompt appenders, and generic Modeling role terminality cannot create, suppress,
review, or admit this work. Shared paths: operator and Resident consume the same
current-work projection and acceptance owner. Deletion line: the aggregate
frontier-verdict context constructor, telemetry appender, latest-result selectors,
parallel MessagePack authority field, and direct Soul-verdict writer are gone.
The exact frontier `EpiphanyMindDocumentVersion` is both sealed audit input and
the family's strong dependency. Admission verifies the mutation planner read
that same version. A later disjoint keyed node commit therefore merges, while a
same-frontier change before planning refuses and a change after planning loses
the batch CAS. The model's terminal output is never reinterpreted against newer
strong state. The focused lifecycle proves deterministic two-launch convergence,
sealed context, terminal result, review, admission, disjoint merge, and
byte-identical stale refusal. Core library 561/561, OpenAI runtime 43/43, Self
policy 26/26, and coordinator runtime 18/18 pass.

View file

@ -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 and Proposal Modeling have been removed from
that authority; repair, verdict, Research, Verification, planning,
reorientation, and generic coordinator presence remain.
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.
- 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
@ -232,11 +232,17 @@ Cut in this order:
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. **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,
`MindMutation` plans, and exact commit receipts. Reuse pure invariant
primitives, not a generic mutable registry.
7. **Frontier-verdict Modeling landed at `d367e525`:** one exact Soul verdict
atomically creates its deterministic request; the sealed role projection,
deterministic attempt, shared Launch/Wait/Review state, and
`Modeling.frontier_verdict` commit own the complete lifecycle. Admission
accepts disjoint keyed changes but refuses a changed strong frontier without
mutation. Accepted Eyes timestamps, latest-result slots, aggregate prompt
construction, and generic role lanes cannot create or suppress this work.
Migrate Research, Verification, 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.
8. 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.

View file

@ -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
`d1b031cb` on `codex/epiphany-shakedown-live`: the keyed Mind foundation, federated Model Atlas
`d367e525` 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,8 +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 and Proposal Modeling are no longer among them: keyed Mind owns
their work projections, operator and Resident launch, exact job-bound
Baseline Body, Proposal, and frontier-verdict Modeling are no longer among them:
keyed Mind owns their work projections, operator and Resident launch, exact job-bound
continuation, review, and semantic admission. Fresh Gate
preflight proved the consequence: both keyed semantic partitions reached ready,
but status still called the organism missing because no thread aggregate
@ -53,9 +53,13 @@ canonical Eve schema IDs without dependency semantics. Eve exact `b597dab` and
`076d212` provide the canonical Atlas provider advertisement and one
`gamecult.eve.surface.v1` retained tree for GUI and TUI.
Verification is green at the latest ownership cut: Epiphany core 563/563,
OpenAI runtime 23/23, and the OpenAI runtime all-target check. Earlier coordinator
18/18 and workspace checks remain accepted; Odin Node 1/1 and Rust 15/15; Eve Atlas
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.
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
weakened; fixture repair remains separate test-harness debt. Earlier workspace
checks remain accepted; Odin Node 1/1 and Rust 15/15; Eve Atlas
conformance 4/4 and Eve contracts 6/6. The workspace-wide all-features check
still reaches an older feature-gated workspace-coverage recovery smoke whose
already-absent API predates this slice; no compatibility shim was added.
@ -369,10 +373,22 @@ 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,
Exact `d367e525` migrates frontier-verdict Modeling onto one atomic typed chain.
Verification acceptance commits the exact Soul verdict and its deterministic
Modeling request together. `EpiphanyCurrentWorkProjection`, operator/status,
Resident pressure, deterministic attempt identity, sealed role projection, and
`accept_frontier_verdict_modeling_result` carry that request through
Launch/Wait/Review and `Modeling.frontier_verdict` admission. The request seals
the exact routed frontier version. A disjoint keyed node commit after basis
sealing merges; a changed frontier refuses with the store byte-identical, so
model output is never silently rebased. Accepted Eyes state is display/audit
input only and cannot manufacture Modeling work. The aggregate telemetry prompt,
accepted-at Research boundary, latest Verification selector, parallel authority
MessagePack, and generic role-lane review path are gone for this family.
Map and migrate Research acceptance next onto its exact request/launch,
EyesEvidencePacket, decision context, and family-owned Mind commit. Continue
with 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