Phillip Tarrant
db5ee247e7
Schema lock built bottom-up from the Duncarrow specimen (candidate-town.md): - disposition rungs as bands over the engine integer (code owns numbers) - town fact = engine reveal-topic (authoring layer over §6, no new runtime) - MD bible -> build -> JSON; split by role (game vs server), secrecy as lint - canon home: content/lore (source) -> content/world + content/server (built) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HuHRPE7VfppUJEaoGBEUqZ
/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.