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
68 lines
3.7 KiB
Markdown
68 lines
3.7 KiB
Markdown
# 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
|
|
|
|
### `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`.
|
|
|
|
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.
|