RFC-010: AIGP Runtime Governance Protocol — 22. Pre-Invocation Signal Registry
AIGP Specification › RFC-010: AIGP Runtime Governance Protocol › 22. Pre-Invocation Signal Registry
← 21. Deployment Manifest and Registry · Section index · 23. Cross-Domain Composition →
22. Pre-Invocation Signal Registry
22.1 Purpose
A deployment-time declaration of all signal sources contributing to admission decisions, with absence-posture enforcement.
22.2 Eight Registration Fields
Each signal source SHALL register:
| # | Field | Content |
|---|---|---|
| 1 | source_identity |
Unique identifier |
| 2 | source_class |
admissibility_gate / context_enrichment / output_pre_evaluation / moderation / custom |
| 3 | output_vocabulary |
Typed outputs this source emits |
| 4 | order_typing_declaration |
Which order this signal relates to |
| 5 | witness_class |
W1 (deterministic) / W2 (auditable) / W3 (human/heuristic) |
| 6 | scope_conditions |
When this source is active |
| 7 | governing_specification_binding |
Which spec this evaluates against |
| 8 | absence_posture |
signal_required or signal_optional |
22.3 Absence-Posture Enforcement
When absence_posture is signal_required and the source does not produce output, the protocol SHALL emit a typed gap referral and block conforming verdict emission.
22.4 Witness-Class Honesty Rule
Only deterministic, machine-evaluable signals MAY claim W1. Heuristic or human measurements are W2/W3. No blanket W1 claim is permitted across heterogeneous sources.
← 21. Deployment Manifest and Registry · Section index · 23. Cross-Domain Composition →