Regroup the flat status list into milestones with a 'what this proves' goal, and tag every item with its §2 side (state/text/both), dependencies, and milestone goal. Sequencing calls locked: M3 leads with the playable dungeon (Adjudicator→Combat→Luck) before the comedic roles (Improviser/Banter); streaming deferred until the M2 dialogue experiment proves aliveness. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
/docs — cross-cutting docs
Anything affecting both client and api, plus planning and roadmap. Side-specific docs live in /api/docs and /client/docs.
Put here:
roadmap.md— phases, POC scope, what's nextadr/— Architecture Decision Records- Shared contracts — canon log schema, tag syntax, retry policy (§11, §12)
- Anything spanning the HTTP boundary
The charter itself — CLAUDE.md — stays at the repo root. It is the source of truth; these docs elaborate, they do not override it.