Map orphan worker Continuity authority

This commit is contained in:
Meta Vens 2026-08-10 12:36:48 +01:00
commit 0fa4f89374
3 changed files with 64 additions and 1 deletions

View file

@ -3160,3 +3160,45 @@ three. Exact live replay remains the package acceptance boundary.
- Verification layer: pure stop/wait tests, focused Heartbeat binary tests, then
exact packaged Linux serve under the copied c006 cognitive brake with SIGTERM,
exit zero, final shutdown receipt, and no new grant.
# Orphan worker Continuity authority map — 2026-08-10
Current mechanism: the coordinator persists an immutable runtime worker launch,
spawns `epiphany-openai-runtime run-worker` detached, and records the returned
PID only in its artifact JSON. The runtime store has no durable binding between
that launch/job and the worker process incarnation. Coordinator death after
spawn therefore leaves resident Self unable to prove whether the worker may
still publish terminal output.
- Owner: the worker runtime owns claiming its exact native process incarnation
before model or tool work. Runtime Continuity owns activation, terminalization,
and exact-death recovery of that claim. Resident Self only decides whether the
authenticated typed request is fulfilled after those runtime facts exist.
- Inputs: immutable worker launch/job, captured PID/creation token/executable,
explicit activation bound to that claim, native exact-process observation,
and authenticated terminal worker result.
- Outputs: `claimed` before consequence-capable work, `active` only after one
explicit activation, then exactly one `terminal-result` or `terminal-death`.
A terminal-death attempt may be superseded by a new ordinal without deleting
the prior launch family.
- Derived state: coordinator artifact PID and detached `Child` handle are
diagnostic only. Request identity remains retry-stable; launch, worker claim,
process, session, and artifact directory are attempt-incarnation state.
- Forbidden writers: receipt absence, coordinator death alone, elapsed time,
generic resident cancellation, and `roleFailureReview` prose cannot declare an
orphan worker dead or authorize a retry. A worker without an activated exact
claim cannot invoke model/tools or publish a terminal result.
- Shared paths: proposal Modeling, Imagination consideration, and admitted model
direction must use the same worker start gate and terminal claim primitive.
The worker itself claims before all provider/tool routes; no coordinator-only
happy path may bypass it.
- Cut line: persist a typed worker process claim from inside `run-worker`, gate
work on exact activation, make terminal result close that claim atomically,
and let Continuity write terminal death only after exact native observation.
Then extend each typed launch family with ordinal/supersession bound to that
terminal-death authority. Do not reuse the current unbound artifact PID.
- Verification layer: kill before claim, after claim/before activation, after
activation/before result, and after valid result/before coordinator receipt;
prove no model/tool work before activation, no dual live attempts, same typed
request with distinct attempt/process/artifact identities, exact replay, and
retention non-resurrection across all three typed lanes.

View file

@ -1,5 +1,26 @@
# Fresh workspace handoff
## Orphan-worker ownership mapped — 2026-08-10
The receipt-free pre-open coordinator boundary already has a focused source
test and fails closed on exact runtime-incarnation absence. The remaining
post-open fault is deeper than resident retry policy. Detached worker launch
persists the immutable runtime job/document, but the spawned worker PID exists
only in coordinator artifact JSON. No typed runtime state binds job, launch,
PID, creation token, executable, activation, and terminal state. After
coordinator death, neither resident Self nor Runtime Continuity can prove that
the worker is dead; supersession would permit two workers to publish for one
typed request.
The authority map is now explicit in the algorithmic map. `run-worker` must
claim its own exact process before provider/tool work and wait for an exact
runtime activation. Authenticated result or exact observed process death then
terminalizes that same claim. Only terminal death can ground a new attempt
ordinal. Proposal Modeling, Imagination consideration, and admitted model
direction must share this primitive. Coordinator artifact PID is sight only;
do not promote it or infer death from time/receipt absence. Actual c006 remains
braked. Yggdrasil never builds.
## Heartbeat graceful SIGTERM accepted on Linux — 2026-08-10
Exact pushed source `bfb92cbb96e8ac085222844d3aa51681d15e18d1`

View file

@ -70,7 +70,7 @@ current_status:
yggdrasil_epiphany_service_contract: repaired_in_gamecult_ops_812b427_not_installed
resident_physiology: c006_exact_c693aaea_settled_braked_no_active_lease_no_attempt_three_old_processes_stopped
unresolved_authority: Coordinator receipt, Heartbeat pulse-artifact, deployed supervisor/projector log retention, genuine-idle and active resource plateaus, exact-grant terminality, restart-persistent cooldown refusal, schedule/action issuance cardinality, runtime-owned typed fulfillment, narrow model-generation retention, published model-turn JSON ingress, semantic logical/physical retention, Persona conversation retention, stable Starfire firewall ownership, completed model-adapter session archival, and normal coordinator lifecycle opening/error closure/legacy repair/archival are accepted live. Receipt-free hard-death recovery is source- and package-accepted but its live kill matrix remains unproven because the first copied run exposed non-atomic storage publication. A typed worker launch without valid terminal fulfillment deliberately remains active awaiting an owner for exact orphan-worker death and supersession; it is not retryable yet. Historical migrated semantic attempts without recorded physical namespace remain durable and non-retirable. Repository Body observation still performs two authenticated full-tree Git index/manifest passes. Execute-mode workers require a persistent process body. Mutable Starfire bind storage is not accepted as resident authority until the packaged CultCache repair and recovery replay pass. One completed Discord consequence remains blocked by the absent Yggdrasil credential.
next_action: Resume the copied receipt-free coordinator death and orphan-worker Continuity matrix from exact bfb92cbb. Prove the pre-open death boundary, then classify post-open typed fulfillment versus orphaned immutable worker launch without inventing retry authority. Preserve distinct cognitive-thread, launch, session, process, and artifact incarnation evidence; keep actual c006 braked. Yggdrasil never builds.
next_action: Implement the runtime-owned worker start gate mapped in the algorithmic map: child claims exact process identity before model/tools, explicit activation gates work, terminal result or exact observed death terminalizes that claim, and only terminal death may authorize a new typed attempt ordinal. Apply the same primitive to proposal Modeling, Imagination consideration, and admitted model direction. Then package once and run the copied coordinator-death boundary matrix. Keep actual c006 braked. Yggdrasil never builds.
active_subgoals:
- Prove Persona, Self, Eyes, Modeling, Imagination, Hands, Soul, Mind, Continuity, and nervous-system behavior individually.