release-governance

# /release-governance - Release Evidence Governance ## Purpose Prepare release-facing academic artifacts with explicit evidence control. The core rule is: ```text release truth = ref + artifact + gate ``` Do not infer release truth from memory, a branch name, a pull request title, a local file cache, or an agent draft. ## Trigger Words This skill activates on: `release governance`, `release evidence`, `camera-ready`, `rebuttal packet`, `artifact packet`, `claim ledger`, `human evidence gate`, `release packet`, `/release-governance`. ## Core Rules 1. Name the exact ref, artifact, and gate behind every release-facing claim. 2. Keep draft advisory evidence, verified artifacts, and final human evidence separate. 3. Do not promote agent or Gemini review output into final evidence. 4. Do not treat ignored, untracked, cached, or local-only assets as submitted artifacts. 5. Do not treat a repository check as venue, submission-system, or scientific compliance. 6. If two refs diverge, name both and scope which one is canonical for each artifact. 7. If a worktree is dirty, list the dirty paths and mark the packet as draft until changes are committed or explicitly scoped. ## Evidence States Use `references/evidence_state_schema.md` for the shared states: - `draft_advisory` - `verified_artifact` - `human_final` `human_final` requires an explicit human confirmation gate when the project schema provides one. Agent drafts, reviewer suggestions, generated summaries, simulations, a...