govern-project-docslisted

# govern-project-docs Keep project documents aligned with development reality through a small loop: resolve authority, run Impact before work, run Closeout before completion, and separate mechanical checks from AI semantic review and human decisions. ## Core Rule Govern by `(question, scope)`, not by filename. A project may use any document structure if each governed question resolves through one rule or an explicitly ordered set of sources. Do not treat Skill output as project authority. Findings are evidence until the durable conclusion is written back into mapped project documents. ## Inputs Use a project adapter with only pointers, rules, and boundaries. Do not copy current project facts into the adapter. Read `references/adapter-schema.md` when creating or validating an adapter. Use `scripts/govern_project_docs.py` for deterministic adapter, fixture, and live diagnostic checks. ## Impact Run Impact before work starts or when the task meaning changes. Return: - affected governed questions and authority rules; - evidence entrypoints to inspect; - protected or excluded paths touched; - candidate document authorities likely to need update; - human approval boundaries. Impact result: - `pass` when the work has mapped authority and no known human or protected boundary; - `unproven` when the adapter is missing, authority, evidence, or approval is missing or uncertain, or excluded paths are touched; - `fail` only for directly provable structural defects. ## Clo