No description
  • Rust 98.4%
  • TypeScript 1.6%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Meta Vens 0808c6a7fd Cut 14: refuse a stale tab's token, a token smuggled via bindings, and a leaked seed config name (PA.f178, PA.f179, PA.f180, seed refusal)
PA.f179 (runtime side): the `world.play` gate compared
`payload.answer_token.as_deref() != Some(question.token.as_str())`, which
forced `question.token`'s own `""` fallback (play.rs's own PA.f179 fix,
previous commit) into a value an attacker could literally send. Extracted
to `answer_token_admits(given, expected)`, which requires both sides
`Some` and equal — `expected: None` refuses unconditionally, including
against `given: None` or `given: Some("")`. Directly unit-tested
(`answer_token_admits_only_two_present_and_equal_tokens`), independent of
the HTTP round trip.

PA.f178: with no question currently open, `payload.answer_token` was
never read at all — a stale tab resubmitting its own spent token fell
through to `answers: None`, and its stale prose silently opened a *new*
turn, spending a real inference budget on an answer to a question that no
longer exists. A token arriving with no question open is now refused
outright ("that question is closed"), before `admit` is ever called.

PA.f180: `unwrap_bindings` merged the envelope's `bindings` object and a
button action's own sibling fields into one map with no memory of which
channel a field arrived on. `answerToken` is only ever legitimately an
action-sibling field (`eve.rs` never renders it as a captured control),
so a request built by hand that sent the *correct* token through
`bindings` instead would have been indistinguishable from the real thing.
`ACTION_ONLY_PAYLOAD_FIELDS` (currently just `answerToken`) is now
checked before the merge and refused if found inside `bindings`; every
other command's own real shape (action fields as siblings, captured
values inside `bindings`, arriving together) is unaffected.

Seed refusal leak: `seed_once`'s vault-root refusal named
`GHOSTLIGHT_SEED_VAULT_ROOT` directly to the player — a fact about this
process's own environment, not about the world (invariant 8). Replaced
with a player-safe "seeding is not available on this world"; the actual
env var name is still logged at `warn` for the operator. The other
refusals on this route (`seeding a world is its owner's lane`, `the
cognition organ is closed`, `VaultEvidenceSource::open`'s own errors,
which are deliberately vault-relative and never carry a path) were
checked and do not leak. `ControllerError`'s own `Display` (from
`runner.sweep`) is out of scope for this cut — see the Hands report for
why.

