RFC-010: AIGP Runtime Governance Protocol — 23. Cross-Domain Composition
AIGP Specification › RFC-010: AIGP Runtime Governance Protocol › 23. Cross-Domain Composition
← 22. Pre-Invocation Signal Registry · Section index · 24. Conformance Certificate →
23. Cross-Domain Composition
23.1 Purpose
When predicates from different authority domains compose, the composition SHALL traverse a registered cross-domain typed interface.
23.2 Interface Registration (7 Fields)
| # | Field |
|---|---|
| 1 | source_domain_identity |
| 2 | target_domain_identity |
| 3 | joint_authority_attestation (both domain authorities sign) |
| 4 | typed_translation_rule_set (in decidable fragment) |
| 5 | loss_of_information_record |
| 6 | scope_of_applicability_certificate |
| 7 | registration_timestamp |
23.3 Composition Gate
No conforming verdict SHALL emit on a composed predicate if the composition traversed an unregistered cross-domain interface. The verdict SHALL be downgraded to REFER with reason cross_domain_interface_unregistered.
23.4 Knowledge-Gap Routing
Unregistered composition attempts SHALL emit a KNOWLEDGE_GAP_ROUTING object with a four-state machine: open → under_investigation → resolved | declared_irresolvable. The object identifies the joint authority responsible for registering the missing interface.
← 22. Pre-Invocation Signal Registry · Section index · 24. Conformance Certificate →