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>
coc-rpg
AI-driven single-player, party-based fantasy RPG. Godot 4 client, FastAPI proxy, AI as Dungeon Master.
Read CLAUDE.md first — project charter and working agreement. It is the source of truth. If code disagrees with it, the charter wins until the charter is changed.
The one rule
Code owns state. AI owns text. (charter §2)
Repo layout
/client Godot 4.7 game client (GDScript) — ALL game state, ALL game rules
/docs Client-specific docs (scenes, input, combat wiring)
/api FastAPI proxy — auth, metering, prompt routing, logging (charter §4)
/docs API-specific docs (endpoints, model routing, deploy)
/prompts Role prompts — source code, versioned, reviewed (charter §5, §16)
/content Authored game data — quests, NPC knowledge lists, fallback text
/quests Story skeletons and quest definitions
/npcs Per-NPC knowledge lists (charter §6 — "the whole design")
/fallback Authored degraded-DM text for every AI surface (charter §13)
/docs Cross-cutting docs — roadmap, ADRs, planning affecting both sides
/adr Architecture Decision Records
The three processes (charter §4)
client (GDScript) ──HTTP──▶ api (FastAPI) ──▶ Replicate / Ollama
The client holds no API key, ever. It knows one base URL and a set of role endpoints. It sends game state, receives text.