Record landed Idunn authority foundation

This commit is contained in:
Meta Vens 2026-09-02 21:15:38 +02:00
commit 8d42a959ec
4 changed files with 67 additions and 71 deletions

View file

@ -1,6 +1,6 @@
# Ghostlight Fresh Workspace Handoff
Updated: 2026-09-01
Updated: 2026-09-02
This is the compact re-entry packet. It carries current authority and the next
gate. Git owns chronology, the system map owns teardown detail, and evidence
@ -129,22 +129,23 @@ body. The 1,200 and 2,400 actor profiles are synthetic fixtures only.
Yggdrasil still serves legacy Ghostlight release `a4080d4` from an enabled
`Restart=always` unit with health v1, campaign/Session Zero state, and no
`world.cc` or `app-sessions-v2.cc` witness. The Connector is also still on its
legacy enabled body. Idunn r21 is live, but its current deploy seam is not safe
to invoke: target policy is repeated across compiled Rust, raw shell command
records, a privileged dispatcher, and large gamecult-ops target programs. Its
root-side source-floor validator cannot inspect correctly Idunn-owned Git
mirrors, and the current fixed-port scripts stop the incumbent before a fresh
candidate is green.
legacy enabled body. CultNet `87d0b0f` now owns the shared runtime-activation,
signed presence-health, and process-write-lease contracts. Odin `cebe425` owns
deterministic recipe and operator-binding parsing, compiled plans, sealed
releases, and sanitized Expected projections. Idunn's Git, runner, workload,
lease/fencing, route, CultCache/CultMesh, and main-loop actuation remain absent;
the legacy deployment seam is still unsafe to invoke.
The adopted cut puts a visible recipe and unit template in each target repo.
Idunn operator bindings own the admitted ref, runner/container image and
affordances, host paths, secrets, routing endpoint, rollout, retention, and
desired replica placement. Idunn freezes and materializes source as its own UID,
executes the configured build/test recipe, seals the candidate, waits for signed
staged readiness on a private endpoint, then alone revokes the incumbent
process/write grant, admits the candidate, moves the stable route, and drains
the old generation. Deployment and continuity remain separate authorities; a
deployment brake cannot suspend restart of the already-admitted body.
desired replica placement. A sealed plan and release publish only Expected.
Idunn observes the exact runtime activation; the service signs Present health.
For writable state, Idunn grants the process-bound lease before state opens.
Odin correlates Expected, activation, and Present into Ready, and stable route
membership moves only after Ready. Deployment and continuity remain separate
authorities; a deployment brake cannot suspend restart of the already-admitted
body.
Heimdall owns account identity. Eve owns command invocation and lowering.
VoidBot owns Vault retrieval and evidence. Idunn owns deployment and daemon
@ -154,14 +155,13 @@ and proposals but cannot commit on their behalf.
## Next gate
Rebuild the Idunn deployment seam before releasing another target brake. Define
one typed target recipe plus operator binding, remove raw executable command
authority and root Git inspection, and move Ghostlight and Connector build,
test, package, unit, health, and state semantics into visible target-owned
recipes. Keep fleet affordances and exact branch admission in Idunn-owned
configuration. Introduce a stable router data plane whose membership only
Idunn can change; candidate health must be green before the process/write lease
and route move.
Integrate the landed recipe, binding, plan, release, Expected, activation,
presence, and write-lease contracts into Idunn's main control plane and narrow
Git, runner, workload, lease/fencing, route, CultCache, and CultMesh drivers.
Keep target semantics in visible Ghostlight and Connector recipes and fleet
affordances in Idunn-owned bindings. Require Expected plus Idunn-observed
activation plus service-signed Present; grant the process lease before writable
state opens; require Odin-correlated Ready before stable route membership moves.
Deploy the Connector and then Ghostlight through that contract. Runtime restart,
route continuity, signed health, exact receipts, exclusive world-v2 state, and

View file

