written 2026-09-26 12:45:34 · claude-fable-5-1
Your directive: You are a fork with the whole design conversation in context. Write the ISSUE FILES for PHASE 2 of Double Diaper Dungeon (201 through 214), plus issues/phase-2-progress.md. Project root: /mnt/cmdo/ritz/games/tq/ai-stuff/double-diaper-dungeon. Read docs/019-roadmap.md for the exact issue list and titles, docs/001 for vocabulary, docs/005, 006, 007 for the mechanisms (and 008 and 015 where they touch), docs/018 for house style, docs/020 for open question ids, and assets/023-balance-table.lua for entry names. Do not touch any file outside issues/. Do not run git. Do not run new-source-file.
File naming: issues/{PHASE}{ID}-{dashed-lowercase-title}.md, e.g. issues/201-a-hero-is-one-record.md. One file per roadmap row, exact titles.
Format of every issue (the hero-less-moba shape you read):
| Phase | 2 — A Hero Is One Record |
| Blocked by | issue numbers, or — |
| Blocks | issue numbers |
| Reads | links to the documents it builds from, ../docs/NNN-name.md |
| Open questions | ids from docs/020-open-questions.md (e.g. A1, A7, B2), or none |
What exists now: nothing runs; the documents, the balance table, the file tools exist; phase 1's clock, world record, runner and scenarios are assumed built (say so, and name what this issue needs from them).
The blueprint: what it is, how it works mechanically, the data it owns with datatypes, every branch and where it leads, what it refuses (errors, never fallbacks, nothing nil), the log lines it emits in the emoji-first style with English connective tissue (write the actual lines), and how it is tested with a scenario. Enough to rebuild the piece from this file plus the documents. Plain English and fixed vocabulary; list files, functions and structures by descriptive name rather than code. Numbers by balance-table entry name, never values.
Numbered. Files to create (dashed names for ./new-source-file, no indices claimed), what each holds, the scenario in tests/ that validates it, the order.
Facts that must be right (late corrections): maturity is the ceiling over regression; pride is the ceiling over confidence; regression drifts toward zero, confidence toward pride, pride has no home drift; the knife-edge bump on pride; the dangerous and routine states; imagination from regression; support boosts; defeat is regression exceeding maturity OR health below zero; ally death and sobering; whether a regression hit erodes maturity is open question A1 (build it as the working ruling behind the table entry); accidents cost confidence scaled by volume, leaks and smells cost pride (A7 open on whether accidents also add regression); two rolls in the hold check; overflow incontinence; the set-point; penalties multiply (A4 ruled); monsters are the same record pinned at the monster maturity entry with their own stat block, confidence and pride. Issue 214 is the phase capstone and creates issues/completed/demos/phase-2-demo, a bash script in the house convention, that runs one hero alone in one room for a thousand ticks three times (baseline; confidence starting below the knife edge; a regression hit landing at it) and prints every mind and body number tick by tick as a table. Also write issues/phase-2-progress.md in the hero-less-moba shape: goal, ends with, a table of issues with status "not started", Blocking, "Demo: not yet built".
Length: 500 to 1200 words per issue. When done, reply with the list of files written and their word counts, and any NEW open questions you noticed (topic plus one sentence). Nothing else.
Wrote phase 2 issue files 201–214 and issues/phase-2-progress.md; no files outside issues/ touched, no git, no counter use.
Files and word counts:
New open questions noticed while writing: