Docs Governance

Docs hold the current truth and the dated records behind it. Git keeps every diff and pull requests explain each change, so no doc records its own edit history.

Detect the Setup

The markers are an AGENTS.md that routes to docs/, a decision register (by default docs/product-decisions.md), a glossary (docs/CONTEXT.md), and an index (docs/README.md).

• Setup present: follow this skill. Where the repository's docs name other paths, use theirs.
• Record-based setup (CHG-* and DEC-* record files, a document registry, front-matter histories): follow that repository's own governance docs, and offer the move in BOOTSTRAP.md when the owner asks.
• No setup, and the owner asks to adopt it: follow BOOTSTRAP.md.
• No setup otherwise: keep the repository's conventions.

1. Read Before You Act

Before product, planning, implementation, review, or any external action, read the docs AGENTS.md routes the work to: the decision register, the glossary, and the docs for the area you touch. When no route matches, start at docs/README.md.

Act only in agreement with current owner decisions and the docs that follow from them. Where a doc is missing or unclear, ask the owner instead of choosing a direction. When requested work conflicts with the docs: