Docs

Keep the repo legible to humans and agents.

Principles

• Docs rot silently — every code change is a possible doc change
• Describe current state; keep history only in migration notes, changelogs, and decisions
• Keep routing docs short and point to deeper docs instead of duplicating them
• Use repo-relative links for in-repo docs
• Keep repo docs, agent guidance, and work artifacts linked but distinct

Handoffs

Not docs work: boot/readiness setup; baseline PR, issue, contributor, or security policy templates; independent code review; runtime verification.

Workflow

1. Audit the doc surface