Phillip Tarrant
29474e5751
The aliveness POC (M0-M2) is proven, so redefine the project as the tactical CRPG the /mockups describe. Charter: §1 reframed (Code of Conquest / The Margreave), §10 combat = tactical + action-economy but GRIDLESS (tokens are flavor, no positional rules), §15 = button-driven actions + free-text NPC dialogue (Adjudicator reshaped to the optional free-text escape hatch), §16 adopts /mockups as the UI/systems bible, §17 rewritten to the game's scope. Two conflicts flagged not silently decided (§18): damage determinism (§7 vs mock ranges → M5) and class names (§8 vs mock callings → M4). Roadmap: M0-M2 kept as the built engine; M3-M9 re-sequenced around the mock screens (Theme+shell → creation → combat → dialogue → inventory/sheet → world systems → framing/AI-flavor/persistence). Streaming stays shelved; v2 NPC ideas preserved, re-homed to M6. 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.