Skip to content

Chronicle — Vision (v2.2)

Status: Revision incorporating the post-constitution research batch (Skyrim social-reactivity and economy mod prior art, Skyrim quest-injection/Radiant Story machinery, and cross-game AI-director/drama-management literature — docs/research/15 through 21 and comparative-systems/ai-directors-and-drama-management + its three independent follow-up passes). Supersedes vision-v2.1.md. This is a surgical revision, not a rewrite: §5 cites ui-doctrines.md and scenario-ladder.md, both already committed, and the dashboard's own contract (ui-spec.md v1.2.1) is untouched — the post-constitution research is entirely sim-side and GM-side, and nothing in it bears on frame schema, storage, or views. Changed from v2.1: the demand case in §3 is now sourced rather than asserted (decade of wishlist perennials, a quantified recirculation thread, Kingdom Come: Deliverance as the community's own named aspiration, and the "talk but nothing changes" reception pattern across Mantella/CHIM/SkyrimNet); a one-sentence positioning statement — the state layer beneath the LLM-dialogue mods, not their competitor — added to Bet 1; the competitive-frontier framing sharpened from "nobody has shipped anything adjacent" to "the adjacent systems are textual-only, and the distance from generated text to mechanical consequence is the moat," since IntelEngine and CHIM have since shipped textual gossip propagation and scoped rumor generation; the GM/director layer named explicitly in §6's road as the natural capstone consumer of everything else Chronicle builds, with its own now-filed research base; and §3's report count updated to reflect the larger corpus.

1. The dream

Skyrim's world is a stage set. Every NPC is a schedule and a barks table; nothing anyone does — the player included — changes what anyone else believes, wants, or remembers. Kill the Jarl and the world does not notice, because the world has no apparatus for noticing.

Chronicle is that apparatus: a social simulation that runs alongside Skyrim and gives its people an inner life with consequences. NPCs witness events and form beliefs with provenance — they know things because they saw them, or because someone told them, and the sim never forgets which. Beliefs travel as rumors that mutate in transit, warped by the teller's loyalties and the hearer's biases, every distortion recorded in a lineage. Beliefs and events accumulate into grudges, obligations, and reputations that are observer-local — you are the guild's hero and the widow's monster simultaneously, because those are different people who know different things. And accumulated state writes back into behavior: grief reroutes a mourner's days, a grudge empties the shared tavern table, a vacancy pulls a successor out of the web of relationships, and — eventually — an NPC crosses a threshold and does something about it.

The shorthand that emerged during design is honest about the ambition: the Sims in Skyrim. The Sims is autonomous characters, relationship state accumulated from interaction, autonomy that acts on that state, and — the part that makes it The Sims rather than an ant farm — a god-view where watching is the pleasure because everything is legible. Chronicle builds all four, with one upgrade The Sims never had: Sims have relationship scores; Chronicle's people have epistemologies. The Sims is a physics of feelings. Chronicle is a simulation of who knows what, how they came to know it, and how wrong they are.

2. The north-star test

One scenario is the acceptance test for the whole architecture. The player assassinates Jarl Balgruuf.

  • Succession: the vacancy resolves through the court's actual relationship and faction state — not a scripted replacement. Different prior relationships produce a different Jarl.
  • Grief and grudge: his household mourns on their calendars, not in a bark; his children hold grudges with the killing as their evidence; the mourners' rerouted days change who they meet and therefore what they hear.
  • The rumor: news travels at the speed people move, along kin and trade and tavern edges — carried beyond the hold by the caravaneers and couriers whose routes stitch Skyrim together — and it mutates: a Stormcloak blacksmith retells it as an Imperial plot; three weeks later a Markarth merchant greets you with a thirdhand version that is confidently wrong, and the sim can show you every hop that made it so.
  • The ripple: guard cohesion, market confidence (a belief aggregate over individual merchants — not a price model), and faction posture shift as aggregates over what individuals actually believe — never as a global flag.

When that scenario runs headless and every assertion passes with an intact evidence chain behind it, the architecture works. Everything in the build order exists to make that test passable one mechanism at a time.

3. The two bets

The research program — an intensive multi-agent effort now producing 38 cross-validated reports across shipped-game forensics, academic social simulation, hybrid LLM architectures, engine substrate, save-state synchronization, UI prior art, Skyrim reactive-NPC and economy mod archaeology, and quest-generation/GM-agent design literature (filed under docs/research/, including the comparative-systems and dashboard-ui-prior-art collections) — established what exists and what doesn't. Chronicle makes exactly two novel bets, and it is honest that they are bets.

Bet 1 — subjective belief with provenance can drive NPC behavior in a walk-around world. Every precedent surveyed gives up one half. Crusader Kings has consequence-rich social state but no subjectivity — opinion is summed attitude with perfect information, no provenance, no mutation. Shadows of Doubt has per-observer knowledge with decay, but its citizens don't act on it beyond testimony. Kenshi collapses the witness to the faction. The Nemesis system does true per-NPC memory for a bounded roster — and routes it into a patented rank loop Chronicle deliberately avoids. None of the surveyed systems ships believes-because-she-was-told, wrong-because-it-mutated, acts-because-she-believes in a spatial world. The demand for exactly this is not asserted, it's documented: a decade of stably-phrased r/skyrimmods wishlist threads (witness-only crime knowledge, NPC memory of deeds, gossip that spreads, nemesis-style recognition), a 1,485-upvote thread asking for the world to visibly register the player's own actions, and the community's own named aspiration — Kingdom Come: Deliverance's word-of-mouth reputation system, repeatedly cited as the mechanic players wish an Elder Scrolls game had. The mitigation for the bet: the epistemology is built on the most-validated data model in the academic literature (Talk of the Town's belief facets, evidence chains, predecessor lineage), and every tier of it is regression-tested headless before any richer layer sits on it.

Chronicle's product positioning follows directly from this bet, and it is worth stating in one sentence: Chronicle is the state layer beneath the LLM-dialogue mods, not their competitor. The reception record for Mantella, CHIM, and SkyrimNet converges, independently and repeatedly, on the same complaint — NPCs talk, but nothing changes and nobody remembers. Mantella's own issue tracker records NPCs that "forget everything which was exchanged before"; its competing fork markets directly against Mantella's "lossy summaries that forget details"; a PC Gamer review of the genre calls it "wide as the ocean, deep as a puddle." Chronicle's belief/rumor/grudge graph is the missing memory those mods are reaching for — designed to be read as context and written to as evidence, not to compete with them on conversation. The competitive frontier has moved since v2.1, and the honest framing has moved with it. SkyrimNet's community plugin IntelEngine now ships "gossip chains that propagate between NPCs," and CHIM's Background Life system generates location-scoped rumors NPCs are aware of for a limited time. "Nobody has shipped anything adjacent" is no longer accurate. What remains true, and is the sharper and more credible version of the claim: the adjacent systems are textual-only — generated prose that colors dialogue, with no mechanical effect on schedules, disposition, or AI packages, and both systems' own documentation concedes the gap (SkyrimNet: "vanilla quest dialogue trees still go through Skyrim's normal system"). The distance from generated text to mechanical consequence — provenance that survives into behavior, not just into a sentence — is the moat, and it is Bet 1 restated as a race Chronicle is already positioned to win rather than a field with no other runners.

Bet 2 — showing the player how a story changed as it traveled. The comparative research's flattest finding: this has no shipped game precedent in any system surveyed. CK3 has secrets (binary known/unknown); nothing in the games literature renders a belief's mutation history. The nearest analogues are cross-domain: phylogenetics tooling (Nextstrain/Auspice, which annotates mutations directly on lineage branches) and one academic prototype (the "bargaining chips" study, where knowledge-as-inspectable-objects playtested well precisely after hidden social knowledge had failed). This is simultaneously Chronicle's signature mechanic and its least-derisked feature — a scoped claim from a specific research pass, not an independently verified absolute. The mitigation: the variant tree is built first as a debugging instrument — it must exist for the developers regardless — so the player-facing bet rides on infrastructure that pays for itself even if the presentation bet fails.

Everything else in Chronicle is deliberately unoriginal: adopted from shipped systems with the failure history read first. That's the doctrine corpus (§5).

