Files
code_of_conquest_dnd/docs
Phillip Tarrant 16527e9d60 docs(spec): content & canon build tool design
Compiler for content/lore/*.md (MD bible + fenced YAML) -> validated
content/world (client) + content/server (server-only) JSON. Python tool
under tools/, manual build + CI --check, band-number-free (client owns the
midpoint mapping), validation gate aborts on any schema violation. Promotes
Duncarrow as the acceptance test; documents the specimen fixes promotion
must apply (shrine->place rename, related stubs, dropped knows/related
spoiler links).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HuHRPE7VfppUJEaoGBEUqZ
2026-07-11 17:39:17 -05:00
..
2026-07-09 11:17:54 -05:00
2026-07-11 11:14:06 -05:00

/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 next
  • adr/ — 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.