JesseMarkowitzandClaude Opus 5
144406cd48
The release-validation milestone, and the thing it had to settle first was whether any of the earlier evidence meant what it said. M8 measured a deployment enforcing a 4,096-token input window while the application budgeted 16,384. Every request returned 200. What Ollama does with the excess is drop the oldest tokens, and the oldest tokens here are the system block — the narrator's rules and the campaign canon. A hundred-turn certification against that server would have looked perfect and proved nothing, which is why this milestone could not begin with a hundred turns. So the application asks now. Ollama's window is a property of how a model was loaded rather than of the request — sending num_ctx is accepted, ignored, and worse, reloads the model at the server's own default — so the only honest move is to find out and then tell the truth about it. /api/ps reports what a resident model is being served with, /api/show what an unloaded one will load with, both on the same host inference already uses, through the same endpoint policy and the same TLS trust store. A verified window is a ceiling on the budget; an unverified one leaves the budget alone and is recorded as unverified in the turn's own provenance, so an old turn can be asked afterwards whether it was built against a checked window. There is no third behaviour, and in particular no hard-coded 4,096: a number the server did not say would be right on one machine and wrong on the next. The proof that this is doing something is a campaign whose canon sits at the front of the prompt, 120 turns of history, and a 4,096-token window. The canon is still there afterwards and the oldest history is gone. The same campaign built the old way produces a prompt more than twice the window — the defect, reproduced, so the fix is measured against it rather than asserted. Two defects the validation found on its own, and they are the same defect twice: something was true and nobody was told. A manual state correction of four changes with one bad reference applied three, returned 201, and said nothing — while recording the refusal on the audit row nobody reads. It came to light because the identity diagnostic's own fixture was refused that way and the whole run proceeded on a campaign with no scene, which would have read as a model failure. And the narration-length setting moved no number: brief, medium and long each became one English sentence, while the numeric hint the model actually reads was derived from the global reply cap and said the same thing for all three. Both now say what they did. The other two post-M8 findings are closed as well. The tab said AI D&D, which no document had ever claimed it did not; it says Interactive Story now, with the open campaign first, and the name is the owner's decision rather than a find-and-replace to something narrower than the engine. After an Undo the reader could not tell where they had landed; the control row now ends with "Moment 11 · later story ahead", from the server's own answer, in the word the transcript already uses, with none of head, branch or depth anywhere near it. The identity diagnostic exists and the root cause does not. That campaign was destroyed, so no cause can be established — what M11 owes the finding is something that can classify the next occurrence, and a diagnostic that makes only the judgements a program can honestly make: duplicate keys, shared names, protagonist drift, state and context disagreeing. Whether prose misattributed a line is left to a person reading it beside its prompt, because a regex cannot read dialogue and one that pretended to would produce exactly the confident wrong answer this finding is about. Its detectors are proved to fire against a planted second Alice. Two entities may still share a display name. That was checked first, as the finding asked, and left permitted: a mother and a daughter, or a stranger giving a false name, are ordinary fiction, and refusing them to guard against a model mistake would refuse the wrong thing. What was missing was that it happened silently. It is reported now. Evidence, not inference: a hundred accepted turns against a real narrator with genuine process restarts; a real browser against the built SPA; a container with no network at all; a campaign moved into a data directory that never existed. Each was discarded and re-run whenever the product changed under it, and the runs that were thrown away are listed in the report with the reason, along with ten defects in the harnesses themselves — because a harness that has only ever agreed with itself is not evidence, and two of M8's five harness defects were masking real ones. No dependency was added, removed or upgraded. No acceptance test was retired, relaxed or reclassified. M11 is implemented and verified; it is not accepted, and there is no release tag. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qyn3oRd4D6pi72nKBG725B
Archive — historical material, not authoritative
Everything under planning/archive/ is evidence and history. None of it
governs current implementation. If an archived document and an active planning
document disagree, the active document is right and the archived one records
what was believed or measured at the time.
Do not consult this directory during ordinary milestone work unless an active document sends you here for a specific piece of historical evidence.
What is here
milestone-reports/ — the completed milestones
One report per milestone that has been accepted, unedited. M7's joined them when M8's report was written, following the convention that a milestone report is useful during the immediately following milestone and historical afterwards.
phase0/ — why AI-DnD was selected
Phase 0A static research and Phase 0B local validation, closed 2026-09-01.
| File | What it is |
|---|---|
RESEARCH-PLAN.md |
The question Phase 0 existed to answer, and its final dispositions. |
PRELIMINARY-RECOMMENDATION.md |
The Phase 0A conclusion, from static review alone. |
REUSE-MATRIX.md |
What each candidate offered against the required subsystems. |
AI-DND-ANALYSIS.md |
The selected base, analysed before the fork. |
AI-ADVENTURE-ANALYSIS.md |
The rejected finalist still cited as the implementation reference for typed state events. |
OPEN-DUNGEON-ANALYSIS.md |
The rejected finalist still cited as the UX/future-media reference. |
PHASE-0B-RECOMMENDATION.md |
The strongest single document. The measured Phase 0B findings and the fork decision. |
PHASE-0B-BASELINE.md |
Clean clones, builds and test runs for the three finalists. |
PHASE-0B-AI-DND-EXPERIMENT.md |
AI-DnD driven against a real local Ollama. |
PHASE-0B-AI-ADVENTURE-OLLAMA.md |
ai-adventure's Ollama and service-boundary behaviour. |
PHASE-0B-OPEN-DUNGEON-HISTORY.md |
Whether Open Dungeon could be retrofitted with history. |
PHASE-0B-OFFLINE-NETWORK.md |
What each candidate reached for with no route to the Internet. |
PHASE-0B-UNDO-SPIKE.md |
The disposable spike that proved non-destructive undo/redo, and became ADR 012's architecture. |
PHASE-0B-FOLLOWUP-CHECKS.md |
The world-state protocol, export/head, story-card lineage and Postgres checks. |
Phase 0A discovery and triage material (the candidate inventory, source index, reference-project list, licensing and static-privacy reviews, the Phase 0A status page) and the Phase 0B execution prompts were deleted in the 2026-09-03 documentation cleanup. They are intermediate working documents whose conclusions all reached the two recommendation reports above, and they remain in Git history.
milestone-reports/ — completed milestone evidence
M1-BASELINE-REPORT.md, M1-IMPLEMENTATION-REPORT.md,
M2-BASELINE-REPORT.md, M2-IMPLEMENTATION-REPORT.md,
M3-IMPLEMENTATION-REPORT.md, M4-IMPLEMENTATION-REPORT.md,
M5-IMPLEMENTATION-REPORT.md, M6-IMPLEMENTATION-REPORT.md,
M7-IMPLEMENTATION-REPORT.md.
M3's report is both its review and its primary evidence record; no separate M3 baseline report was produced. It arrived here when M4's report landed.
Every architectural conclusion these reports reached has already been applied to
the active planning documents and the ADRs — see planning/VERSION.md, which
lists the corrections each milestone produced. The reports are kept for their
measurements and their reasoning, not as instructions.
The current milestone's report stays in planning/reports/ while it is
still useful for reviewing the next milestone, and moves here when it is not.
decisions/ — superseded or completed ADRs
008-phase0-before-build-plan.md — a process gate ("do not start production
work before Phase 0 closes") that Phase 0 satisfied on 2026-09-01. It
constrains nothing now. ADR numbering continues from 012 in
planning/DECISIONS/; 008 is not reused.
A note on paths inside these files
Archived documents are kept verbatim. File paths written inside them refer to where those files lived when the document was written — before this archive existed, and in some cases before files were deleted. That is deliberate: an evidence record that has been quietly edited is no longer evidence. Resolve any such path against Git history, not against the current tree.