Documentation Standard

• Document why and boundaries, not line-by-line what code does.
• Keep module docs concise and decision-focused.
• Keep generated blocks fenced with markers; never hand-edit generated ranges.
• When behavior changes, include request/response examples.

README sync rules

• .env.example is source of truth for env vars.
• Auto-generate env var table in README between markers.
• Keep setup commands validated by CI.

ADR rules

• Add ADR for cross-cutting changes (data model, migration path, command contracts, architecture).
• Include context, decision, consequences, alternatives.
• Link PR and follow-up tasks.

CI rules

• docs:generate must be deterministic.
• docs:check must fail if generated docs are stale.
• Command-contract changes without docs updates are blocking.

Reviewer/fixer integration

1. Reviewer checks for missing/outdated docs in changed scope.
2. Fixer updates docs artifacts and templates.
3. Re-run docs checks and reviewer confirmation.

Deliverable format

Return:

1. Docs artifacts generated/updated
2. Files changed with paths
3. Drift checks run and result
4. Gaps intentionally deferred with explicit owner/date