Update planning package after Phase 0B
This commit is contained in:
@@ -1,9 +1,11 @@
|
||||
# Adventure Storyteller — Phase 0 Research Plan
|
||||
|
||||
**Status:** Ready for execution
|
||||
**Status:** Complete — Phase 0 closed 2026-09-01
|
||||
**Phase:** 0 — Research, Validation & Architecture
|
||||
**Goal:** Determine what to build, what to fork/reuse, and finalize the technical design before production implementation begins.
|
||||
|
||||
**Outcome:** AI-DnD selected as the production base; non-destructive head-cursor history and explicit typed narrative-state events selected; production milestones now defined in `BUILD-MILESTONES.md`.
|
||||
|
||||
## 1. Why Phase 0 Exists
|
||||
|
||||
The project has several promising open-source starting points. They differ substantially in:
|
||||
@@ -28,6 +30,26 @@ Phase 0 therefore ends when we can answer:
|
||||
|
||||
No production feature work should begin before that decision unless explicitly authorized.
|
||||
|
||||
## 1A. Phase 0 Completion Summary
|
||||
|
||||
Phase 0A static research and Phase 0B local validation are complete.
|
||||
|
||||
Final dispositions:
|
||||
|
||||
- AI-DnD — production fork/base at `d72f7c1bda0f34fccd84afb7a25c34eb01c901de`.
|
||||
- ai-adventure — primary implementation reference for authoritative typed state events, checkpoint/head/replay semantics, and narrow local-only behavior.
|
||||
- Open Dungeon — UX and future-media reference only.
|
||||
|
||||
Critical Phase 0B prototype results:
|
||||
|
||||
- non-destructive Undo/Redo with a movable active head was demonstrated on AI-DnD without deleting history and without breaking branch-scoped memory isolation,
|
||||
- export/import must preserve active head position,
|
||||
- AI-DnD's relative-delta state protocol should not be retained as the generic narrative-state contract,
|
||||
- imported knowledge should be a separate subsystem rather than Story Cards,
|
||||
- runtime offline hardening is required for tokenizer data and fonts.
|
||||
|
||||
The original milestone text below is retained as the research execution record.
|
||||
|
||||
## 2. Candidate Repositories
|
||||
|
||||
Initial candidates:
|
||||
@@ -575,4 +597,22 @@ Phase 0 is complete only when:
|
||||
- the technical design is v1.0,
|
||||
- the actual implementation milestone plan has been written.
|
||||
|
||||
At that point, production implementation can begin.
|
||||
At that point, production implementation becomes eligible to begin, but still requires explicit approval and a milestone-specific execution prompt.
|
||||
|
||||
|
||||
## 17. Final Phase 0 Closure Record
|
||||
|
||||
Phase 0 definition of done is satisfied for architecture/planning purposes:
|
||||
|
||||
- finalists cloned and run,
|
||||
- test suites measured,
|
||||
- Ollama exercised locally,
|
||||
- offline/network behavior investigated,
|
||||
- critical history/state uncertainties prototyped,
|
||||
- fork/build strategy selected,
|
||||
- specification revised to v1.0,
|
||||
- technical design revised to v1.0,
|
||||
- production build milestones written,
|
||||
- foundational ADRs updated/added.
|
||||
|
||||
No production implementation prompt is part of this research plan.
|
||||
|
||||
Reference in New Issue
Block a user