What problem does it solve? High-stakes decisions need an authoritative verdict from a reviewer that is genuinely independent of the primary agent and artifact author, but routing results alone cannot prove that independence. This Skill enforces caller-side lineage verification and exact repository-grounded scope before any governance verdict is accepted. ## Core Features & Use Cases - Independent reviewer enforcement: Records the lineage and source of the primary and artifact author before dispatch, then verifies the observed reviewer lineage afterward; unknown lineage stays unknown. - Bounded routing invocation: Sends one EOF-delimited JSON routing request to the plugin's coordinator.py using the governance.repository action with frontier quality and maximum effort, never reconstructing provider commands. - Advisory fallback: When no known-distinct eligible reviewer exists, the response is kept as advisory content with no authoritative-approval claim. - Use Case: Before merging a contested architecture change, dispatch a governance review pinned to the exact source head, verify the reviewer's lineage differs from both the author and primary agent, and accept the verdict only when independence is positively established. ## Quick Start Ask the agent to run a governance review on the current repository at the exact expected source head with an independent reviewer.
