Files

Phillip Tarrant 800811dac2 docs: canon log schema + origin seed design

Design spec for the §11 canon log, plus origin seeds as thin initial-state
overlays over a single static world. Three layers (world content / origin seed /
runtime canon log), the in/out boundary (numeric Luck never enters the AI
payload, §7), field-level schemas, new-game construction order, turn-to-turn
maintenance, and JSON storage validated on both client and api.

Folds content/npcs and content/quests under content/world/; adds
content/world/{locations,items} and content/origins. fallback/ kept outside
world/ (authored prose, not id-referenced).

Spec: docs/superpowers/specs/2026-07-09-canon-log-schema-design.md

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

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

adr

first commit

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

superpowers/specs

docs: canon log schema + origin seed design

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

README.md

first commit

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

roadmap.md

first commit

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

README.md

/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.