Files

Phillip Tarrant 87c5748295 docs: implementation plan for canon log contract + api validation

Plan A of two: the JSON Schema contract, authored POC fixtures (deserter
origin + minimal world), and the api's runtime validation of every canon log
(422 on invalid, enforcing the §7 luck boundary). Five TDD tasks, all runnable
with pytest + Docker in-repo. Plan B (GDScript client construction/maintenance)
deferred until we're in Godot.

Plan: docs/superpowers/plans/2026-07-09-canon-log-contract-and-api-validation.md

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

2026-07-09 12:18:41 -05:00

adr

first commit

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

superpowers

docs: implementation plan for canon log contract + api validation

2026-07-09 12:18:41 -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.