Refresh v44 shakedown boundary

This commit is contained in:
Meta Vens 2026-08-08 04:34:35 +01:00
commit ced86e7e98
3 changed files with 69 additions and 231 deletions

View file

@ -1331,6 +1331,17 @@ the continuity checkpoint deterministically from accepted RepoModel evidence,
or CRRC consumes canonical RepoModel admission directly. Canonical Imagination
and dedicated Mind must adopt the choice before Hands changes the seam.
Fresh v44 then proved that planning path through canonical Imagination and
dedicated Mind adoption. Inspection at the Hands boundary found the adopted
safe-path set omitted `epiphany-core/src/bin/epiphany-mvp-status.rs`, the actual
composition owner. The gate correctly forbids editing it. The route cannot yet
return this falsified plan to planning authority: the Hands contract catalogs
an action-refusal receipt, but no typed record, writer, CLI transition, or
frontier lifecycle effect implements it. A route currently terminates only
after a complete mutation, verification, Soul verdict, and Modeling
incorporation chain. Hands must gain a typed refusal/relinquish consequence
before the checkpoint repair can continue without fabricating work.
## Exact release build cache ownership
Release construction has two serialized cache authorities. The graph cache is

View file

@ -1,232 +1,59 @@
# Fresh Workspace Handoff
Fresh v42 now proves the `ecfff489` repair live. Exact release
## Live boundary — 2026-08-08
The active branch is `codex/epiphany-shakedown-live`; pushed state is
`dae006a0`. Exact cognition source `ecfff489fe7e46f6ddcc9d58f0723411e8d94c13`
is packaged as
`sha256-6e5cd9827ab6a659c8a29f1147daf8ebec52ea3d148a16905a1401c539059d79`
with witness
`sha256-8d53746348eecf2afd2a5def5539dfb544e260104fb33e3e7d0eec83573ce3dc`
gave ordinary resident Modeling its role-scoped read tools. The worker inspected
source, emitted a generic node/edge-only RepoModel evolution, and Mind accepted
it without the frontier bypass seen in v41. v41 remains sealed.
`sha256-8d53746348eecf2afd2a5def5539dfb544e260104fb33e3e7d0eec83573ce3dc`.
Starfire remains the cognition and release forge; Yggdrasil remains the small
public runtime body.
The accepted result exposed the next authority seam. RepoModel admission does
not create or replace the legacy durable investigation checkpoint consumed by
CRRC, so status remained `prepareCheckpoint` and Self launched another generic
Modeling pass. The worker cannot repair this through `statePatch`: repository
anatomy was deliberately removed from that surface, and the worker must not own
accepted checkpoint truth. Typed proposal
`proposal-v42-unify-modeling-checkpoint-authority` is selected as request
`repo-frontier-proposal-modeling-bfb37ae71693a31ea573ef3ffaeec3f9561d51afff4a9c30bb59606d54d2586f`.
Its required route is proposal Modeling -> canonical Imagination -> dedicated
Mind decision -> Hands. The proposal-bound worker is PID `32480` with a
600-second bound; poll it before launching anything else.
Fresh runtime
`F:\Projects\.epiphany-runtime\shakedown\live-20260808-v44-clean-planning`
proved the native proposal Modeling -> Imagination -> dedicated Mind planning
circuit without overrides. Mind adopted candidate
`repo-frontier-plan-candidate-700b1404f73888840ea5981be736ad3b2406e72ec4ee7eba7f763d9db03e498c`
and Self derived Hands route
`repo-frontier-route-86b9702dd4ad3eedae2693e8af7d0b547fe00885949fa2646b3f3b6a47a6225d`.
The operator-safe gate summary is
`.epiphany-dogfood/v44-clean-planning-r5/coordinator-summary.json`.
Exact `ecfff489` packaging took 7m04s of Cargo work. Release incremental
compilation is absent, a core edit recompiles monolithic `epiphany-core`, and
the bundle relinks 21 binaries. Benchmark `incremental=true` and `rust-lld`
independently after the cognition boundary. During v42 tool rounds `runtime.cc`
grew beyond 59 MB and exposed brief whole-file replacement windows; measure
that separately as retention/storage work rather than mixing it into the
checkpoint repair.
The adopted plan cannot be executed truthfully. Its path ceiling omits
`epiphany-core/src/bin/epiphany-mvp-status.rs`, the composition owner that must
project current RepoModel admission into Reorientation and CRRC. The existing
coordinator and CRRC inputs do not independently observe that admission. No
source was changed outside the gate.
Fresh v41 exhausted the selected proposal queue, then exercised failure and
recovery. Two Modeling runs launched with resident `--no-auto-tools` failed
immediately because the assistant payload was empty/non-typed JSON. Supervised
failure review wrote exact supersession receipts and relaunched through the
packaged coordinator. A tool-enabled retry completed with source-grounded
findings, proving the missing input. Mind nevertheless rejected two successive
completed patches because ordinary `evolution` attempted to mutate the current
verdict-owned frontier: `Evolution cannot bypass a current route or own
verdict-driven frontier lifecycle`. The runtime stayed unchanged.
This exposes a route-lifecycle defect: an adopted Hands route has no typed
refusal, relinquish, or supersession transition when implementation inspection
falsifies its plan. `epiphany.hands.action_refusal_receipt` is named in the
contract catalog but has no persisted type, writer, CLI command, or route
terminalization semantics. The only implemented terminal path requires a
patch, command, commit, verification request, Soul verdict, and verdict
incorporation. Do not fabricate that consequence chain or mutate the v44 store
by hand.
The current worktree removes resident's blanket tool disable and makes ordinary
Modeling's JSON schema expose only node/edge operations unless a typed proposal,
claim-repair, or verdict authority field is present. Focused schema and
resident-launch tests pass. v41 is sealed as the missing-tools and overbroad
output-contract boundary.
## Active work
Exact pushed `5f09d35a` packages as
`sha256-39a81a35d847fd6b459379d5bf3ef4fa57a3142745a10f13f4b033eea85ca45a`
with witness
`sha256-9cf82d9c1bdf018c36d199838598f5476acbc43818beb9fdb68840dc00be7f9b`.
Because this commit changed only the coordinator binary, the stable release
cache reused `epiphany-core` and Cargo completed in 29.58s; the preceding core
change took 6m50s. The remaining iteration penalty is monolithic core
invalidation, not universal package reconstruction.
A detached release-incremental benchmark runs under PID `8368`. It writes cold
and invalidated-core timings to
`.epiphany-run/build-benchmarks/incremental-20260808/result.json`, with Cargo
logs beside it. Poll that artifact; do not launch another Cargo process. After
it completes, benchmark `rust-lld` independently in a different target
directory. The baseline core-change package took 7m04s; a warm unchanged
package took 1.48s of Cargo work.
Fresh v40 replay proved the proposal startup actuator. Request `4b9414...`
launched under persistent supervision, resident revision 5 remained running
while its Modeling worker lived, and revision 6 completed only after the exact
proposal launch binding existed. Typed status then advanced the pending queue
to request `e75b60...`. The Modeling worker result failed and is not accepted,
but the first request was consumed by its exact launch consequence rather than
by a generic coordinator receipt. v40 is sealed as the successful
binding-before-success boundary.
After the build benchmark, first give adopted Hands work a typed
refusal/relinquish path that preserves Mind's plan authority, records why Hands
cannot proceed, and returns frontier ownership to a lawful replanning state.
Then replay v44, reject the incomplete plan through that path, adopt a corrected
plan including the status-composition owner, and prove CRRC -> accepted
Reorientation -> Continuity recovery -> Soul closure.
Exact `58f42b6a` packages as
`sha256-562aeb2bf246e27f2b63ed094633b63daff7ca07d5eb5f14dfcb12d47fca6daf`
with witness
`sha256-8d5ad5e2b734679c8b788445f6ad91d31468cc56d001f3d975fa34f373faf0c2`;
its stable-cache core build took 6m50s. Fresh v39 proved `unfulfilled`
cancellation and heartbeat retry repeatedly preserve the exact proposal
pressure. It also exposed why no retry could succeed: resident coordinators run
in safe `plan` mode, and proposal Modeling alone lacked a typed startup launch
handler. Operator-safe coordinator evidence showed `launchModeling`,
`canAutoRun=true`, one planning step, and zero launch events. Raising the step
budget from four to eight did not change the result and is rejected as a fix.
The current worktree gives proposal Modeling the same exclusive objective-free
startup ownership already used by typed Imagination and direction requests.
All 15 coordinator binary tests pass. v39 is sealed at this missing-actuator
boundary.
Exact pushed `88a38987` packages as
`sha256-76ed147f0ce86f26bab210534e623ed0a67030c2d8a03a7ad7e5226ffa934059`
with witness
`sha256-d7f6551dda188dbd3abe4ccbd73ce97825bc3d77f1467968f8d56c1fdd40437f`.
Fresh v38 replay from the pre-proposal v31 boundary crossed autonomous
Imagination and derived proposal Modeling request `673ab...`. The replay then
falsified the fulfillment repair before its intended assertion: swarm emitted
typed cancellation status `unfulfilled`, but the sole cancellation primitive
rejected that new terminal class, so it could not perform its atomic pressure
requeue. The current worktree aligns that contract and the focused atomic
requeue test now exercises `unfulfilled`; it passes. v38 is sealed as the
terminal-contract failure boundary.
## Current authority — 2026-08-08
The active branch is `codex/epiphany-shakedown-live`. Exact pushed release
`8a9439ca2e0dddaec832a5e9285735b4d5a109cd` is authenticated as
`sha256-39e12132f829fbb782cc4ba33308e44c641f6bd4a1136850ce9246b1179c3cbd`
with witness
`sha256-d57bdeb6e6b14cc3b7500d461fa7ea26455d319b4f1d904cda2fa6e0317407be`.
Its 21 binaries contain no private state. The active stable-cache publisher
completed this core-change Cargo pass in 6m46s; an identical warm pass took
1.48s of Cargo work and 18.669s end to end. An older publisher using ephemeral
source plus a commit-local target was terminated after 12.8 minutes. Rebuild
the publisher itself after changing release-cache machinery; otherwise the
benchmark measures an obsolete body.
Fresh runtime `live-20260808-v35-request-thread` published that release and ran
under persistent swarm supervision. The resident child completed on exact
thread `shakedown-v31-rupture-closure-implementation-r1`, proving the typed
request owns the launch and lease across the real process boundary. The
accepted Imagination direction result contained several options. Autonomous
promotion correctly persisted each option and its exact provenance as selected
proposal-Modeling work, but status then failed because the pending projection
required exactly one unclaimed request.
The current worktree treats selected proposal-Modeling requests as an
oldest-first execution queue. Exact `16be92f4` packages as
`sha256-998dbac0877ee2249f723796501f4f82c50cc9dcb8ae205117a50cde04bab3e6`
with witness
`sha256-4975a3b043012f62eecfd9c9b6c9f431bbf66a48ff1f46117bd1532c8b0dba28`.
v36 proved status derives `launchModeling` instead of rejecting cardinality and
completed one proposal Modeling turn. The oldest request nevertheless remained
pending because v35 had emitted pressure for every option and heartbeat had
selected a later pressure first. This falsified the partial repair: runtime and
resident pressure were still separate schedulers.
The current worktree emits resident pressure only for the runtime-owned pending
head. Its exact launch binding exposes the next request on a later ingestion
cycle. All 17 resident-Self tests pass; focused tests prove runtime ordering,
single-request launch consumption, and head-only pressure emission. v35 and v36
are sealed failure boundaries.
Exact `a1d80d40` packages as
`sha256-1ef95f24e9d0bfb5e88ded9391c261d3b4cdc37276f4a6a0f2479cb57a8c9760`
with witness
`sha256-1fde6a1cd73747393631ac50de02c5e404a48c263f48386232b01ae288ab0024`.
Fresh v37 replay proved head-only pressure: only request `464ac...` received a
pressure, grant, and child claim. The coordinator exited zero and resident Self
accepted its generic terminal receipt, but typed status still reported that
same request pending. The runtime had no exact proposal-Modeling launch binding.
The current worktree makes that impossible to call success. A proposal-Modeling
grant must have its exact runtime launch binding before resident terminal ack;
otherwise the turn is cancelled as `unfulfilled` and the same pressure returns
to heartbeat. The focused fulfillment test and both swarm binary tests pass.
v37 is sealed at the false-success boundary.
Fresh runtime `F:\Projects\.epiphany-runtime\shakedown\live-20260808-v31`
accepted initial and proposal-bound Modeling for thread
`shakedown-v31-rupture-closure-implementation-r1`. The generic user proposal
lawfully derived a direct Hands gate, but that gate remains inert because this
objective requires the autonomous Imagination-origin path and dedicated Mind
adoption before Hands.
Resident ingestion then committed the admitted-model direction request and
pressure. A standard heartbeat selected that pressure. The next resident cycle
failed before launch because replay recreated the same producer pressure ID
with a later `created_at_millis`; full document equality misclassified that
ordinary replay as an identity collision.
Pushed commit `b81092b2` repairs ownership in `resident_self.rs`: producer replay
compares immutable producer identity, while timestamp and pressure lifecycle
remain derived/mutable. Changed objective, provenance, kind, schema, identity,
or privacy authority still collide. All 15 resident-Self tests pass, and the
autonomous promotion integration proves ingestion after heartbeat consumption
returns zero without recreating work.
Exact `b81092b2` packages as
`sha256-da343dcfe478720320f94c582eebcef2804aac41ac136a9c6a504cd248f495fa`
with witness
`sha256-41f081ce260467325a759bf6c888b30cf7d57faff1b1fdcfab398191323cf333`.
The authenticated replay clone `live-20260808-v32-replay` crossed the original
collision and launched the resident coordinator. The child correctly refused
an operator-supplied artifact root outside `.epiphany-dogfood`. Its typed
cancellation then exposed a second continuity wound: the source pressure stayed
`consumed`, so heartbeat could never grant an exact retry.
The current worktree makes cancellation atomically return the exact pressure to
`pending` while writing the failed terminal acknowledgement. Heartbeat remains
the sole retry scheduler and issues a new grant identity. All 16 resident-Self
tests pass, including exact failed-turn pressure recovery.
Exact pushed `c5f99c46` packages as
`sha256-04a4854a1268139e42c028503460bb75d5b4c97b28c7fafcfb963ad1210c0090`
with witness
`sha256-615b3878473d65c67998614e1f6e33cec2bb5ea08a985210ff1c2161c1a481a5`.
The v33 retry proof repeated the deliberate startup refusal under this release.
Cancellation returned the pressure, but heartbeat reconciliation exposed that
grant identity was still only schedule + action + pressure. A same-action retry
therefore collided with the immutable first grant.
The current worktree adds a pressure-local attempt ordinal to grant identity.
The retry test now uses the same heartbeat schedule/action and proves attempt 2
receives a distinct grant while retaining the same pressure authority. All 16
resident-Self tests pass.
Exact pushed `d4b446ab` packages as
`sha256-d31ab4329dd34d93e101fa3a783373b6b1f3bc311fac057c6f0d0b4ce5911122`
with witness
`sha256-d5256ee2181dcacc3da87c8f491a12c359a0bde6139a362d40053d453acac4b8`.
The v34 live timeline proved the deliberate failure, cancellation, attempt-2
grant, and replacement launch. Running the replacement under persistent
`epiphany-swarm serve` reached coordinator validation, which correctly refused
`model direction consideration provenance mismatch`: resident preparation had
substituted fixed thread `resident-self-thread-epiphany-starfire` for the
implementation thread owned by the typed direction request.
The current worktree reloads typed direction, Imagination-consideration, and
proposal-Modeling requests during preparation and carries their exact runtime
and thread identity through argv, child launch, and lease. Plain operator
pressure alone retains the fixed resident thread. All 16 resident-Self tests and
both packaged swarm tests pass; typed launch tests assert the request-owned
thread.
## Next action
1. Commit, push, package, and authenticate proposal-pressure fulfillment.
2. Preserve v31 through v37 as failure evidence; clone v37 and publish the exact
successor release.
3. Prove the unfulfilled zero-exit requeues, heartbeat retries, the exact launch
binding is created, and only then the next selected option becomes pressure.
4. In a fresh runtime, re-run pressure ingestion twice and resident launch.
Prove autonomous direction consideration, proposal-bound Modeling,
canonical Imagination, dedicated Mind adoption, and exact Hands authority.
5. Deliberately fail one bounded worker and prove typed terminalization,
restart/recovery, Reorientation, and Soul-verifiable closure.
6. Continue through Persona consequence, retention, endurance/resource
plateau, and Linux/Yggdrasil cognition.
Do not execute v31's direct Hands gate, read raw worker transcripts, mutate
sealed runtimes, or start concurrent Cargo against the release cache.
Persona consequence, bounded retention, crash/restart closure, endurance and
resource plateau, and Linux/Yggdrasil cognition remain open. v22 and earlier
shakedown scars remain in git and the typed evidence ledger; they are not active
rehydration state.

