JesseMarkowitzandClaude Opus 5
d27ee34901
The planning package had grown to where a new agent could not tell what was authoritative. Phase 0 execution prompts sat beside the specification; four completed milestone reports sat beside the current one; and upstream AI-DnD's own `plan/` build log and `docs/` project site still described a hosted, scripted, multi-user product with accounts — every screenshot in it showed a Scripts tab and a Sign up button, none of which has existed since M2. `planning/archive/` now holds the history and says so in its own README: `phase0/` for the research that chose AI-DnD, `milestone-reports/` for M1 and M2, `decisions/` for ADR 008, the Phase-0-before-build gate Phase 0 satisfied. `planning/reports/` holds only the current milestone's report, because that is the one M4 planning has to read; it moves to the archive when M4's replaces it. Deleted rather than archived: the Phase 0B execution prompts and the handoff/status/summary documents, the Phase 0A discovery and triage reports, upstream's `plan/` and `docs/` trees, and `frontend/README.md`, which was Vite's template boilerplate. All of it is in Git history, and the two recommendation reports carry every conclusion the deleted research reached. Archived documents are kept verbatim. Paths written inside them point at where those files were when the document was written, which is the point: an evidence record that has been quietly edited is no longer evidence. Active documentation is corrected where it pointed at the removed trees or described removed capability as present. `DEVELOPMENT.md`'s "things M1 did not touch" list had gone stale at M2 and claimed QuickJS scripting was still tested; its test count was 604 against an actual 638. `README.md` loses the upstream CI badge, which reported upstream's pipeline rather than this fork's, and a reference to `backend/app/worldstate/engine.py`, a file that does not exist. `planning/README.md` is rewritten as the documentation index. New: `planning/PROJECT-SOURCES.md` and `planning/project-sources.txt`, the manifest of what belongs in the ChatGPT project's Sources. Source comments referring to the deleted trees are reworded; no behaviour changes. 638 backend tests pass, frontend lints and builds, and a reference scan over all 48 tracked Markdown files reports no unresolved path in active documentation. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NCbwH7yLGKsj1rhXXzKSCu
3.0 KiB
3.0 KiB
Reuse Matrix
Historical status: Phase 0A matrix. Some ratings were corrected by Phase 0B; use the v1 technical design and ADRs for current decisions.
Date: 2026-09-01
Legend:
- KEEP — candidate implementation is close to target.
- MODIFY — strong implementation but needs adaptation.
- REFERENCE — borrow pattern/idea; do not make it the ownership center.
- BUILD — target capability is substantially absent.
| Capability | AI-DnD | Open Dungeon | ai-adventure | Best current source |
|---|---|---|---|---|
| Browser storyteller UI | MODIFY/KEEP | KEEP | BUILD | Open Dungeon |
| Ollama text adapter | KEEP | KEEP | MODIFY | AI-DnD/Open Dungeon |
| SQLite local persistence | KEEP | MODIFY | KEEP | AI-DnD / ai-adventure |
| Immutable turn parentage | KEEP | BUILD | KEEP | AI-DnD |
| Alternate takes | KEEP | BUILD | MODIFY | AI-DnD |
| Named checkpoints | MODIFY | BUILD | KEEP | ai-adventure |
| Branch restore | KEEP | BUILD | KEEP | AI-DnD / ai-adventure |
| Complete tree export | KEEP | BUILD | MODIFY | AI-DnD |
| Exact prompt inspection | KEEP | BUILD/MODIFY | audit-oriented | AI-DnD |
| Recent-history budgeting | KEEP | KEEP | KEEP | AI-DnD |
| Rolling summaries | KEEP | KEEP | KEEP | all |
| Semantic old-story retrieval | KEEP/MODIFY | BUILD | BUILD/MODIFY | AI-DnD |
| Lexical local lore | MODIFY | BUILD | KEEP | ai-adventure |
| Lore/story cards | KEEP/MODIFY | BUILD | MODIFY | AI-DnD |
| Canon/Reference/Inspiration authority tiers | BUILD | BUILD | MODIFY | Chronicler/IFF concepts |
| Generic narrative state | MODIFY | BUILD | MODIFY | ai-adventure pattern |
| Model-proposes/app-validates | KEEP but RPG-shaped | BUILD | KEEP | ai-adventure |
| Atomic state + turn commit | VERIFY | VERIFY | KEEP | ai-adventure |
| Local-only privacy posture | MODIFY | MODIFY | KEEP | ai-adventure |
| Local image generation | BUILD | KEEP | BUILD | Open Dungeon |
| Provider-neutral media | BUILD | MODIFY | BUILD | Gamentic reference |
| Scene/visual continuity | BUILD | KEEP/MODIFY | BUILD | Open Dungeon |
| Large automated test base | KEEP | BUILD/VERIFY | KEEP/VERIFY | AI-DnD |
| Genre-neutral core | MODIFY | MODIFY/KEEP | MODIFY | IFF/story-state concepts |
Cross-project architecture we should aim for
Use one primary fork, not a stitched codebase.
Preferred composition of ideas:
AI-DnD production base
+ ai-adventure trust/commit/privacy rules
+ Open Dungeon scene/media UX
+ Chronicler memory-authority tiers
+ IFF Story Bible authority/validation
+ Gamentic media-provider abstraction
If AI-DnD strip-down proves too invasive, invert the first line:
Open Dungeon production base
+ new AI-DnD-style immutable story tree
+ ai-adventure event/commit discipline
+ local memory/document retrieval
That fallback is viable, but static analysis suggests it recreates more hard correctness work.