4. The observation thesis

The dashboard is not tooling for the mod. It is the other half of the product.

Three facts, established independently, converge here. First, the Sims' 25-year lesson: the core pleasure of a social simulation is legible observation — the plumbob, the moodlet, the relationship panel; watching is playing. Second, the market's one-sentence complaint about every social system in every game, quoted from the mod that exists to fix RimWorld's: it "gives you a list of names and a number beside each one. It never tells you why." Chronicle's provenance layer is the first architecture where why is always answerable, all the way down. Third, the UI research confirmed a genuine four-way gap: ABM platforms have inspection without time travel; the Smallville lineage has persistence without interaction; games have legibility without debugging depth; replay systems have the timeline grammar without agent semantics. No surveyed tool combines them. Chronicle's dashboard — god-view map, global tick scrubber where every view renders as-of-T, provenance drill-down, variant lineage tree, run comparison — is that unbuilt instrument.

The consequence for priorities: observability is first-class from the first commit — the event-sourced store, deep-linkable ticks, and the derivation trace (specified in the ladder as tier-1 infrastructure: an append-only record of every roll with its value, every rule that fired, and every rule that declined with its reason) — because the same artifact serves three audiences on one timeline. Now: the developer debugging tier assertions. Next: the player who alt-tabs to watch the news of the Jarl's death crawl across the map toward Riften. Eventually: the second-screen mode — Skyrim on the TV, the living town on the monitor — which costs nothing extra because it was the debugger all along. And when the LLM conversation tier arrives, the dashboard inherits the best debugging affordance no debugger has: pause the world and interview an NPC against their actual memory.

5. The constitution

Design authority lives in three documents committed alongside this vision: design-doctrines.md (doctrines distilled from shipped-game failure history), ui-doctrines.md (the convergent interaction patterns, pattern assignments for the four hard views, and a prohibition list), and the ADRs. Three doctrines are load-bearing enough to inline:

  • Expected randomness. Every NPC behavior is probabilistic in firing, deterministic in explanation — surprising in outcome, retroactively explainable in cause, with the reason attached at the moment of action. (Fåhraeus's principle; enforced mechanically by the derivation trace rather than aspirationally by design intent.)
  • Every derived state answers "why." Who believes this, from what evidence, through whom, since when — the inspectability requirement shapes the schema, not the UI. If the simulator cannot answer why, it cannot be debugged, authored, or enjoyed.
  • One honest mechanic, one named fake — scoped to when the game isn't actually connected. Every shipped spatial social sim pairs a load-bearing simplification with an honestly-simulated felt mechanic. Chronicle's pair, stated so nobody discovers it as a scandal: the headless math tier (running without a live game, or reasoning about NPCs outside the game's currently-loaded area) fakes continuous NPC movement (discrete schedule blocks, sampled encounters — the same abstraction Skyrim itself uses offscreen, and the only tractable option across up to ~1,000 NPCs with no positional ground truth to sample from) and honestly simulates belief provenance and mutation (the thing nobody in the surveyed field has shipped with mechanical teeth — see §3's sharpened framing). The fake carries one obligation the honest mechanic must meet: information can only travel where bodies go, so the world's mobile carriers — caravaneers, couriers, traveling merchants, NPCs whose schedule blocks span holds — are first-class citizens of the fixture data, because they are the bridges every cross-hold story crosses. Correction (2026-08-24, owner): an earlier revision stated flatly that Chronicle fakes continuous movement everywhere, full stop — that overreached past what the owner actually asked for and was never a signed-off decision; it got written in without the owner's real intent being checked. When Chronicle is actually connected to a running game, live NPCs are not faked. The v0.2 seam streams real position/activity telemetry (starting scope: every NPC in Whiterun, ~1 Hz cadence — a deliberate, owner-approved cost/fidelity tradeoff, not full continuous animation-frame tracking) and the dashboard renders that directly. The schedule-block abstraction remains legitimate for the headless math tier's own encounter-sampling math (that part was never in question), and for any NPC currently outside the game's loaded/connected area — but it is not, and was never meant to be, a statement that the live dashboard shows fake positions for NPCs the game is actually telling us about in real time.

6. The shape of the road

Build order is the scenario ladder (scenario-ladder.md, finalized from the reviewed v0.2 draft): each tier adds exactly one mechanism, forces exactly the tooling its assertions need, and stays in the regression suite forever. In outline: beliefs and their claims-layer mechanics; one-hop transmission plus the derivation trace; multi-hop propagation with mutation and variant conflict; social accumulation, decay, and the tell-decision gate; state writing back into schedules — the first visible reactivity; roles and vacancy; and the Jarl as a composition test with no new machinery. One amendment carried from vision review into the ladder: mobile carriers (inter-hold schedule blocks and the bridge-node fixtures they imply) are a named prerequisite exercised before the composition test, because the north star's Markarth and Riften beats structurally depend on them.

Version road: v0.1 is the headless ladder through its early tiers with the dashboard's core views. v0.2 is the Skyrim seam — event extraction in, hydration overrides out, save-timeline sync — begun only after the headless suite is green. v0.3 is NPC-initiated social actions with CK-style thresholds, hysteresis, and crystallized named relationships. v0.4 is the economy tier. Beyond the ladder proper, the research base now supports a GM/director layer as the natural capstone consumer of everything below it — a component that sifts the belief/rumor/grudge/faction graph for dramatically-charged, already-provenanced situations and expresses them as Skyrim-native content (quest instances, faction moves, dialogue framing) rather than inventing anything ungrounded. It is deliberately not on the version road above: it has a researched seed (docs/research/19–21 on Skyrim's Radiant Story/quest-injection machinery, and comparative-systems/ai-directors-and-drama-management plus three independent follow-up passes on the cross-game drama-management literature), a stated design law (provenance-anchored intervention — a generated quest must cite real tracked belief state, never decorate an independently-rolled event), and an explicit positioning claim (no surveyed system combines deep state grounding with real dramatic control; that combination is the gap this layer would occupy) — but no scheduled tier, because it is a consumer of the belief/rumor/grudge/faction state the ladder above has not yet finished producing. The LLM layers come strictly last and strictly as renderers — a small local model as semantic mutation engine for ~30 gossip-hub NPCs, a conversation model performing sim state as dialogue with structured output writing evidence back, procedural voice (design-once-then-clone) giving every NPC a permanent unique voice. The LLM is the actor, never the author: facts come from the sim, always.

