RFC-010: AIGP Runtime Governance Protocol — 26. Gap Governance State Machine
AIGP Specification › RFC-010: AIGP Runtime Governance Protocol › 26. Gap Governance State Machine
← 25. Tri-State Verdict Discipline · Section index
26. Gap Governance State Machine
26.1 Purpose
When a verdict is REFUSE or REFER, the underlying gap requires lifecycle management. This section defines the general-purpose gap state machine.
26.2 States
| State | Meaning | Terminal |
|---|---|---|
open |
Gap identified, not yet accepted | No |
in_resolution |
Authority accepted, working on fix | No |
resolved |
Resolution evidence provided | Yes |
declared_permanent |
Irresolvable determination | Yes |
26.3 Valid Transitions
open→in_resolutionin_resolution→resolvedin_resolution→declared_permanent
No other transitions are permitted. Terminal states cannot transition.
26.4 Gap Types
| Type | Source |
|---|---|
verdict_refuse |
From REFUSE falsifier |
verdict_refer |
From REFER coaching record |
cross_domain |
From unregistered cross-domain interface |
signal_absence |
From missing required signal |
authority_reconcile |
From unresolved AR event |
accumulation_escalation |
From accumulation trigger |
26.5 Quality Moderator Integration
Unresolved gaps at immediate urgency feed the Quality Moderator risk posture. The immediate_unresolved_count property signals posture degradation when > 0.
26.6 Resolution Evidence
Resolved gaps SHALL carry: action taken, evidence of discharge, resolving authority, resolution timestamp.
© 2024-2026 Kanjani AI Research & Causum. All rights reserved. This specification is proprietary and subject to the terms in LICENSE.md. Unauthorized modification, redistribution, or commercial resale is prohibited.