Skip to content
AIGP

RFC-010: AIGP Runtime Governance Protocol — 20. Governed Decision Service Pattern

AIGP Specification › RFC-010: AIGP Runtime Governance Protocol › 20. Governed Decision Service Pattern

← 19. Actuation Anchor and Reversibility Grading · Section index · 21. Deployment Manifest and Registry →

20. Governed Decision Service Pattern

20.1 Purpose

A governed decision service is a real-time AI service that emits governance-verified decisions with freshness bounds, staleness detection, and degradation modes.

20.2 Decision Bundle

Every governed decision SHALL emit a DECISION_BUNDLE carrying:

  • Order-typed verdict
  • Three-invariant recomputation witness (traversal trace, evidence record, uncertainty-reduction record)
  • Per-aspect freshness bounds with declared degradation mode
  • As-of timestamps for grounding evidence
  • Governing asset versions in effect (governing spec hash, KB hash, calibration hash)
  • Decision latency vs declared maximum

20.3 Degradation Modes

Mode Behavior on Stale Evidence
fail_closed REFUSE — stale evidence on this aspect blocks actuation
fail_stale_declared Emit with staleness flag visible to consumer

silent_stale_emission is structurally prohibited (no enum value exists).

20.4 Freshness Propagation

The decision bundle’s freshness disposition SHALL propagate to the actuation gate. A bundle with stale fail_closed aspects SHALL NOT pass the actuation anchor.

← 19. Actuation Anchor and Reversibility Grading · Section index · 21. Deployment Manifest and Registry →