RFC-010: AIGP Runtime Governance Protocol — 25. Tri-State Verdict Discipline
AIGP Specification › RFC-010: AIGP Runtime Governance Protocol › 25. Tri-State Verdict Discipline
← 24. Conformance Certificate · Section index · 26. Gap Governance State Machine →
25. Tri-State Verdict Discipline
25.1 Purpose
The verdict is computed mechanically from obligation results. No thresholds, no weights, no soft logic.
25.2 Verdict Computation Rule
Given a multiset of obligation results {(passed, has_falsifier)}:
| Condition | Verdict |
|---|---|
ANY has_falsifier == true |
REFUSE |
ALL passed == true |
CERTIFY |
| Neither condition | REFER |
25.3 Properties
- Order-independent: Shuffling the obligation list produces the same verdict
- Falsifier absolute: One falsifier among 1000 passes → REFUSE
- No model-internal signals: Verdict derives from structural obligation results only
- Immutable after computation: Same inputs always yield same output
25.4 Per-Verdict Behaviors
| Verdict | Actionable | Proceeds to Actuation | Display Class |
|---|---|---|---|
| CERTIFY | Yes | Yes | pre_verified |
| REFUSE | No | No | suppressed |
| REFER | No | No | requires_judgment |
25.5 Integration with Actuation Gate
Only CERTIFY verdicts SHALL pass the actuation gate’s originating-certificate check. REFUSE and REFER verdicts structurally cannot drive actuation — this is a protocol property, not a policy.
← 24. Conformance Certificate · Section index · 26. Gap Governance State Machine →