docs-governance

Topics in the source

• Documentation Governance Router
• When to Activate
• Role Contract
• Intent Routing
• Read-Only Audit
• When to Use
• How It Works
• Examples

Use this optional router to select the smallest existing ECC capability for a documentation-governance request. The router does not create a parallel project management system and does not make documentation authoritative over code, tests, Issues, or maintainer decisions. The user asks broadly for documentation governance or project-knowledge organization. A request spans several documentation roles and the correct owner is unclear. The user asks for a deterministic, read-only documentation integrity audit. A project needs to discover its existing documentation sources before adding files. Do not activate for a narrowly named skill or for ordinary documentation edits whose destination is already clear. Read the artifact-role contract before interpreting .governance/docs-map.json or default filenames. Logical roles own facts; filenames are fallbacks. Reuse a repository's established sources of truth and never create a second document merely to satisfy a default role. | User intent | Route to | |---|---| | Adopt or maintain a constitution, map, status, and history spine | living-docs-governance | | Record a hard-to-reverse architecture decision | architecture-decision-records | | Pre

This is an excerpt. Refer to the complete source and its current requirements.