Reference: Mars® as AIGP's Post-Invocation Consumer
Reference: Mars® as AIGP’s Post-Invocation Consumer
Informational reference. AIGP is owned by Kanjani AI Research & Causum and commercially licensed exclusively through Causum. Mars® is a separately-owned Causum specification. This document declares the interface by which AIGP-emitted evidence is consumed by Mars®; it does not merge the two estates.
© 2024-2026 Kanjani AI Research & Causum. All rights reserved.
1. Why this reference exists
AIGP governs the pre-invocation phase of an AI invocation and emits evidence about what happened. Mars® (Causum) governs the post-invocation phase: it analyzes evidence, verifies conformance against a governing specification, and issues an independently re-derivable conformance certificate.
The two protocols compose across a single structural boundary — the moment the model produces its output. AIGP owns everything up to and including output generation; Mars® owns verification and certification of the output. The authoritative specification of this interface is Mars® §02e Appendix: The AIGP ↔ Mars Bridge.
2. The boundary in AIGP terms
The pre/post-invocation boundary is structural (the production of model output), not temporal. In AIGP’s 17 governance stages:
- Stages 1–11 and stage 12 (
output_generation) are pre-invocation with respect to Mars®. - Stage 14 (
post_invocation_record) is the point at which AIGP-emitted evidence (RECORD, andTRACEwhere enabled) becomes available for Mars® ingest.
3. What Mars® consumes from AIGP
| AIGP object | Mars® use |
|---|---|
REQUEST decision (ALLOW / ALLOW_WITH_CONSTRAINTS / DENY) |
Admissibility signal → ADMIT / REFUSE / REFER |
RECORD (tokens, duration, guardrail, system_prompt_hash) |
Output-validation input |
TRACE spans (17 stages) + d_dna_signature |
Prior-stage witness-chain links |
ANTICIPATE / VERIFY (MATCH / PARTIAL_MATCH / MISMATCH / VIOLATION) |
Cross-phase corroboration against the Mars® analysis battery |
scope-envelope (permissions, budgets, autonomy_level) |
Declared certificate scope + actuation bounds |
4. Witness-class expectation (important)
Mars® classifies evidence by content, not by source brand. AIGP’s HMAC-SHA256 request signing (RFC-010 §4) and the D-DNA d_dna_signature establish tamper-evidence and attributability, not independent re-derivability. Under the Mars® witness taxonomy:
RECORD/TRACE→ W2 (execution record).- HMAC/D-DNA-signed decision without a derivation trace → W3 (attestation).
- An
ANTICIPATEcriterion withmeasurement: DETERMINISTICand a machine-evaluableassertion→ W1 (full recomputation witness) for that criterion only.
To have any AIGP signal treated as W1, emit a derivation trace sufficient for an independent inspector to re-derive the signal value from the order-typed input and the policy/spec version — not merely a signature. The normative way to do this is the Order-Typed Recomputation Witness Profile (specification/extensions/mars-w1-witness-profile.md): a deployment that emits it for a decision class produces W1 links for that class; everything else stays W2/W3. Absent the profile, AIGP evidence is W2/W3 and is annotated as such. AIGP integrations SHOULD NOT represent AIGP evidence as W1 by default.
5. Governance-mode signaling
AIGP-emitted evidence SHOULD carry the active governance mode (RFC-010 §5):
- ENFORCE — the admissibility gate is treated by Mars® as
signal-required; a fail-open ALLOW-on-unreachable is not a valid admission verdict. - REPORT / REPORT-TRACE — REQUEST checks return ALLOW for observability; Mars® treats these as optional observations and marks pre-invocation admissibility outside the certified scope.
6. Reciprocal direction
Beyond supplying evidence, AIGP also governs the AI invocations Mars® itself performs (probabilistic analysis methods, evidence-gathering traversal, and governed generation). In that direction AIGP acts as the pre-invocation gate in front of Mars®’s internal AI use, and each AIGP admission witness becomes a pre-invocation link in the resulting Mars® certificate. See the Mars® §02e bridge appendix for the normative treatment.
7. Authoritative source
The normative interface — crosswalk tables, witness-class honesty rule, 17-stage boundary mapping, and the BR property series — is maintained in the Mars® repository at spec/02-jupiter/02e-appendix-aigp-bridge.md. The bundle shape is governed by the co-owned schema schemas/aigp-evidence-bundle.json (Mars repo). The AIGP-side W1 emission profile is specification/extensions/mars-w1-witness-profile.md (this repo).