2 Commits

Include renames

Author	SHA1	Message	Date
JesseMarkowitzandClaude Opus 5	0c7316f951	Keep the state section and its proposal out of the story ... The first complete M01 run with the memory bank on (f8d4010, 101 turns on a GPU host) reported "complete". It still did not prove M04. The planted clue was found at turn 100 only because the narrator had pasted the narrative-state section into its own prose, and the paste was still in recent history. No memory and no summary carried the clue. The narrator is a small local model. It wrote protocol into its stored narration on 42 of 104 turns, starting at depth 2, in four shapes: - a copy of the state section: `Scene:`, `Who and what exists:`, `Held:`, `Established:`, `Still open:` - that copy above a correct ```state block, which was stripped while the copy stayed - the copy, then a bare `State` heading, then a `> {"events": ...}` proposal quoted like a player turn, sometimes with story after it - the same block cut off by the output-token limit, on 10 turns Stored text is replayed verbatim as history, so each leak also put a second, older account of the state into the next prompt. That is what M5 review Finding 4 removed from history replay, and every leak gave the model another example to copy. The extractor now removes: - a pasted state section, recognised by at least two of the renderer's own headings as whole lines. The headings are constants in `render.py`, so the renderer and the extractor cannot drift apart. One heading alone, or a `Scene:` line of prose, is left. - an unfenced proposal that starts a line, quoted or not, when it parses and is a proposal. With no fence it becomes the turn's proposal. A `State` heading directly above goes with it. Candidates are taken outermost first, so a finished event line inside an unfinished block is never taken as a proposal by itself. - an unfinished unfenced proposal at the end that reads as protocol. - whatever is left at the end: a `State` heading, a bare `>`, a parroted reminder or continue hint (closed or not), and a ```json fence cut off before it names its events. These are cut repeatedly until nothing more comes off. This also fixes an older bug. `_STATE_FENCE_RE` read "a ```state block" inside a parroted reminder as a fence opening and cut out the middle of the reminder. The label must now end its line or run straight into the payload. A reply whose only removal is a pasted state section records no raw block, so the turn is not marked unparseable for a block it never started. Every AI turn in four real runs was replayed through the new extractor: draco M01, the two 26-turn GPU trials, and this M01 run. 339 turns in all. No turn the old extractor had left clean changed. Every leak of our own protocol is gone: 42 of 42 in this M01 run, 5 in trial 2, 3 on draco. Trial 1 still has model-invented headings ("Identifiers established:", "Set of events made true:") on 10 turns. They paraphrase the instruction and are not our renderer's text, so they are left, not guessed at. The long-run harness now records an explicit M04 verdict, which is never a recovery while the clue is still in recent history. It also counts the AI turns in the export that still carry protocol. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136VBTMUKWYeU6G9HgbDbND	2026-09-13 21:18:18 -04:00
JesseMarkowitzandClaude Opus 5	b7005e6fdd	M5: genre-neutral authoritative narrative state, with review corrections ... Replaces AI-DnD's RPG relative-delta world state with the genre-neutral typed narrative state of ADR 010: explicit, absolute, allowlisted events proposed by the model, validated by the application, applied to one authoritative document, and snapshotted per position so restore stays a row read. This commit includes the corrective pass that followed the independent review in planning/reports/M5-IMPLEMENTATION-REPORT.md. The invariant it exists to hold is: visible active transcript position == stored head == authoritative state Narrator editing (D10, STORY-BRANCH-SEMANTICS §§14-15) A narrator edit no longer rewrites a row. It returns to the state before the turn, takes the reader's exact text as the accepted narration, re-derives the state that text implies, and becomes a new active continuation — while the original narration keeps its words, its live flag and its whole future as retained history. At the tip the correction is another take; with story below it, it forks. No new history machinery: this is the existing fork/take/head path with the reader's text in place of a generated reply. The §14A refusal is therefore gone for narrator turns, and remains only for player input. Pre-M5 positions Migration 88 backfills the empty narrative document onto every action written before M5, and a missing snapshot now restores the empty document instead of leaving the previous position's state standing. Restoring to an old Save Point no longer leaves a later position's entities and facts on screen. Narrator context Replayed history carries prose only; the machine-readable block is no longer reconstructed into past turns, where it contradicted the authoritative state in the same prompt. A fact withdrawn by a manual correction is now named as no longer true, with the reader's reason, rather than silently dropped. Also - state_changes joins the action-list bulk read, removing one query per row. - Extraction takes only the application's own protocol payload: an ordinary ```json or ```python block in a story survives, and a mangled proposal still does not reach the reader. Planning: ADR 013 records the authoritative document shape; §§14-15/14A, D10, C04 and BUILD-MILESTONES are updated to describe what exists. Debt is recorded against M8 (scenario editor UX) and M9 (export of the audit trail). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PWU4gTfLYY6Qq9U7aa9Qw2	2026-09-05 07:01:50 -04:00