The substrate strategy: pure-Python engine-agnostic core; the Skyrim seam isolated behind a provider abstraction (open-source reference path first, SkyrimNet as a pinned optional adapter); save/reload handled by fork-never-delete timeline branching anchored in the co-save. Skyrim is the first renderer, not the identity — the sim would work over RimWorld or a 2D world, and proving it headless first is what keeps that true.

Non-goals, stated to stay honest: - No economy simulation before v0.4; no LLM anywhere before the symbolic tiers are green; no voice before dialogue exists. - No in-engine code before the headless scenario suite passes (the seam is the grungiest work and the sim must not wait on it). - No nemesis-style chains where a player↔NPC-A interaction automatically rewrites NPC-B's parameters+rank+dialogue (patent doctrine; observer-local propagation and vacancy-triggered succession are the compliant — and better — design anyway). - No global reputation, ever. No belief without an evidence chain, ever. No behavior threshold without hysteresis and an attached reason, ever. - Not a chatbot mod. The existing AI-NPC mods put a mouth on a static world — "wide as the ocean, deep as a puddle." Chronicle is the missing world; mouths come last. - No GM/director layer before it has something true to sift — it consumes belief/rumor/grudge/faction state the ladder has not yet produced, and its research base (§6 above) is filed against that future need, not against current work.

7. What success looks like

Near: the composition-test scenario passes headless, and a stranger can open the dashboard, scrub to the assassination, watch the stain of the news spread, click a wrong belief in Markarth, and walk the chain back to the dagger — without anyone explaining the tool to them.

Far: a player three weeks into a modded playthrough hears an innkeeper repeat a mangled version of something they actually did, realizes the mangling has a history, alt-tabs to the map, and finds the exact blacksmith who bent the story. The world remembered, imperfectly, the way worlds do. That moment — the lie has a biography, and you can read it — is the product.