View file

@ -34,7 +34,7 @@ invariants:
- Evidence and git retain history; this map retains only state that changes future decisions.
current_status:
summary: Epiphany is a supervised engineering alpha on Starfire, not deployment-ready. Exact ecfff489 packages as sha256-6e5cd9827ab6a659c8a29f1147daf8ebec52ea3d148a16905a1401c539059d79 with witness sha256-8d53746348eecf2afd2a5def5539dfb544e260104fb33e3e7d0eec83573ce3dc. v42 proves ordinary resident Modeling receives role-scoped source tools, emits a grounded schema-constrained node/edge RepoModel patch, and reaches Mind admission without frontier bypass. That proof exposed a split checkpoint authority: accepted RepoModel admission does not satisfy CRRC's durable investigation checkpoint, so Self relaunches generic Modeling. A selected typed proposal now routes that seam through proposal Modeling, canonical Imagination, and dedicated Mind before Hands. Persona consequence, retention, endurance, and Linux/Yggdrasil cognition remain open.
summary: Epiphany is a supervised engineering alpha on Starfire, not deployment-ready. Exact ecfff489 packages as sha256-6e5cd9827ab6a659c8a29f1147daf8ebec52ea3d148a16905a1401c539059d79 with witness sha256-8d53746348eecf2afd2a5def5539dfb544e260104fb33e3e7d0eec83573ce3dc. Fresh v44 proves proposal Modeling, canonical Imagination, dedicated Mind adoption, and exact Hands gating without overrides. Hands inspection then falsified the adopted path ceiling: it omits the status-composition owner required by the checkpoint repair. The gate held, but adopted Hands work has no typed refusal or relinquish transition, leaving the frontier unable to return lawfully to planning. Persona consequence, retention, endurance, and Linux/Yggdrasil cognition remain open.
operational_state:
local_worktree: clean_at_ecfff489_live_v42_checkpoint_authority_shakedown
operator_wireguard: restored
@ -52,8 +52,8 @@ current_status:
bifrost_feedback_crossing: authenticated_transport_only
yggdrasil_epiphany_services: absent
resident_physiology: heartbeat_and_self_running
unresolved_authority: v42 proved Modeling tool access and ordinary output authority, but accepted RepoModel admission and CRRC's durable investigation checkpoint remain separate truths. Typed proposal proposal-v42-unify-modeling-checkpoint-authority is selected for exact proposal Modeling so canonical Imagination and dedicated Mind can choose the repair before Hands. Failure-to-Reorientation-to-Continuity-to-Soul closure, Persona consequence, retention, endurance, and Linux/Yggdrasil cognition remain open.
next_action: Complete and admit the proposal-bound v42 Modeling result, drive its actionable frontier through canonical Imagination and dedicated Mind adoption, then execute only the adopted Hands repair that gives checkpoint truth one owner. Prove CRRC advances into accepted Reorientation, a Continuity recovery receipt, and Soul closure. Benchmark release incremental compilation and rust-lld separately after this cognition boundary; measure the growing whole-file runtime store as a distinct retention problem.
unresolved_authority: v44 proved the native planning circuit and exact Hands gate. The adopted plan omitted epiphany-core/src/bin/epiphany-mvp-status.rs, so truthful implementation is forbidden. The cataloged Hands action-refusal receipt has no typed persistence or route-lifecycle transition; a falsified adopted plan therefore cannot return authority to planning without fabricating a consequence chain.
next_action: Finish the detached release-incremental benchmark under PID 8368, then benchmark rust-lld separately. Add and prove a typed Hands refusal/relinquish transition through a fresh lawful plan, replay v44 to retire the incomplete route, adopt a corrected checkpoint-authority plan including the status-composition owner, and prove CRRC advances through accepted Reorientation, Continuity recovery, and Soul closure.
active_subgoals:
- Prove Persona, Self, Eyes, Modeling, Imagination, Hands, Soul, Mind, Continuity, and nervous-system behavior individually.