PA.f176: `eve_client_bridge_is_available()` checked only `node
--version` and that the vendored lowering's *committed* `dist/index.js`
is a file — always true regardless of whether either vendored package's
own `npm install` had ever run. Measured: with `node` present and no
`npm install` run anywhere, the old check reported "available" and the
four gated tests failed outright on `jsdom`; after installing only
`eve-browser-lowering`'s own deps, still failed on `ajv` (the sibling
`eve-contracts` package's own dependency, in its own `node_modules`,
which an install scoped to `eve-browser-lowering` never populates). The
check now spawns a real `node` process that does exactly what
`tools/eve_client_bridge.mjs` does at import time (resolve `jsdom`
through the lowering's own `package.json`, then dynamically import the
built `dist/index.js`, which is what actually pulls in `eve-contracts`
and `ajv`) and reports "available" only if that succeeds — cached behind
a `OnceLock` so the four gated tests share one real probe. All four
SKIPPED messages updated to name both vendored packages' own `npm
install`.

Tests added: a_stale_tabs_spent_token_is_refused_and_never_opens_a_new_turn,
an_answer_token_sent_as_a_captured_binding_is_refused_not_admitted,
an_ordinary_answer_with_text_via_bindings_and_token_as_a_sibling_is_still_accepted
(negative proof for PA.f180), answer_token_admits_only_two_present_and_equal_tokens,
the_unconfigured_seed_vault_refusal_does_not_name_the_environment_variable.

Mutations verified by hand this pass (applied, confirmed the named test
failed, then reverted):
- removing the `payload.answer_token.is_some() && !is_awaiting_player`
  guard: a_stale_tabs_spent_token_is_refused_and_never_opens_a_new_turn
  fails (the stale resubmission is wrongly "accepted").
- reverting `answer_token_admits` to
  `given.unwrap_or_default() == expected.unwrap_or_default()`:
  answer_token_admits_only_two_present_and_equal_tokens fails (`None,
  None` and `Some(""), None` wrongly admit).
- removing the `ACTION_ONLY_PAYLOAD_FIELDS` check from `unwrap_bindings`:
  an_answer_token_sent_as_a_captured_binding_is_refused_not_admitted fails
  (the smuggled token is wrongly "accepted").
- reverting the seed refusal to
  `format!("{SEED_VAULT_ROOT_ENVIRONMENT} is not configured")`:
  the_unconfigured_seed_vault_refusal_does_not_name_the_environment_variable
  fails.
- making `eve_client_bridge_is_available()` return `true` unconditionally
  once `dist/index.js` exists (the pre-PA.f176 shape): with both vendored
  packages' `node_modules` removed, the suite goes from 170 passed to 166
  passed / 4 failed with a real `Cannot find module 'jsdom'` node crash —
  reproducing the exact bug this cut fixes.

cargo test -p ghostlight-dungeon --bin ghostlight-dungeon: 170 passed,
with both vendored packages' own dependencies installed. With `node`
present and both packages' `node_modules` removed: 170 passed, 0 failed,
4 skipped (verified this pass by temporarily moving both directories
aside and restoring them afterward). A true "no `node` on PATH" run could
not be produced in this sandboxed workstation (multiple node shims exist
on PATH outside the vendored packages); the early `node_on_path` check
this cut did not touch is unchanged from before, and
`the_committed_eve_client_bridge_fixture_round_trips_through_api_router_with_no_node`
already proves the node-independent fixture-replay path.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-23 04:30:43 +02:00
acceptance Rebuild qualified world elaboration 2026-09-01 09:54:04 +02:00
assets/newspaper/woodcuts Build seeded TeX newspaper press 2026-08-30 18:30:56 +02:00
crates Cut 14: refuse a stale tab's token, a token smuggled via bindings, and a leaked seed config name (PA.f178, PA.f179, PA.f180, seed refusal) 2026-09-23 04:30:43 +02:00
deployment/idunn Give the world library a sealed public boundary 2026-09-16 02:06:07 +02:00
docs Record Soul on Cuts 12 and 13 (PA.f176-PA.f182) 2026-09-23 03:39:49 +02:00
examples Keep the world elaboration record and first-generation world fixtures in Ghostlight 2026-09-13 16:35:03 +02:00
experiments Keep the world elaboration record and first-generation world fixtures in Ghostlight 2026-09-13 16:35:03 +02:00
notes Scope the interpretation boundary to the library, and mark step 16 as cutting 2026-09-23 03:52:42 +02:00
output Separate newspaper house style from issue flow 2026-08-30 19:34:37 +02:00
prompts Keep the world elaboration record and first-generation world fixtures in Ghostlight 2026-09-13 16:35:03 +02:00
schemas Add initiative scheduler artifact seam 2026-05-04 23:58:07 +01:00
scripts Correct re-entry steering after the fan-out 2026-09-04 15:58:55 +02:00
sidecar/claude-sdk Add granting and revoking affordances to the world kernel (play agent Cut 5, PA-Q10) 2026-09-22 04:54:35 +02:00
state Scope the interpretation boundary to the library, and mark step 16 as cutting 2026-09-23 03:52:42 +02:00
tools Refuse to type into a disabled control in the Eve client bridge (PA.f174) 2026-09-23 02:28:01 +02:00
vendor Replace vendor/cultcache-py submodule with published PyPI dependency 2026-09-13 16:08:19 +02:00
web Rebuild Ghostlight around explicit world authority 2026-09-02 07:21:11 +02:00
.gitignore Add the Claude SDK sidecar: framing, the closed schema converter, the query 2026-09-06 02:10:33 +02:00
.gitmodules Replace vendor/cultcache-py submodule with published PyPI dependency 2026-09-13 16:08:19 +02:00
AGENTS.md Replace vendor/cultcache-py submodule with published PyPI dependency 2026-09-13 16:08:19 +02:00
Cargo.lock Use UAX #29 word boundaries in SourceSpan::locate (PA.f78) 2026-09-22 16:25:32 +02:00
Cargo.toml Use UAX #29 word boundaries in SourceSpan::locate (PA.f78) 2026-09-22 16:25:32 +02:00
CLAUDE.md Wire AGENTS.md into Claude Code memory 2026-09-03 22:22:51 +02:00
package-lock.json Adopt Ink for branching scenes 2026-05-01 23:52:15 +01:00
package.json Replace vendor/cultcache-py submodule with published PyPI dependency 2026-09-13 16:08:19 +02:00
README.md Give the world library a sealed public boundary 2026-09-16 02:06:07 +02:00

Ghostlight

Ghostlight builds persistent generative people and worlds. Its active product is Ghostlight Dungeon: a Vault-grounded narrative simulation in which places, knowledge, relationships, institutions, clocks, and consequences survive beyond the model's current context.

The project began as a research and fixture pipeline for socially persistent Aetheria agents. That material remains useful regression evidence. The live machine is now a Rust runtime with typed campaign state, one canonical world authority, bounded Persona projection, fiction-first action resolution, and a multiresolution agency graph for keeping large settings active at finite cost.

What Ghostlight Owns

  • WorldKernel is the sole owner of committed campaign state and revisions.
  • Every player command, NPC action, strategic tick, wait, import, and reload enters the same validated campaign mailbox and atomic CultCache commit path.
  • Foreground actions, NPC reactions, strategic Gestalt activity, waits, travel, and population fission lower into one closed semantic world-mutation algebra. Means and intended effects remain proposals; only an admitted mutation batch can change canonical components. There is no model-authored JSON Patch path.
  • Vault evidence constrains world compilation without pretending every playable route, procedure, or local institution is already written down. The compiler synthesizes the smallest compatible branch elaboration, exposes it for approval, and keeps it distinct from canon. Details that must not vary belong in the Vault.
  • Hosted lore Vaults are planned as Git-synchronized, Obsidian-compatible Markdown hierarchies. The Vault service owns their indexes; campaigns retain only manifest bindings and exact evidence receipts.
  • Projector → Persona → Interpreter turns produce proposals. Models never commit world state.
  • Knowledge, perception, capability, location, custody, and authority are validated against the exact actor proposing an action.
  • Fiction-first d20 resolution treats player text as an attempt rather than an accomplished fact.
  • Multiresolution Gestalts keep people, institutions, and factions active under a bounded Persona-cell budget without merging rivals into one mind or erasing named individuals.
  • Away-time simulation advances clocks and remote agency without puppeting or directly harming an absent player character.
  • CultMesh publishes typed service and Eve/CultUI state; the browser lowers that surface and does not become a second state authority.
  • Odin receives Ghostlight's advertised boundary schemas and typed projections over ACK-bounded RUDP publication. Internal runtime schemas are not treated as discovery contracts merely because Ghostlight owns them.

Eve-native interface

Ghostlight publishes one stable logical surface, ghostlight.play, for anonymous entry, Session Zero, Contract Review, and campaign play. The browser contains Eve's canonical provider host and lowering package plus Heimdall's access-plugin adapter. It does not contain Ghostlight-specific screen renderers or domain API routing.

Editable Eve bindings are the input model. Text, number, and choice controls bind either provider-owned typed state or renderer-local draft state; an operation captures named bindings and submits one canonical Eve command. Rejected or stale commands preserve local drafts, while an accepted receipt may clear named bindings before the host refetches the authoritative surface. A browser may lower this interaction to an HTML form for accessibility, but forms are not part of Eve's state or command ontology.

Heimdall authentication is composed as the required gamecult.heimdall.access Eve plugin. Heimdall owns OAuth attempts, provider callbacks, claims, entitlements, and single-use completion redemption. Ghostlight owns only its hashed HttpOnly app session and derives campaign authority from canonical membership. The browser sees an opaque attempt handle, never a claim, refresh credential, account hash, member ID, or actor authority. See docs/architecture/ghostlight-eve-native-interface.md.

Current Status

Ghostlight Dungeon is implemented and deployed as a native Yggdrasil, Heimdall-gated playtest harness. Idunn owns daemon continuity, Odin owns Verse discovery, and the application remains the sole owner of campaign truth. Authentication commands resolve Heimdall's redacted private boundary through Odin; no direct route is browser- or unit-owned, and valid local sessions do not phone home on routine commands. The current acceptance surface covers:

  • persistent DM-led Session Zero with shared/private channels, typed contracts, private boundaries, character bargains, digest-bound unanimous approval, and atomic publication;
  • source-constrained world compilation from an approved brief: canon evidence pins what must remain true, compatible game-scale connective tissue becomes disclosed branch-local state, and genuine premise conflicts return to negotiation instead of borrowing a nearby story;
  • selectable Aetheria and Kalsa Vaults, with Kalsa's player-safe Public and GM-only Spoilers evidence lanes preserved through exact receipts;
  • persistent campaigns, forks, resets, exports, and Heimdall-account-isolated sessions;
  • parallel affected-character Projector/Persona/Interpreter waves;
  • impossible-action refusal, assessed stakes, server-side rolls, and receipted commits;
  • strategic clocks, away-time catch-up, institution activity, migration, and information-channel-aware news;
  • bounded shared-scene co-op for up to eight Heimdall members, with exact member→actor authority, actor-filtered surfaces, unanimous time/budget governance, and no player puppeting or PvP mutation;
  • connected cohesive and arena simulation covers at budgets from 1 to 128;
  • Gestalt materialisation, folding, member deltas, migration, and later rematerialisation of the same person;
  • atomic rejection of malformed, stale, or semantically invalid model waves;
  • one kernel-owned mutation reducer for foreground, reaction, strategic, time, travel, population-fission, and bounded region-expansion consequences, with exact component versions and mutation proof receipts;
  • provider, token, cache, latency, validation, state-version, and build receipts;
  • provider-neutral inference through either direct DeepSeek/OpenRouter boundaries or the independent CodexConnector daemon's encrypted loopback CultNet boundary, while every prompt, schema, retry, interpretation, and world commit remains Ghostlight's;
  • exact-build deployment, state migration, public cutover, and restart verification on Yggdrasil.

Initial compiler seed publication is a bounded empty-store creation transaction. Named-person materialisation and folding are resolution transactions that preserve individual deltas without rewriting their Gestalt. The remaining forge gates are expansion and review of the agency corpus beyond its current candidate seed, removal of legacy model effect schemas, multi-account human pressure testing of Session Zero privacy/publication and bounded co-op, and continued multiresolution Gestalt agency pressure. The public site is provisional; checkout is not live.

Bounded Co-op

Campaign creation now supports one to eight authenticated players. One SessionZeroKernel owns negotiation; after unanimous approval, one WorldKernel owns the shared campaign. Membership binds each account to one exact actor, and every player receives an actor-filtered Eve projection.

This milestone is intentionally one shared scene with sequential public actions. PvP, split parties, private in-play actions, delegation, late joining, and simultaneous declarations remain closed until their consent and governance contracts exist. See docs/architecture/ghostlight-dungeon-session-zero.md and the longer-term multiplayer intention.

Lore Vault Product Intention

The hosted product will accept ordinary Obsidian-compatible lore Vaults synced through Git. Contributor and Private plans provision one active custom Vault; their Plus variants provision three, subject to combined indexed-source and import allowances. The entitlement, accounting rules, authority boundary, and security gates are recorded in docs/product/lore-vault-entitlements.md. Custom tenant import is not yet part of the deployed tester harness.

Architecture

The shortest reliable re-entry path is:

Repository Shape

  • crates/ghostlight/: the library crate — world kernel, ontology and reducer, journal, mailbox, controllers, elaboration, cover, clock, consumer admission, inference ports, and evidence sources;
  • crates/ghostlight-dungeon/: Rust daemon consuming that library — HTTP routes, Eve projection/command ingress, Heimdall and app sessions, CultMesh publication, Idunn health, and acceptance harnesses;
  • crates/ghostlight-persona-projection/: generalized projection membrane owned by Ghostlight and consumed by Epiphany;
  • docs/architecture/: durable contracts and authority maps;
  • docs/articles/: accessible public explanations;
  • notes/: implementation planning, handoff, and current-system maps;
  • schemas/: published JSON Schemas for typed boundary documents;
  • examples/: earlier fixtures and regression material;
  • state/: human-readable project memory plus older research-pipeline state;
  • tools/: state, validation, and fixture helpers.
  • web/: thin Eve browser host, Ghostlight transport, and Heimdall plugin adapter; product state and product-specific rendering remain server-owned.

Runtime documents and campaign exports use MessagePack-backed CultCache .cc. JSON exists at schema publication, browser, MCP, model-provider, and diagnostic boundaries; it is not the canonical hosted state store.

Useful Commands

cargo test --workspace
npm run state:status
npm run state:prepare-compaction
npm run schema:validate

For Codex-driven work, read AGENTS.md before changing the repository. It owns the persistence, grounding, verification, and handoff discipline.