RFC-010: AIGP Runtime Governance Protocol — 18. Non-Linguistic Invocation Governance
AIGP Specification › RFC-010: AIGP Runtime Governance Protocol › 18. Non-Linguistic Invocation Governance
← 17. AIGP-Light Embedded Runtime · Section index · 19. Actuation Anchor and Reversibility Grading →
18. Non-Linguistic Invocation Governance
18.1 Purpose
AIGP governs AI invocations whose input is not language (EO/IR pixel streams, KLV telemetry, sensor engineering results). This section defines how non-linguistic invocations are admitted, recorded, and validated.
18.2 Input Modality Declaration
The REQUEST message SHALL support an input_modality field:
| Modality | Description |
|---|---|
text |
Natural language (default) |
image |
Still images |
video |
Video streams |
audio |
Audio signals |
sensor |
Sensor telemetry (EO/IR, radar, KLV) |
telemetry |
Platform/system telemetry |
structured_data |
Structured non-text data |
composite |
Multiple modalities combined |
18.3 Seven-Invariant Non-Language-Provenance Anchor
Every non-linguistic RECORD SHALL carry a non_language_anchor with seven fields:
| Field | Content | Purpose |
|---|---|---|
| 1 | engineering_program_identity |
Which program produced the result (content hash) |
| 2 | input_data_identity |
Which input was consumed (content hash) |
| 3 | engineering_result_binding |
SHA-256 of the raw engineering result |
| 4 | analysis_specification_identity |
Which spec governed the program |
| 5 | interpretation_generation_spec_identity |
Which spec governs the lift |
| 6 | causal_closure_witness |
Re-derivation proof (predicate from result under spec) |
| 7 | faithfulness_attestation |
Engine signature + timestamp + witness structure |
18.4 Anti-Flattening Gate
No non-linguistic signal SHALL enter the governance pipeline without a conforming anchor. The gate SHALL REFUSE on any of five conditions:
- Anchor absent
- Signature invalid (Field 7 attestation fails verification)
- Analysis specification unregistered
- Interpretation-generation specification unregistered
- Causal-closure witness fails re-derivation
18.5 Joint-Authority Attestation
The interpretation-generation specification SHALL support joint-authority attestation: both engineering authority and doctrine authority sign, and the joint-authority attestation hash SHALL be recomputable from both signatures.
← 17. AIGP-Light Embedded Runtime · Section index · 19. Actuation Anchor and Reversibility Grading →