Phillip Tarrant
aeb9ee4a9d
Settles the §17 class-name reconcile (charter §8 vs mock callings) in favor of the gritty callings, and gives every race trait a concrete rule. Feeds M4 character creation; combat ability kit deferred to M5. - Resolution model: deterministic value vs DC, LCK selects the borderline band (§7) — flat mods, no random d20, no advantage. - 5 saves (LCK owns none); death saves = LCK. - Races: features only, no stat mods; Nightsight ruling for darkvision. - 7 callings (charter-7), 2 names [CANON-TBD]; casters=MP, martials=cooldowns. - Flags two contract migrations for M4: canon-log gains `race`; deserter origin's allowed_classes migrates to new calling ids. 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.