[SYS] SYS.00 · CANONLOCK™ · NARRATIVE PERSISTENCE ENGINE
GEN II · LIVECANONLOCK®
ONE WORLD ON RECORD AT
TURN 5,011
CANONLOCK keeps supported world and mechanical state outside the Narrator's prose. We published one world artifact sealed at turn 5,011 and audited its selected entity categories with zero rows lost. That result is inspectable below and scoped to that run.
ENGINE CØS-CL-01 · BUILD 12.2 · CLASS: NARRATIVE PERSISTENCE · STATUS: LIVE
// THE ENGINE
CANONLOCK®ARTIFACT 5,011 TURNSSERVER-SIDE STATECØS-CL-01 · GEN IIThe model proposes supported changes. The server validates and commits them.
// THE DIFFERENCE
Prose for the scene.
Records for the state.
Generative memory still matters for narrative detail. Supported inventory, currency, factions, quests, relationships, properties, and production can also use structured records, so mechanical truth does not depend on one paragraph of context.
The readout.
FIGURES ATTESTED FROM A LIVE CAMPAIGN · SERVER-AUTHORITATIVE TURN COUNTER · NO CLAIM OF PERFECT MODEL RECALL
One run. Indexed through turn 5,011.
Proof, not promise.
FIRST-PARTY ATTESTATION · ONE PUBLISHED ARTIFACT · SEALED AT TURN 5,011
VERIFIED2026 / 06 / 26We drove one world to turn 5,011 and re-read its selected entity records: characters, factions, quests, and locations were still on file. Zero rows were lost in those audited categories for this artifact.
Verified against the published server record, not the model's self-report. Reproducible from the same artifact. No independent third-party audit and no claim of perfect model recall.
// AND HERE IS WHAT THAT BUYS YOU IN PLAY
KURODA.T · HOSTILEFIXED VERIFIED REPLAY · TURN 1,047 · NOT A LIVE GENERATION
“You think your silence wipes the slate clean? You put me in the dirt and chose to let me liveT12. That mercy has festered in me like an open wound. And Yukikaze, my clan’s ancestral blade, still rides at your hipT27. I have counted every season since.”
This fixed reconstruction is drawn from the published turn-1,047 interaction. It illustrates one documented callback and does not promise the same result for every fact or every world.
Don’t take the stamp’s word for it.
This is the published event artifact from one automated run, indexed through turn 5,011 and frozen on the day it was checked. Pick a turn to inspect the player action and displayed mechanical receipts. It is not the full raw prompt, model response, or database dump for each turn.
READING THE RECORD…
Mechanical receipts only, capped at 12 per turn for display; the true write count is shown on each turn. The record ships with this page as sealed files and has not been edited since capture. Read a static excerpt and how to check it yourself.
The AI proposes. CANONLOCK commits.
PROPOSE
The model reads a curated slice of your world and proposes what changes. It never holds the truth. It only suggests.
COMMIT
The server validates supported mechanical intents and writes accepted changes to structured records.
RECALL
Layered retrieval can surface relevant past events while structured state remains available to supported systems.
CANONLOCK II · LIVE · ONE ARTIFACT SEALED AT 5,011 · SCOPE: STATED BELOW
The second generation is shipped.
The live engine is CANONLOCK II. The published 5,011-turn artifact above ran on it. Supported world changes are written to server-side records, while narrative history is compacted and retrieved in layers. The event timeline can be paged where recorded; this is not a claim that every narrative detail is stored verbatim or recalled perfectly.
Supported mechanical state is committed by server-side systems, not owned by generated prose.
Layered retrieval can return relevant older events. Results remain selective and testable.
Recorded events can be paged through in the timeline, subject to the data captured for that turn.
// CANONLOCK™
Inspect the record.
Then judge the engine.
CANONLOCK II · LIVE · ONE ARTIFACT SEALED AT 5,011 · SCOPE: STATED ABOVE