argument-governance

# /argument-governance - Argument System Governance ## Purpose Make the paper's argument inspectable as a system: ```text intent -> gap -> contribution data -> result -> claim -> contribution prior-work evidence -> innovation -> contribution claim/contribution -> boundary -> reviewer risk ``` Use this before major manuscript revision, before `/peer-review`, before `/self-review`, or after `/manuscript-reframe` when the draft needs stronger gap-contribution and claim-evidence control. ## Codex-Only Baseline Complete this workflow with Codex, local files, and the bundled checker. External reviewers, subagents, Gemini, or other model calls are optional advisory inputs only; do not require them and do not stop because they are unavailable. ## Enhanced Advisory Mode When the user explicitly enables an API-key-backed reviewer, Codex may request an external advisory pass after the local argument packet exists. Use this only as a second opinion: - keep API keys in environment variables, never in CSV, Markdown, logs, or manifests - send only the source subset the user or manifest permits - record the provider, model, source subset, prompt purpose, and output path - place results in advisory notes or reviewer-risk fields - never treat external output as evidence, source support, or a final gate ## Core Rules 1. Every contribution must answer a named gap. 2. Every main claim must belong to a contribution or the paper-level thesis. 3. Every lower-level claim must support a par...