Phillip Tarrant
f5e6c59f2a
A laptop-dev enabler (planned, not specced): extend the proxy's M1 model-call pipeline with an Ollama Cloud backend reachable via API key, plus a switch to flip local-ollama <-> ollama-cloud, so AI works off the homelab. Reconciles against §4: the API key and provider choice stay server-side in the proxy (the client never holds a key, never picks the backend). The title Settings-button "config file" splits — the client may hold only the proxy base URL / profile (folds into M9); the provider/key switch is proxy config. Filed under a renamed "Landed / planned out of band" section and pointed to from the sequencing table as the next task before M5. 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.