Docs

Keep the repo legible to agents and humans.

Principles

• Docs rot silently — every code change is a possible doc change
• Optimize for decision-relevant, repo-owned truth per token
• Describe current state; keep history only in migration notes, changelogs, and decisions
• Lead with supported capabilities and next actions
• Prefer short, task-shaped sections and structured facts over narrative prose
• 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 tracking linked but distinct

Negative-state rule

When rewriting current-state docs, delete every absent, removed, or unprovisioned item, including specific names and category paraphrases, unless it changes a plausible current action. Prior curiosity, old tickets, and "agents ask about it" do not make an absence operational. If a limitation must stay, state one precise boundary and the supported path.