govern-ai-codinglisted

# Govern AI Coding Keep complex AI coding changes aligned with project facts, decisions, and evidence. Resolve authority before edits, then bind semantic review, final content, project validation, and human decisions before calling work complete. ## 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. ## Applicability Gate Run this lightweight gate immediately after loading the Skill and before creating an adapter, governance document, receipt, or extra validation: 1. Applicability is established when the user explicitly requests GAC setup, adapter creation or repair, diagnosis, execution, or closeout, or when a verifiably active governed event must resume Freeze, validation, or Closeout. 2. Otherwise, locate an existing valid adapter. Do not create an adapter as a discovery fallback. 3. When relying on the adapter, compare the exact intended change paths and governed question with its declared rules. At least one actual boundary must be present: a mapped authority rule, protected path, required human approval, governed decision, historical interpretation, or governed release authorization. Adapter existence by itself is insufficient. 4. If neither branch applies, *