What problem does it solve?
It prevents wasted re-execution by turning already-collected evidence into a rigorous, policy-aligned gate decision for whether the harness can advance in the current judging phase.
Core Features & Use Cases
- Gate verdict from orthogonal evidence: Evaluates implementation/validation/policy evidence to derive a structured verdict and confidence.
- Scoped decision without refresh: Produces an allowed-next-route decision while explicitly avoiding actions like recovery, merge, close, or repo refresh.
- Noise absorption for low-severity findings: Keeps P2/P3 low-severity items as residual risk unless they form cross-layer, systemic threat patterns.
- Node-type aware strictness: Tightens or relaxes requirements based on worktrack contract node type (feature/refactor/research/bugfix/docs/config/test) with documented fallbacks.
- Upstream-constraint routing enforcement: Blocks pure code-repair routing when upstream constraints or contract/boundary/governance dependencies are decisive.
Quick Start
Use gate-skill when your harness is in WorktrackScope.judging and you already have the current round evidence needed to decide whether to pass, soft-fail, hard-fail, or block within the scope.