@ -13,16 +13,15 @@ Yggdrasil systemd body, Idunn continuity target, and Odin discovery crossing
are the live machine; the older validated artifact seams remain regression
evidence only.
## Implemented sealed replacement boundary (Phase 2)
## Landed replacement source owner
`crates/ghostlight-dungeon/src/world/` now contains the private
`ghostlight.world_state.foundation.v0` owner. It is an implemented and tested
foundation, not yet the hosted runtime: `lib.rs` still keeps `world` private and
exports the legacy `kernel::WorldKernel`, while `main.rs` still opens
`CampaignStore` and runs the legacy Session Zero and campaign paths. Source
inspection finds no production caller of the replacement types outside the
private module. The two bodies currently coexist without a state bridge; the
hosted process still belongs to the legacy body.
`crates/ghostlight-dungeon/src/world/` contains the sealed
`ghostlight.world_state.foundation.v0` owner. Commits `6bb6869` and `13d5136`
make that mailbox/kernel path the crate and executable runtime identity, remove
the legacy Session Zero/kernel/scheduler/verifier source body, and place app
sessions, world journal, and controller custody behind one CultCache
implementation. Production remains on the separately recorded legacy release;
source cutover is not deployment evidence.
### Replacement authority map
@ -63,10 +62,9 @@ hosted process still belongs to the legacy body.
controller implementations, model output, snapshots, derived opportunities,
replay, and consumers cannot mutate canonical state. The legacy
`SessionZeroKernel`, public `kernel::WorldKernel`, `CampaignStore` callers,
assessor/reconciliation chains, schedulers, and reload repair paths have no
admission path into the replacement journal. They remain live authorities in
the hosted legacy body and therefore remain on the deletion line rather than
becoming compatibility writers.
assessor/reconciliation chains, schedulers, and reload repair paths are
absent from the committed replacement source and have no admission path into
its journal.
- **Shared paths:** after create or open constructs the owner, `WorldMailbox`
consumes it and offers only `Submit` and `Snapshot`. Human controllers,
Narrative Personas, and operational agents all exercise the same
@ -74,16 +72,12 @@ hosted process still belongs to the legacy body.
controller-specific mutation API. Draft commands use that same submit
primitive. Command ID replay is checked before revision so an exact retry can
recover a known durable result, while reuse with different content fails.
Runtime identity construction and controller execution are not wired yet.
- **Cut line:** make app-session identity the only production constructor of
`AuthenticatedCaller`, expose the mailbox as the runtime's world handle, and
route creation, Draft activation, player action, Narrative Persona action,
and operational-agent action through it. As each complete ingress moves, cut
its legacy handler and store writer. Completion requires removal of the
public legacy kernel, Session Zero publication split, direct `CampaignStore`
mutation surfaces, scheduler/reconciliation writers, reload repairs, and
their obsolete modules and binaries; no dual-write or compatibility mode is
admitted.
Runtime identity and human, Narrative Persona, and OperationalAgent execution
are wired to that mailbox boundary in the committed source.
- **Cut line:** source subtraction is complete. Production cutover now belongs
to Idunn's typed deployment path: admit the replacement release and exclusive
world-v2 state without a dual-write or compatibility bridge, prove restart
and negative legacy authority, then remove the old hosted body and state.
- **Verification layer:** the reducer checks exact authentication, world,
revision, lifecycle, approver, controller, opportunity, scope, affordance,
and action bindings before proposing an effect. `apply_effect` rechecks the

View file

