§02e Appendix — AIGP↔Mars Bridge — What this appendix covers
Mars® Spec › §02e Appendix — AIGP↔Mars Bridge › What this appendix covers
Section index · The boundary, restated in AIGP terms →
Mars® Protocol — §02e Appendix: The AIGP ↔ Mars Bridge
Version 1.0-draft — companion to §02e (AIGP and Pre-Invocation)
1. What this appendix covers
§02e specifies the pre-invocation boundary contract abstractly and source-agnostically: any system that produces a typed, witness-bound pre-invocation signal may register. This appendix instantiates that contract concretely for AIGP — the Autonomous Intelligence Governance Protocol — which is the preferred pre-invocation companion for Mars®.
It defines the bridge in the only two directions in which the two protocols compose, and it does so by naming AIGP’s actual emitted objects (RFC-009 messages, evidence schemas, and verdicts) and mapping them onto Mars® ingest points, boundary artifact classes (§02e §2), and witness classes (§02e §5).
The two directions are distinct applicability modes and are specified separately:
- Mode 1 — Data plane (AIGP → Mars). AIGP’s emitted evidence is the subject Mars analyzes and certifies. AIGP registers as a pre-invocation signal source; its objects enter the §02a battery as inputs and its verdicts participate in cross-phase corroboration (§02e §6).
- Mode 2 — Governance plane (AIGP governs Mars’s own AI). The AI invocations Mars itself performs — probabilistic battery methods (§02a), evidence-gathering traversal (§03-iii), and governed data/benchmark generation (§03-iv) — are themselves governed invocations, gated by AIGP before execution and recorded after.
Mode 2 is the precondition for Mode 1 being trustworthy. Mars asserts independent-inspector evaluability and prohibits model-internal confidence as a gating signal (AR4; §02e §13). Because Mars’s own operations use AI, an ungoverned internal AI call would place an ungoverned substrate beneath the certificate. Governing those calls with AIGP closes the reflexivity: the governor is itself governed.
Dependencies. This appendix depends on §02e (signal registry, witness classes, absence postures, cross-phase corroboration), §02a (battery, multi-stage witness chain), §02b (delta-attestation lifecycle, conformance certificate, registry), §02c (output validation gate, actuation), and §03-iii (evidence-gathering verification, grounded verdict). On the AIGP side it depends on RFC-009 (protocol messages, HMAC authentication, governance modes, the 17 governance stages) and the AIGP evidence schemas (anticipation.json, scope-envelope.json).
Ownership note. AIGP is owned by Kanjani AI Research and is commercially licensed exclusively through Causum; Mars® is owned by Causum. The two are separately-owned specifications that compose across the boundary defined here. This appendix does not merge the estates; it declares the interface between them.