Ghostlight/state/evidence.jsonl

{"note": "VoidBot social intelligence is a first-class Ghostlight consumer: appraiser and relationship/perception training must support human-facing reads, grounded opinions, uncertainty, repair signals, and opinion updates over repeated interaction, not only fictional scene mutation.", "status": "accepted", "ts": "2026-05-02T14:41:30+00:00", "type": "architecture"}
{"note": "Generated environment images are accepted only as concept/material reference for illustrated IF. Multi-angle or branch-consistent replay needs a durable scene-set/blockout/layout source with named cameras and staging slots; imagegen should paint over camera-specific visual input rather than preserve room topology from memory.", "status": "ok", "ts": "2026-05-04T11:20:03+00:00", "type": "visual-doctrine"}
{"note": "Coordinator seam correction: future training-shaped loops should sandbox coordinator turns as their own promptable organ. Codex acts as meta-coordinator, preparing inputs, launching/reviewing workers, labeling interventions, and wiring structured state; raw coordinator training data must not be silently collapsed into omniscient chat steering.", "status": "ok", "ts": "2026-05-04T17:14:29+00:00", "type": "architecture"}
{"note": "Character cognition seam: Ghostlight machinery should be maximally smart, but characters must reason and socially maneuver only to the level supported by their modeled intelligence, culture, role, experience, stress, and state. Coordinator/narrator prose may translate opaque high-context tactics for reader legibility without granting that explanation to characters.", "status": "ok", "ts": "2026-05-04T18:44:45+00:00", "type": "architecture"}
{"note": "CultCache wire contract clarified: DatabaseEntry payloads must be MessagePack arrays indexed by explicit field keys with nil gaps for reserved/deleted slots; cultcache-py now exposes define_database_entry_type for that contract and CultLib generator was patched to preserve sparse key slots.", "status": "accepted", "ts": "2026-05-06T03:57:10+00:00", "type": "architecture"}
{"note": "Ghostlight agent-state schema is now the first shared cross-runtime payload contract. CultNet clients should carry ghostlight.agent_state.v0 unchanged inside typed document envelopes, with CultLib-style auth/session semantics handled by the transport layer rather than bespoke per-repo glue.", "status": "accepted", "ts": "2026-05-06T04:49:20+00:00", "type": "architecture"}
{"branch": "codex/ghostlight-dungeon-mvp", "note": "Multiplayer is an intended post-solo extension of the existing one-WorldKernel, many-actor authority model. Multiple authenticated humans will control distinct actors through the same campaign mailbox, perception gates, initiative, and atomic commit path; no party prompt or room-state authority is introduced. The paid alpha remains single-player while multiresolution Gestalt proof stays the immediate forge priority.", "status": "accepted", "ts": "2026-08-18T14:36:02+00:00", "type": "design"}
{"note": "DELVE/HOLD boundary: live Ghostlight WorldKernel, multiresolution agency, typed transitions, persistence, and receipts are reusable, but current InstitutionState and strategic resource handles do not implement HOLD quantities, prices, recipes, capacity, inventories, orders, contracts, or conservation. Delvehold therefore retains quantitative economy authority; a forced ontology may bypass world generation but never WorldKernel validation. Owner witnesses: crates/ghostlight-dungeon/src/domain.rs and F:\\Projects\\Delvehold\\Delvehold\\Game Design\\Shared World\\World State Model.md.", "status": "ok", "ts": "2026-08-26T00:50:11+00:00", "type": "architecture"}
{"note": "Delvehold is a proving consumer of Ghostlight's generic world-simulation API, not a Ghostlight integration organ. Ghostlight may add only generic capabilities: one seed admission primitive shared by compiler and consumer producers, generic externally owned subject authority, consumer-supplied effect schemas, and typed proposals and receipts. The greathold ID, all delvehold.* bindings, and detailed projection/economy translation remain Delvehold-owned. Cells and WorldKernel never switch on consumer-specific names.", "status": "ok", "ts": "2026-08-26T15:55:05+00:00", "type": "architecture"}
{"note": "Supersedes the 2026-08-26T15:51 research note only where it called Delvehold the redirected primary play target: Delvehold is the first proving consumer of the generic world API, while adversarial single-player Dungeon play remains an active regression and context-discovery path. Implemented one compiler/consumer WorldSeed admission transaction, institution-scoped ExternalSubjectAuthority, WorldKernel-owned revisioned snapshots, atomic strategic-wave proposals, acknowledgement receipts, and typed loopback CultNet RUDP operations. Consumer-specific IDs and quantitative economy semantics remain outside Ghostlight.", "status": "ok", "ts": "2026-08-26T16:46:55+00:00", "type": "architecture"}
{"note": "The generic external authority/snapshot contract admits both institution and Gestalt subjects. This closes the Delvehold sovereign-gestalt requirement without adding a Delvehold-specific type: one tagged ExternalSubjectProjection carries either canonical shape, WorldKernel validates exact authority kind and subject ID, refreshes derived agency facets, and keeps the subject non-simulation-eligible while still targetable by foreign proposals.", "status": "ok", "ts": "2026-08-26T17:12:55+00:00", "type": "architecture"}
{"note": "Operator architecture directive: a newspaper is a persistent political/editorial Persona, not a neutral fact summary. Each publication owns audience, remembered beats, narrative memeplex, selective pickup, recurring throughlines, ideological framing, and rivals; competing Delvehold publications may frame one committed event substrate differently. Grounding owns factual assertion/provenance constraints but must preserve clearly legible interpretation, selection, framing, and insinuation. Current Canopy Ledger acceptance remains one publication instance. Do not patch this into the fact-check prompt or derail run43. The detailed owner/state cut belongs in the implementation plan after current acceptance.", "status": "ok", "ts": "2026-08-29T05:15:35+00:00", "type": "correction"}
{"note": "Read-only inspection of immutable Delvehold Run 108 through the focused CampaignStore explorer found a strong authored crisis theater but a failed whole-world complexity shape. The canonical state has 55 locations, 68 institutions, 164 facts, 3,141 Gestalts, 366 Actors, 371 member records, and 2,430 agency relations; exactly 2,400 active leaves are distributed across five realms plus the boundary scene. The eight titled elaborators produce excellent distinct lanes for texture, civic authority, economy, care, politics, secrets, urgent pressure, and numinous meaning. Repeated fission then substitutes taxonomy for novelty: 557 searchable records contain other-unknown, 780 contain residual, many active leaves inherit identical goals, and identity generation repeats public names across distinct people (including at least eight materialized Actors named Mara Venn and four named Nera Quill). Treat this as promising base material for one international crisis region, not yet a plausible entire world or training-ready autonomous narrative substrate. The next world-shape design must gate semantic distinctness, identity diversity, relation/pressure contribution, and horizontal geographic and cultural expansion rather than counting active leaves alone.", "status": "ok", "ts": "2026-09-01T03:06:42+00:00", "type": "research"}
{"note": "Run 115 terminated at revision 2 with 2/8 regions and 0/1 waves after an SSE timeout and a dangling institution location exhausted the model reconciliation workbench. The qualification/verifier/reconciliation/context/timeout/routing patch sequence through 8964a92 did not establish structural ownership. Operator ordered a whole-machine rebuild: one WorldKernel, one typed ontology reducer, one CommandEnvelope/CultCache commit path; NarrativePersona retains Projector-Persona-Interpreter prose isolation, while OperationalAgent is an explicit disjoint controller for operator-shaped cognition. Actor counts and qualitative interest remain evaluation evidence, never admission or completeness authority.", "status": "accepted", "ts": "2026-09-01T12:11:39+00:00", "type": "architecture"}
{"note": "Mind maintenance falsified stale rebuild steering: the map still claimed subtraction had not begun and the handoff later revived Run 111 as an active continuation. Rebuilt the handoff and implementation plan around the adopted one-WorldState authority, landed cuts 64f50de/a144c33, total interpretation, current deletion line, and focused verification gate; chronology remains in Git, evidence, and the frozen teardown map.", "status": "ok", "ts": "2026-09-01T12:37:47+00:00", "type": "architecture"}
{"note": "Rejected and deleted the uncommitted first world.rs foundation after focused tests passed. Review found the public module exposed mutable WorldState and ID issuance, translation-gap inference had become canonical world mutation, empty batches could advance revision, controller commands lacked consumed opportunity/readiness/affordance binding, external ownership was bypassed by world-author authority, command evidence did not bind fact evidence, and batch self-digests were unverifiable. Next cut is private-first: seal WorldKernel/aggregate/journal ownership before reintroducing a minimal reducer behind it.", "status": "rejected", "ts": "2026-09-01T13:03:26+00:00", "type": "architecture"}
{"note": "Commit b53251f lands a private provisional foundation.v0 WorldKernel owner: immutable genesis and exact create retry, sealed authentication evidence, one live CultCache owner, canonical WorldId issuance and reduction kept private, digest/replay recovery, persisted no-op and rejection non-commit, path-identity revocation, and poison/reopen after a simulated post-durable lost acknowledgement. Nine focused world tests pass. The legacy exported kernel remains live; this is the sealed foundation, not cutover.", "status": "ok", "ts": "2026-09-01T14:18:40+00:00", "type": "implementation"}
{"note": "Commit d49b907 makes the replacement Persona interpretation contract structurally total. Persona source prose is immutable noncanonical evidence bound to typed world/controller/opportunity/revision and inference receipts; only exact typed captures may propose state, actual quoted dialogue is required for speech, malformed spans or raw tool payloads become exact whole-source translation gaps, normal step exhaustion adds an unresolved-source gap, and infrastructure interruption discards partial captures and returns the source pending. Ten focused projection tests pass. Legacy exported Persona runners still contain terminal failure paths and do not expose record_gap; they remain deletion targets, so totality is not yet a live-runtime claim.", "status": "ok", "ts": "2026-09-01T14:37:59+00:00", "type": "implementation"}
{"note": "Commits 12ee9f4 and 66ed2ec advance the authority rebuild past the private reducer phase. The first removes 686 lines of dead legacy Elaboration and Mutation ingress without a compatibility writer. The second completes the sealed Draft-to-Active authority loop with canonical controller assignments and affordance grants, revision-bound opportunities, one shared human and autonomous ExerciseDecision reducer, one serialized mailbox, atomic replay, and exact rejection and lost-ack behavior; eighteen focused world tests pass. This is not runtime cutover: the legacy exported kernel and startup, Session Zero, player, autonomous, and recovery paths remain live owners. The next move exposes and wires the replacement runtime identity and mailbox, deleting each old owner without dual-write.", "status": "ok", "ts": "2026-09-01T17:40:32+00:00", "type": "implementation"}
{"note": "Pushed Ghostlight 13d5136 has no legacy runtime modules and one CultCache owner, but Yggdrasil still runs legacy a4080d4. Read-only cutover audit proved the current Idunn path structurally unfit: source/ref/floor policy is duplicated across compiled Rust, raw executable command records, a privileged shell dispatcher, and large gamecult-ops target programs; root Git cannot inspect correctly idunn-owned mirrors; Ghostlight world-v2 purity checks ignore most legacy state; and fixed-port activation stops the incumbent before the candidate is green. Adopted cut: visible target-owned recipes and unit templates, Idunn-configured refs/runner containers/affordances/host bindings, Git and recipe materialization as idunn, narrow sealed privileged consequences, candidate staged health behind a stable router, process/write-lease handoff, atomic route change, and separate deployment versus continuity authority. Do not issue the current Connector or Ghostlight redeploy requests.", "status": "ok", "ts": "2026-09-02T14:10:03+00:00", "type": "research"}
{"note": "Supersedes the 2026-09-02T14:10:03+00:00 Idunn cutover design receipt where it named target-owned unit templates, an executable-affecting-commit selector, and staged health. Odin cebe425 rejects raw repository unit/container templates: targets own constrained launch declarations and the operator-selected workload driver lowers them. Deterministic plan validation retains commit, tree, recipe, and Gitlink facts but does not prove ancestry, signatures, or object custody; a future narrow Idunn source driver must. CultNet 87d0b0f and Odin cebe425 establish Expected, Idunn-observed activation, service-signed Present, process lease before writable state, Odin Ready, and route membership only after Ready. Actuation and Idunn main integration remain absent.", "status": "ok", "ts": "2026-09-02T19:30:00+00:00", "type": "research"}
{"note": "Supersedes the 2026-09-02T19:30:00+00:00 deployment integration checkpoint. Owning Body inspection found CultNet pushed through e542225 (generation-bound activation, lifecycle brake, process lease, provider-observed capabilities, and explicit disagreements) and Odin pushed through d527d72 (exact source freezing and narrow actuator ports), with an uncommitted four-file integration for dynamic systemd isolation, authenticated Ready-only provider selection, protected one-shot activation delivery, and the e542225 gitlink. The remaining deployment owner is not another driver gate: replace control_plane.rs command ownership with exactly DeploymentCommand, DeploymentTransaction, and AdmittedGeneration; persist each of the nine phases before effects; persist prepared activation before start; reject pre-persistence orphans; and atomically complete the transaction with exact admitted-generation CAS. Production cutover remains unproven.", "status": "ok", "ts": "2026-09-03T00:58:55+00:00", "type": "research"}
{"note": "Supersedes the 2026-09-03T00:58:55+00:00 deployment-owner checkpoint. CultNet f4ab237, Odin 65cf2b2, Ghostlight a0b16b9, and CodexConnector ede3c30 land the routed runtime contracts, durable three-record/nine-phase transaction owner, and provider sides. Live admission remains absent. Current Odin projection/RUDP/UDP-route and Rust Odin correlation work is uncommitted; the Nginx route receipt proves configuration plus nginx -T visibility only, not live-worker adoption or packet delivery, so an exact data-plane observation remains required before fence clearance, drain, or cutover acceptance.", "status": "ok", "ts": "2026-09-03T06:13:20+00:00", "type": "research"}
{"note": "Mind and workspace compaction. The evidence ledger was 258 records of which 235 were per-release/per-run receipts, self-consuming falsification chains, and May fixture doctrine already owned by docs/architecture and map hard_boundaries; those moved to state/evidence.archive.jsonl and were deleted from the CultCache evidence document, since evidence.jsonl is a regenerated export and a store-only deletion is the sole durable compaction. Twenty-three records remain: still-binding contracts (CultCache wire format, agent_state.v0, cognition ceiling, image-geometry authority, sandboxed coordinator, VoidBot appraisal, multiplayer extension, the Delvehold boundary set, newspaper-as-Persona) plus the whole rebuild era from Run 108 forward. A duplicate multiplayer note recorded twice under different timestamps was reduced to one. The worktree shed 87MB of untracked debris: three Git bundles whose commits are all ancestors of HEAD, ~60 legacy live-fire run scripts and sftp batches, the forbidden redeploy helpers, downloaded run61-63 acceptance copies whose authoritative roots remain on Yggdrasil and whose frozen copy is digest-bound in output/tex, a redb file created by a stray --help argument, and 71MB of tmp/ legacy campaign caches and newspaper renders. .gitignore now refuses all of it. map.yaml and the handoff had stale frontiers naming 13d5136 and a0b16b9; both now name 6a79cb0.", "status": "ok", "ts": "2026-09-03T20:00:00+00:00", "type": "maintenance"}
{"note": "Core GameCult stack ownership resolved. CultLib is the canonical home for CultCache, CultNet and CultMesh across every runtime because wire parity conformance lives only there; a runtime-specific repo cannot own the engine other runtimes must agree with. The standalone GameCult/cultcache-rs and GameCult/cultnet-rs repos are pre-consolidation origins that kept receiving work after the 5c69bfc import, and Ghostlight became a third lineage by written charter: vendor/README.md declares a locally owned compatible protocol generation, which is duplicate authority over the wire stack held outside the only harness that checks parity. That is why runtime_authority_contracts.rs forked: Ghostlight vendors e542225 while map and handoff declare CultNet f4ab237 authoritative, and the two disagree on whether Present may coexist with a disagreement -- Ghostlight's copy makes them exclusive, f4ab237 separates presence from readiness and gates through into_undisputed_present. Re-vendoring fixes that instance, not the mechanism. CultLib branch claude/consolidate-rust-core-stack commit 34488e8 returns the Rust CultCache engine to CultLib: the standalone body as base (3,714 lines, 46 passing tests) over CultLib's 1,554, with the cultnet-rs RUDP gate passing 20 unchanged. Two CultLib-only commits remain unported debt. cultmesh-rs is homeless: the only Rust CultMesh implementation in existence is 1,363 lines inside Ghostlight's vendor, absent from CultLib and from any repo, so it has never been parity tested against the browser, Kotlin and TypeScript implementations it must interoperate with. Ghostlight must consume CultLib by pinned rev and stop vendoring before the standalone repos are retired.", "status": "ok", "ts": "2026-09-03T21:00:00+00:00", "type": "architecture"}
{"note": "Ghostlight's vendored core-stack fork is retired at d0510ac: cultcache-rs, cultnet-rs and cultmesh-rs now come from CultLib pinned at 85f7024 and vendor/README.md's 'locally owned compatible protocol generation' charter is deleted with them. The predicted migration did not exist. RuntimePresenceCorrelation moving from enum to struct is Odin's side of the contract and no Ghostlight file references it; with line endings normalised the e542225 and f4ab237 copies differ by 132 lines, and the only production change reaching a provider is IdunnExpectedRoute requiring rudp:// schemes for rudp transport, which this service does not use. Ghostlight compiled unchanged and passes 89 workspace tests against the pinned rev. One thing was nearly lost: the vendored transport.rs alone checked a framed payload length against the advertised maximum before allocating, so a four-byte header could otherwise size a buffer to whatever a peer claims; it is now CultLib 85f7024 with a test. Verified by diffing all twelve vendored cultnet files against CultLib before deleting rather than after. vendor/ still holds the cultcache-py and eve submodules; cultcache-py is the same runtime-specific-repo pattern and CultLib carries packages/cultcache-py, but it backs the state tooling rather than the daemon.", "status": "ok", "ts": "2026-09-03T23:13:55+00:00", "type": "architecture"}
{"note": "The pre-existing worktree drift is landed at 751b5c4 and 322cc11. The daemon no longer names GHOSTLIGHT_RUNTIME_ID, GHOSTLIGHT_DUNGEON_BIND or GHOSTLIGHT_DUNGEON_ROOT under management; Idunn supplies the runtime id in the activation bundle, the candidate bind, and the state root as a recipe argument binding. That binding is required rather than cosmetic: Odin deployment.rs refuses a stateful workload with no state_root argument binding and refuses one whose binding disagrees with the admitted root, so the old recipe could not have deployed. The acceptance harness identity is renamed GHOSTLIGHT_ACCEPTANCE_RUNTIME_ID so a test-supplied id cannot be read as the managed one. 89 workspace tests pass. Provenance finding that changes the cultnet-rs retirement gate: the contract revisions the Mind cites, CultNet f4ab237 and its predecessor e542225, are not ancestors of CultLib main and exist only on GameCult/cultnet-rs branch codex/idunn-runtime-authority-contract. Their content is on CultLib main at 85f7024, verified by symbol, but the SHAs are not, because the consolidation ported commits forward rather than merging them. Deleting GameCult/cultnet-rs therefore breaks every citation in map.yaml, the handoff, both notes and the evidence ledger. Odin 65cf2b2 and d527d72 are likewise off Odin main, on pushed branch codex/ygg-idunn-independent-bootstrap, which is resolvable and needs no action.", "status": "ok", "ts": "2026-09-03T23:26:24+00:00", "type": "architecture"}
{"note": "Live contract citations are re-anchored from CultNet f4ab237 onto CultLib 85f7024 across map.yaml, the handoff, and both notes. Verified before swapping rather than assuming equivalence: at 85f7024 packages/cultnet-rs carries IDUNN_LIFECYCLE_BRAKE_* distinct from IDUNN_DEPLOYMENT_BRAKE_*, IdunnProcessWriteLeaseRecord, GameCultRuntimeCapability, OdinTopologyDisagreement with disagreements() and into_undisputed_present separating presence from readiness, generation-bound IdunnRuntimeActivationRecord with a distinct activation-proof signing purpose, and IdunnExpectedRoute rejecting non-rudp:// endpoints for RUDP routes. All six cited contracts hold. 85f7024 is both CultLib's current main head and a permanent ancestor of main, so the citation survives every future advance, which f4ab237 never could. Two citations were instructions rather than descriptions and could not be swapped mechanically: map.yaml next_action and the handoff next gate both said advance Odin to CultNet f4ab237, which would have advanced Odin deeper into the repo being deleted. Both now say repoint Odin off its vendored CultNet fork onto CultLib 85f7024 as Ghostlight did at d0510ac. Evidence records keep their pre-consolidation SHAs as dated history; this record is the resolution key for reading them. The retirement gate for GameCult/cultnet-rs is now one item: Odin's vendored CultNet gitlink is the last reader of that repo.", "status": "ok", "ts": "2026-09-03T23:51:32+00:00", "type": "architecture"}
{"note": "Odin is repointed off the vendored core-stack forks onto CultLib, closing the last code reader of GameCult/cultnet-rs. The forks were not pure duplication: a whole-file symbol comparison, not a diff of recent changes, found four capabilities CultLib lacked. cultnet-rs needed reliable send expiry, where a reliable packet past its deadline is dropped rather than retransmitted because live media tolerates loss but not lateness; cultcache-rs needed both compare_exchange_snapshot and a per-entry compare_exchange with CultCacheExpectedEnvelope, which CultLib lacked despite carrying the larger body. All are ported with tests on CultLib branch claude/cultnet-reliable-expiry at cbde940. The expiry design moved during the port: CultLib now lets the advertised transport profile own each channel's expiry rather than a runtime field that can disagree with the profile a peer was shown, which is where Odin's fork already had it. That field is wire-visible and Rust peers now advertise it on the media channel; TypeScript, C# and Kotlin accept it unchanged across five passing interop lanes each, and the other four runtimes should grow it. Python lanes cannot run on this machine because its Python runtime has no msgpack, and they fail identically before and after. Two Odin test failures are pre-existing rather than caused by the repoint, verified rather than assumed: idunn-daemon fixtures use /srv paths that Path::is_absolute rejects on Windows, and a muninn test expects an Unreliable media channel while every cultnet lineage including both previously pinned revisions declares it Reliable. Odin's recipe required the vendor/cultnet-rs gitlink, so removing the submodule would have made it unadmittable; the core stack is now pinned by rev in Cargo.lock inside the frozen source tree instead of by a gitlink Idunn verifies directly.", "status": "ok", "ts": "2026-09-04T02:02:32+00:00", "type": "architecture"}
{"note": "Swarm-wide core-stack consolidation. A survey of every vendored copy under F:/Projects found the divergence far smaller than the number of forks implied: against CultLib, Epiphany's CultCache, CodexConnector's CultCache, VoidBot's CultCache-TS and Ghostlight's CultCache-Py each hold nothing unique. What the forks mostly held was reach rather than capability, and one earlier claim was wrong: raw_document_record_from_envelope was reported missing from CultLib when it was present but private, because a pub-fn scan cannot distinguish a visibility difference from an absence. It is public now, and CultMesh gained get_all_with_keys and soa, two genuinely absent delegations to CultCache. With those exposed, Epiphany repointed to CultLib with zero code changes and 16 green test binaries, and CodexConnector with zero changes and 35 tests; both now carry no submodules at all. CodexConnector's fork held the pre-migration RuntimePresenceCorrelation enum, but the connector never referenced the type, so that migration cost nothing. Each consumer had pinned a different branch of the standalone repos -- resident-retention-compaction, public-anchor-parent-permissions, canonical-binary-slots, idunn-runtime-authority-contract, windows-atomic-replace-retry -- which is the combinatorial explosion that made separate repos untenable. Remaining forks are non-Rust and blocked on distribution rather than divergence: npm and pip cannot consume a package from a subdirectory of a git repo the way cargo git dependencies can, CultLib has no publish workflow, and a whole-monorepo submodule costs 140MB to replace a 104KB package.", "status": "ok", "ts": "2026-09-04T02:27:13+00:00", "type": "architecture"}
{"note": "The TypeScript and Python forks existed because nothing was publishable, not because the code diverged: npm and pip cannot consume a package from a subdirectory of a git repo the way cargo git dependencies can, so vendoring was the only way to depend on CultLib. CultLib 8cb3b72 adds a tag-triggered publish workflow for @gamecult/cultcache-ts to npm and cultcache-py to PyPI, each refusing a tag whose version disagrees with its manifest, with PyPI on trusted publishing so no long-lived token is stored. Licensing was the blocker discovered on the way: cultcache-py declared itself 'Private GameCult infrastructure' and cultcache-rs and cultmesh-rs declared no license at all, inside a repo whose LICENSE is MIT and whose every other package says MIT. That was load-bearing rather than cosmetic, because a package calling itself private is not one to push to a public registry; the operator confirmed the swarm is MIT and all three now say so. cultcache-ts is scoped to @gamecult so CultLib holds the name unambiguously on a public registry, which moves CultLib's own cultmesh-ts and cultnet-ts imports with it. Ghostlight's own repoint is not a dependency swap: ghostlight_state_store.py puts vendor/cultcache-py/src on sys.path precisely so the state tooling runs from a clone with no install, and session bootstrap depends on that, so replacing it with a pip dependency trades a fork for an install step unless bootstrap installs it.", "status": "ok", "ts": "2026-09-04T02:42:08+00:00", "type": "architecture"}
{"note": "CultLib main is at 8cb3b72. The consolidation work landed by fast-forward rather than squash, which mattered because four repos pin revisions from that branch: Ghostlight 85f7024, Epiphany and CodexConnector e171eca, Odin cbde940. All four verified as ancestors of origin/main after the push, so they resolve from a fresh clone; a squash merge would have orphaned every one of them and broken the builds it was meant to unify. Rust packages green at the merge point: cultcache-rs 53, cultnet-rs 107, cultmesh-rs 7. The merged branch is deleted, its commits reachable through main.", "status": "ok", "ts": "2026-09-04T11:02:22+00:00", "type": "verification"}
{"note": "Odin 27cc815 consumes CultCache and CultNet from CultLib; vendor/cultmesh-rs is the last fork and itself consumes CultLib, so exactly one version of each crate spans the graph. The commit had to carry the operator's in-flight CultMesh RUDP document server because it is a prerequisite rather than a coincidence: the previously committed CultMesh calls assume_connected(), a CultNet method the fork carried and CultLib does not, so the old code cannot build against CultLib at all. That was established by reverting the file and watching it fail, after an attempt to split the repoint into two independently building commits. The same test was run on the in-flight idunn-daemon work and it passed, so those five files were left uncommitted and the committed tree was verified to build without them. Three CultLib API differences needed adapting in Odin: transport options carry a reconnect_policy the fork lacked at seven sites, create_ack builds from ack state and cannot fail, and the transport profile owns each channel's reliable expiry. Odin's Idunn recipe still declares required_gitlinks = [vendor/cultnet-rs] and will refuse admission until that line is dropped; the fix exists in the working tree but the deployment directory is untracked, so it could not be committed. Source custody for the core stack now rests on the revision pinned in Cargo.lock inside the frozen source tree rather than on a gitlink Idunn verifies directly.", "status": "ok", "ts": "2026-09-04T12:56:04+00:00", "type": "architecture"}
{"note": "Swarm triage: every repo under F:/Projects is now clean and pushed. Two findings bear directly on Ghostlight's deployment gate, both caused by the core-stack consolidation removing submodules that Idunn was still told to expect. Odin's deployment/idunn/recipe.toml declared required_gitlinks = [vendor/cultnet-rs], and gamecult-ops' operator binding templates declared gitlinks for vendor/cultcache-rs and vendor/cultnet-rs on codex-connector and vendor/cultnet-rs on odin; Idunn would have refused to admit those targets for gitlinks it could not find. All are corrected and committed at Odin eedce4f and gamecult-ops 8f7ae2a. Ghostlight's own binding is untouched because vendor/cultcache-py and vendor/eve still exist. The rest of the triage: Odin eedce4f also lands 4,167 lines of real in-flight work including UDP route actuation via RouteBinding::stable_socket and an NginxStreamUdp driver, plus the new odin-daemon crate, which cannot compile on Windows because it reads systemd listen file descriptors through std::os::fd, so Linux CI is its first witness. Epiphany 616a2c8e was an interrupted cargo fmt run rather than a feature, finished rather than reverted. Aetheria reclaimed about 1.6GB of scratch checkouts and sandboxed toolchain caches, all verified clean with no unpushed commits first, and the cleanup was scoped to the debris so Unity's Library and Build survived. Two apparently stranded commits turned out to be duplicates already upstream under different SHAs, found by patch-id rather than by subject.", "status": "ok", "ts": "2026-09-04T13:17:04+00:00", "type": "architecture"}
{"note": "Run 115 root cause is vocabulary-shaped, not model-shaped. Legacy transition.rs used caller-supplied SubjectRef{kind,id:String}, two-phase AdmitEntity{initial_components}, and a flat Vec<PermittedWorldMutation>, so a dangling reference like inst:kharad-road-keepers -> loc:kharad-rhythm-road was a runtime discovery rather than an unrepresentable input; reconciliation existed only to repair that class and exhausted after four steps. Depth lived in free strings (posture, resource_kind, capability_id, persistent_features), so the prior attempt to fix shallowness added model tribunals (ElaboratorTitle, WorldComplexity*Qualification, *Verification) as compensators for an ontology with nowhere to hold depth. Adopted cut: reducer-issued typed ID namespaces, draft handles resolved inside one closed WorldPatch before any ID allocates, twelve decision-constraining components, and elaboration that answers a derived CausalBoundary instead of running waves and quotas. Recorded in docs/architecture/ghostlight-world-ontology.md.", "status": "ok", "ts": "2026-09-04T13:39:08+00:00", "type": "research"}
{"note": "Ontology v2 unifies elaboration and character action under one WorldPatch and one deterministic verifier. Three decisions change future belief: (1) affordances are world-authored data (preconditions, effect slots, weighted outcome bands) over a closed 29-operation kernel set, so genre lives in the seed and the kernel never learns one; (2) uncertainty is resolved by kernel entropy seeded from world/revision/command, so no model ever chooses success, which deletes the legacy wave-level outcome resolver; (3) proposals bind to a scope digest of the components their verification reads rather than the whole state digest, so eight elaborator loops and many subjects do not serialize on one revision, replacing the stale-means-discard rule. Elaborator tools are a derived projection of the operation set and cannot drift. ghostlight-multiresolution-agency.md is demoted to teardown evidence keeping only resumable sessions, compact drafts, and the complete mismatch set.", "status": "ok", "ts": "2026-09-04T14:01:12+00:00", "type": "research"}
{"note": "Operator correction, 2026-09-04: the 2,400-subject / 240-cell / 10% cover profile is a design target, not a load fixture. A world feels alive only when actors at every level pursue their own goals; that requires generating that detail first and then choking multiresolution simulation so attention is scarce and selection is forced. The mvp doc sentence calling the profile \"test data, not a production elaboration target\" was teardown-era text, not operator design, and is amended. Ontology v2 now carries: an authored WorldScaleIntent with a structurally counted deficit (qualified subject = active, one controller, one Goal commitment, one affordance) that elaborators pursue after boundaries; a budgeted connected cover every tick with singleton detail cells and grouped coarse cells; per-constituent attribution and partitioned knowledge in grouped cells; debt rotation. Still deleted: gestalt as canonical identity, arena knowledge union, semantic qualification and verification models, fission quotas as mutation, string identifiers.", "status": "ok", "ts": "2026-09-04T14:14:10+00:00", "type": "research"}
{"note": "Codex CLI fan-out that must commit cannot run in a linked git worktree. A linked worktree's .git is a file pointing into the parent repo's .git/worktrees/, which is outside the Codex sandbox's writable roots, so every git commit fails with index.lock Permission denied; the default sandbox also blocks outbound push. All four world workers died on this on 2026-09-04. Fix: full clones at the same paths (F:/Projects/Ghostlight-worlds/<world>, F:/Projects/<Lore>-worktrees/ghostlight-worlds; .git is a directory despite the directory name) and launch with -c sandbox_workspace_write.network_access=true. Uncommitted worker output was banked by hand to codex/world-<world> and codex/ghostlight-worlds before the worktrees were removed. Rule for any future Codex fan-out that writes: give each worker a clone whose entire .git lives under its own writable root, and grant network if it must push.", "status": "ok", "ts": "2026-09-04T14:18:47+00:00", "type": "verification"}
{"note": "Supersedes the 2026-09-04T14:18 clone-plus-network record, which was necessary but not sufficient. The Codex workspace-write sandbox keeps .git read-only even when the whole clone sits under the writable root, so a Codex worker can never commit or push regardless of clone layout or network grant. Rule for any Codex fan-out that must produce committed work: the worker writes files only; a supervisor outside the sandbox commits and pushes the clone after the worker exits. The world elaborator scheduler (C:/Users/Meta/.claude/worlds/Invoke-Elaborators.ps1) does this per slot to slot/<world>/<title>/<stamp> branches in both the Ghostlight world clone and the lore clone, recording completions in logs/elab-done.csv; integration into codex/world-<world> and codex/ghostlight-worlds is a separate deliberate pass. First banked fixture: Delvehold cistern-house-nine-breaker-test, codex/world-delvehold 9374fd0.", "status": "ok", "ts": "2026-09-04T15:04:24+00:00", "type": "verification"}
{"note": "Plan step 6, the ontology widening, is complete: ten passes landed on codex/ghostlight-dungeon-mvp between 2026-09-04 and 2026-09-05, each as a Hands cut in an isolation worktree, a Soul falsification in the same tree, and a fast-forward integration. Pass tips: 1 typed ID namespaces and closed patch resolution 5e53beb; 2 Position/Route/containment and scope-digest binding e99af63; 3 Custody/Dependency/conservation d2805fe; 4 world-authored affordance catalog with kernel-entropy bands 0f21a49; 5 Authority/Selection/Redress dbe176d; 6 Knowledge/Channel/Fact standing cb6a126; 7 clock, Commitment, Pressure, derived CausalBoundary and the structural answer rule 1852ddd; 8 confined elaborator lane and derived tool catalog 3ed3868; 9 budgeted connected cover with tick-driven fairness ceil(N/R), R = cells minus urgency slots, verified 22 ticks at the 2,400/240 profile 8aebfb6; 10 confined external consumer ingress over POST /cultnet/world-patch a1fd645. The kernel now holds 12 decision-constraining component kinds over 27 named operations under one WorldPatch, one reducer, one CAS commit, one decode bound for both authoring lanes, and three confined SystemCapability arms (Clock, Elaborator, Consumer); the action vocabulary is data in the seed and the kernel never learns a genre. The eleven plan invariants hold structurally at the end of the series per Soul: one deterministic reducer and atomic commit; kernel-derived authority; one controller per scope with no fallback or double action; total interpretation with exact gaps; deterministic structural rejection without a model verifier; scoped knowledge until explicit communication; external-consumer sovereignty; sparse causal sufficiency with counts as evidence only; restart reconstructs the exact world; IDs allocated only inside an admitted reduction; opportunities bound to a scope digest rather than a revision. The pairing invariant is re-decided at three gates by doctrine, not by a repair loop. Test surface grew from 43 world / 83 crate at the series start to 313 world / 357 crate source functions at a1fd645 (focused world:: run 312 / 352). Two design decisions remain with the operator and are recorded nowhere else durable: whether a refused coupled constituent may re-submit once inside the same tick, to be decided with the submitted-versus-committed number in hand; and the authority for an owner-only Eve world.run_tick command. The next seam after the series is the outbound consumer response batch and a non-loopback CultMesh lease.", "status": "ok", "ts": "2026-09-05T02:13:22+00:00", "type": "implementation"}
{"note": "First local live smoke of the rebuilt kernel (2026-09-05): production tick driver, cover, Persona membrane, operational lane, clock, and elaboration sweep ran three ticks against a real CodexConnector (head daemon, ChatGPT auth) on a genesis world; revision 2->11, two singleton cells per tick, Persona spoke each tick, elaboration clean (nothing derived to answer). Wall time 40-70 s per tick. The road works; prose is thin because genesis is three subjects in one room with one affordance, which is the seed-producer gap. Runbook: notes/local-live-smoke.md. Stale: the pre-pass-6 ignored acceptance test in controllers.rs fails at NoAudience.", "status": "ok", "ts": "2026-09-05T13:42:18+00:00", "type": "verification"}
{"ts": "2026-09-05T17:36:41+00:00", "type": "verification", "status": "ok", "note": "Seeded live smoke passed (2026-09-05): from the Kalsa Public vault, one seed session authored six qualified persons into Low Sere in one round (39 s), deficit 6->0; the world activated with nine subjects and six boundaries; three ticks of eight singleton cells each (95-123 s) with the seeded people speaking to each other by name. Twelve runs; every failure was on the road and each became a rule: one credential family (real codex home), strict schemas (anyOf, typed tags, offline totality test), a supported Persona model, expiry skew vs response timeout, ids beside labels in the brief, seed budget 24 with parallel calls and budget-end submit, content-addressed provider request ids, the commitment shape rule in the tool description, and the placement rule. The harness fails on an empty seed or a silent world."}