@ -19,12 +19,13 @@ assessor, verifier/reconciliation, or legacy-transition module path.
Production has not crossed that source boundary. Yggdrasil still runs legacy
release `a4080d4` under an enabled `Restart=always` unit and a legacy state
root. The current Idunn path repeats deployment authority across compiled
target policy, persisted raw shell commands, a privileged dispatcher, and large
target-specific gamecult-ops programs; it also validates Idunn-owned Git as
root and stops the incumbent before the candidate is ready. The active move is
therefore the Idunn recipe/binding/router rebuild and one-way live cutover, not
more Ghostlight runtime wiring.
root. CultNet `87d0b0f` lands shared runtime activation, signed presence-health,
and process-write-lease contracts; Odin `cebe425` lands deterministic recipe and
operator-binding parsing, compiled plans, sealed releases, and sanitized
Expected projections. Git materialization, runners, workload and route drivers,
lease/fencing, CultCache/CultMesh control-plane state, and Idunn main integration
remain absent. The active move is that actuation integration and one-way live
cutover, not more Ghostlight runtime wiring.
## Authority map
@ -179,23 +180,23 @@ remain future typed consumers at their causal boundaries. Model transport,
Vault retrieval, Heimdall identity, Eve/CultMesh projection, Idunn health, and
external adapters survive only where their ownership remains clean.
### 5. Rebuild deployment authority and cut production — active
### 5. Integrate deployment actuation and cut production — active
Each target repository publishes one strict visible recipe and unit template
covering build, test, package, artifact, health, and state semantics. Idunn
operator bindings own exact source admission, runner/container selection and
affordances, host paths, identities, secrets, capabilities, resources, private
candidate endpoints, stable routing, rollout, retention, and desired replica
placement. Typed target/action/source/recipe/deployment records replace raw
executable command state; source work runs as the Idunn identity and the narrow
privileged boundary consumes only sealed material.
The deterministic foundation is landed: target recipes and Idunn operator
bindings compile into private plans and sealed releases, and only a sanitized
Expected incarnation may leave that control plane. Shared CultNet contracts own
runtime activation, service-signed Present health, and process-bound write
leases. Idunn main integration and the Git, runner, workload, lease/fencing,
route, CultCache, and CultMesh drivers are not implemented yet.
Start each candidate on a private endpoint while the incumbent retains the
stable route. Signed staged readiness must pass before Idunn revokes the old
process and write lease, grants the candidate, atomically moves router
membership, and drains the incumbent. The deployment brake gates body changes;
same-release continuity remains separately owned and may be stopped only by an
explicit lifecycle brake.
The integrated path must publish Expected from the sealed plan and release,
record Idunn's observation of the exact runtime activation, and require the
service's signed Present health. A stateful candidate receives its process-bound
write lease before it opens writable state. Odin alone correlates Expected,
activation, and Present into Ready. Only after Ready may Idunn change stable
route membership and drain the incumbent. The deployment brake gates body
changes; same-release continuity remains separately owned and may be stopped
only by an explicit lifecycle brake.
Deploy CodexConnector first, then Ghostlight. Ghostlight's live cut archives the
entire legacy state root, creates a clean world-v2 root, and validates a complete

View file

