Go to file

Phillip Tarrant 1f39ec709e Merge client canon log engine (Plan B)

Client-side GDScript engine that constructs the canon log at new-game
(origin + world + character creation) and maintains its invariants turn
to turn. Headless GUT-tested logic layer (48 tests): typed RefCounted
model with invariants-in-the-model, Luck-centric GameState, ContentDB
mirroring the api id-resolver, NewGame.construct, and a pure §12 tag
extractor. Binds to the Plan A canon log contract.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-09 15:34:41 -05:00

api

chore(api): canon log follow-ups — hardening, unified 422, contract doc

2026-07-09 13:03:59 -05:00

client

chore(client): Godot rewrote project.godot header on open

2026-07-09 15:34:41 -05:00

content

feat(content): POC deserter origin + world fixtures with id-resolution check

2026-07-09 12:37:29 -05:00

docs

docs(plan): client canon log engine (Plan B) implementation plan

2026-07-09 13:58:21 -05:00

.dockerignore

chore(api): bundle canon log schemas into image; repo-root build context

2026-07-09 12:45:49 -05:00

.gitignore

chore: gitignore and untrack .claude harness files

2026-07-09 11:24:46 -05:00

CLAUDE.md

docs: add git workflow to working agreement (§18)

2026-07-09 11:27:04 -05:00

docker-compose.yml

fix(api): constrain disposition_overrides keys; close docker paper cuts

2026-07-09 12:54:01 -05:00

README.md

first commit

2026-07-09 11:17:54 -05:00

README.md

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.