@ -95,8 +95,9 @@ live_architecture:
- Each target repository owns a visible versioned deployment recipe: build, test, package, artifact map, unit template, health contract, state semantics, and requested runner profiles. A target may request an affordance; it cannot grant itself host authority.
- Idunn operator bindings own admitted source origins and refs, minimum revisions, exact release selection, container images and runner kinds, network, mounts, secrets, identities, capabilities, resources, routing endpoints, rollout policy, retention, and desired replica placement. `gamecult-ops` owns those fleet bindings and substrate provisioning, not target deployment programs.
- Idunn has two present authorities: deployment control changes an admitted body; continuity supervision keeps that same admitted body alive from signed health. The deployment brake gates only the first. A separately named lifecycle brake may suspend the second.
- A deployment starts a candidate on a private endpoint while the incumbent retains the stable route. Signed staged readiness precedes the one-way process and write-lease handoff; Idunn then revokes the incumbent admission, grants the candidate, atomically changes router membership, and drains the old generation. The router preserves the last admitted route but cannot choose membership.
- A sealed plan and release produce only Idunn's sanitized Expected incarnation. Idunn observes one exact runtime activation; the service signs its own Present health. For writable state, Idunn grants the process-bound write lease before the service opens state. Odin alone correlates Expected, activation, and Present into Ready. Stable route membership may move only after Ready; route membership and the write lease remain separate authorities.
- Typed target, action, exact source, recipe digest, runner binding, and deployment identity replace raw persisted shell-command authority. Source fetch and recipe materialization run as the Idunn identity; a narrow privileged boundary consumes sealed inputs and cannot interpret branch heads or mutable worktrees.
- CultNet commit `87d0b0f` owns the shared canonical runtime-activation, signed presence-health, and process-write-lease contracts. Odin commit `cebe425` owns deterministic recipe and operator-binding parsing, compiled plans, sealed releases, and sanitized Expected projections. Git, runner, workload, lease/fencing, route, CultCache/CultMesh, and Idunn-main actuation are not integrated yet.
pre_rebuild_architecture:
ghostlight_dungeon:
@ -218,7 +219,7 @@ pre_rebuild_architecture:
- Institution, faction, and consumer decision models
active_subgoals:
- Rebuild Idunn's deployment seam around one typed target recipe and operator binding. Ghostlight and CodexConnector must publish visible build, test, package, unit, health, and state contracts; Idunn configuration owns exact refs, runner containers and affordances, host bindings, routing, rollout, retention, and desired singleton placement. Remove raw executable command authority, root Git inspection, gamecult-ops target deployment programs, and stop-old-before-candidate activation before releasing another target brake.
- Integrate Idunn's landed deployment contracts into its main control plane and narrow Git, runner, workload, process-write-lease/fencing, route, CultCache, and CultMesh drivers. Ghostlight and CodexConnector publish visible recipes; Idunn bindings retain refs, runner affordances, host bindings, rollout, retention, and singleton placement. Preserve Expected plus observed activation plus service-signed Present plus Odin Ready, open writable state only after the process lease, and move the stable route only after Ready. Remove raw executable authority, root Git inspection, target deployment programs, and stop-old-before-candidate activation before releasing another target brake.
- Connect a Delvehold-owned adapter to the admitted generic consumer contract: shared compiler/consumer WorldSeed admission, externally authoritative institution-or-Gestalt snapshots, attributed proposal acknowledgement, and committed-event newspaper composition over typed CultNet, without consumer-specific IDs or schemas in Ghostlight.
- Extend strategic/offscreen named-person individuation beyond the proven emerge-then-act path so people plot across sustained political waves, acquire relationships, fold, and return without granting a cell, arena, or model commit authority.
- Finish the semantic mutation migration: delete or demote remaining legacy model effect schemas and move aggregate campaign fields toward projection-only state. Seed publication and named-person presence now have explicit non-effect authority classifications.
@ -349,10 +350,10 @@ data_flow:
current_status:
summary: Ghostlight's source teardown is complete at pushed commit `13d5136`: executable startup now enters the replacement runtime, the legacy scheduler/kernel/Session Zero pipeline modules are absent, and one CultCache implementation owns persistent state. Production has not cut over: Yggdrasil still runs legacy release `a4080d4` under an enabled `Restart=always` unit with health v1 and legacy state. The attempted deployment exposed duplicate authority across hard-coded Idunn policy, raw shell commands, the privileged dispatcher, and target-specific gamecult-ops programs, plus a root-versus-Idunn Git ownership failure and stop-old-before-candidate routing. The adopted deployment rebuild uses target-owned visible recipes, Idunn-configured runner and host bindings, candidate readiness behind a stable route, process/write-lease handoff, and separate deployment versus continuity authority. No deployment or acceptance run is active.
provider_acceptance_checkpoint: Exact pushed commit `139b8a6` completed Run 60 under `character-newsroom.v10` without world or per-wave replay. Its acceptance witness and terminal status bind the completed page and exact resume lineage. The independently dispatched blind reviewer, shown only the reader-facing fantasy newspaper, read it as a real left-populist civic broadsheet and did not immediately identify procedural generation, so the narrative reverse-Turing criterion passes. The review's substantive criticism is that the three stories feel like three rewrites of one briefing; accepted Run 60 remains immutable. The run used 96,902 prompt tokens and reported zero cache hits. Its delivered typeset artifact is `output/pdf/canopy-ledger-run-60-front-page.pdf`; frozen-source and visual verification remain accepted. Exact pushed `bc2ca39` then produced frozen-fact newsroom-only Run 61 Issues 13, 15, 16, 17, and 18 without world or wave model replay. Provider output proves `special_issue` convergence in Issues 13 and 15, independent `general_issue` beats in Issues 16 through 18, and assignment-selector cache hits. Blind review of Issues 13, 15, 16, and 17 passes both distinct recurring voices and issue-shape diversity, recognizing Ossan, Mera, Corin, and Lysa's biases plus modest cross-issue evolution. Run 62 exercised v12 without world or wave replay and failed only because two lead articles proposed invalid datelines; recurring reporter calls still recorded zero cache hits. Run 63 used exact pushed v13 `a52d57b`; Issues 17 and 18 completed before root stopped the final weekly recomposition, both repeated bylines again recorded zero cache hits, and live services remained unchanged. Preserve Runs 61 through 63 as stopped or completed immutable evidence. Copy defects remain later deadline-correction work rather than a reason to reopen accepted issue artifacts.
implementation_checkpoint: Pushed commit `6bb6869` makes the replacement mailbox/kernel architecture the crate and executable runtime identity and removes the legacy runtime owner. Pushed commit `13d5136` unifies app sessions, world journal, and controller custody under the vendored CultCache implementation and deletes the duplicate legacy CultCache dependency. The committed daemon tree has no old Session Zero, legacy kernel, scheduler, assessor, verifier/reconciliation, or legacy-transition module path. This proves source subtraction, not deployment: the running Yggdrasil process and state remain legacy until the Idunn recipe/binding/routing rebuild performs the one-way cut.
implementation_checkpoint: Pushed commit `6bb6869` makes the replacement mailbox/kernel architecture the crate and executable runtime identity and removes the legacy runtime owner. Pushed commit `13d5136` unifies app sessions, world journal, and controller custody under the vendored CultCache implementation and deletes the duplicate legacy CultCache dependency. The committed daemon tree has no old Session Zero, legacy kernel, scheduler, assessor, verifier/reconciliation, or legacy-transition module path. CultNet commit `87d0b0f` lands shared canonical runtime-activation, signed presence-health, and process-write-lease contracts. Odin commit `cebe425` lands deterministic recipe and operator-binding parsing, compiled plans, sealed releases, and sanitized Expected projections. Idunn's Git, runner, workload, lease/fencing, route, CultCache/CultMesh, and main-loop actuation remain absent. This proves source and contract foundations, not deployment: the running Yggdrasil process and state remain legacy until the integrated Idunn path performs the one-way cut.
full_world_acceptance_checkpoint: Run 115 is terminal failed at `/var/lib/gamecult/ghostlight-dungeon/acceptance/full-world-delvehold-0a83034-115`, semantic revision 2, regions 2/8, waves 0/1. Resume2 ended on provider SSE timeout. Resume3 exhausted four reconciliation steps after `inst:kharad-road-keepers` referenced unknown `loc:kharad-rhythm-road`. Preserve the root, receipts, service invocation `d9254cd9b77946aebcf7a7fdae821402`, and failed patch sequence through 8964a92 as immutable evidence. Do not resume it.
scale_checkpoint: Runs 108 through 115 prove load and failure properties of the pre-rebuild body, not world completeness. The 1,200 and 2,400 actor figures are synthetic evaluation profiles only. Production expansion is sparse and causal; structural admission cannot require interest, diversity, name uniqueness, or an actor count. The committed replacement authority suite passes, but no further scale run is admitted until Yggdrasil serves the exact world-v2 release through the rebuilt Idunn recipe/binding/router seam, the live state root satisfies the complete world-v2 allowed-path contract, restart preserves exact journal and digest identity, and no old service, state path, process grant, or route can regain write authority.
presentation_checkpoint: The historical press-layout and seed-ownership split are complete. `notes/historical-newspaper-layout-grammar.md` remains the durable grammar. Manifest v2 at `output/tex/canopy-ledger-run-61-style-1847-flow-723.manifest.toml` independently binds `style_seed=1847`, `flow_seed=723`, frozen source SHA-256 `8f195140f52a40ba705d6a66987146a1500ae89668e5d82b01d1792eb3afb882`, and the final artifact `output/pdf/canopy-ledger-run-61-style-1847-flow-723.pdf`, SHA-256 `a457f4b1702a7a52480e42fce0039f0dbe677ff32958e98f1c412b346237190c`. An identical seed pair produces byte-identical TeX and PDF; changing only flow preserves the exact style section while materially changing a plausible layout, and changing only style preserves flow topology. Cut-first and cut-midstory templates pass visual inspection; the failed split-card template is deleted. Frozen copy/assets, actual PDF `/BM /Multiply`, and economic-layer advertising authority remain invariant.
public_reference_checkpoint: The published public architecture is immutable pre-rebuild history, not current rebuild authority. Canonical Ghostlight commit `15ea0f0` owns five archived pages covering the former overview, authority, pipelines, 43 named production stages, and eight titled elaborators. Site commit `2035e799c2cf7470b2bfc70d5a878d5d3be5e90f` publishes a shared mobile Home/Blog/Docs masthead, visibly marks every Docs page as a teardown archive, and publishes the postmortem `The World Counter Lied` at `https://ghostlight.gamecult.org/Blog/the-world-counter-lied`; live HTTP inspection returned 200 for the postmortem and Docs index and found the masthead and archive banner. Do not use the archived pages to steer the whole-machine rebuild. `docs/architecture/ghostlight-dungeon-mvp.md` owns the adopted target; publish replacement architecture only after the replacement body is implemented and verified. The site repository owns public composition and deployment.
next_action: Rebuild Idunn's deployment seam before releasing another brake. Replace hard-coded target policy, raw executable command records, root Git inspection, and gamecult-ops target programs with one typed target recipe and operator-binding contract. Put visible recipes and unit templates in Ghostlight and CodexConnector; configure exact refs, runner containers and affordances, host paths, secrets, routing, rollout, retention, and singleton placement in Idunn-owned bindings. Start each candidate on a private endpoint, require signed staged readiness, then let Idunn perform the process/write-admission handoff and stable-route swap. Deploy Connector and Ghostlight through that path, prove continuity and negative legacy authority, and only then purge old units, releases, state roots, acceptance debris, and local run scaffolding.
next_action: Integrate the landed Idunn contracts into its main control plane and narrow Git, runner, workload, process-write-lease/fencing, route, CultCache, and CultMesh drivers before releasing another brake. Admit visible Ghostlight and CodexConnector recipes through Idunn-owned bindings. Publish Expected from the sealed plan and release, record Idunn-observed activation, require service-signed Present, grant the process-bound lease before writable state opens, require Odin-correlated Ready, and only then move stable route membership. Deploy Connector and Ghostlight through that path, prove continuity and negative legacy authority, and only then purge old units, releases, state roots, acceptance debris, and local run scaffolding.
gestalt_population: Gestalt Personas own shared population baselines; persistent member deltas own named individuality; WorldKernel materialization and approval-gated fission preserve lineage and identity. Materialisation/folding changes only representation and the exact member delta, advances resolution epoch, and retires the old cover; it has no Gestalt-wide effect authority. Selected actionable member exceptions are mandatory Projector perspective owners, so aggregation cannot silently erase their decision. Presence projection is limited to nearby active leaves and exact-location dormant members, includes reciprocal player relationship evidence, and may propose an earned cast without committing it. Simulation cells are derived covers only.