§02e Jupiter — AIGP & Pre-Invocation — What MARS receives from AIGP at the boundary
Mars® Spec › §02e Jupiter — AIGP & Pre-Invocation › What MARS receives from AIGP at the boundary
← AIGP: Causum’s pre-invocation governance specification · Section index · Operating MARS without AIGP →
10. What MARS receives from AIGP at the boundary
Four artifacts may pass from AIGP to MARS at the handoff point. Each is described below: what it is, which part of MARS consumes it, and what happens when it is absent.
10.1 Pre-execution admission verdict
What it is. A tri-state verdict — ADMIT, REFUSE, or REFER — produced by AIGP before the model executes. The verdict is spec-version-stamped and accompanied by a recomputation witness from which any independent inspector can re-derive the ADMIT/REFUSE/REFER result from the order-typed prompt and the governing specification, without executing the original deployment.
What MARS does with it. The pre-execution admission verdict populates the inbound boundary of the MARS analysis chain. In the non-language bridge layer (§02c), the non-language-provenance anchor records what governed the input before it reached the model. The AIGP pre-execution verdict is the pre-invocation admissibility component of that record: it attests that the prompt was evaluated against the governing specification before execution and states the result. MARS treats an ADMIT verdict as affirmative evidence of pre-invocation admissibility; a REFUSE or REFER verdict at this position is a signal that the invocation was not cleanly admitted and may affect the certificate path.
When absent. If no pre-execution admission verdict is provided, the inbound non-language-provenance anchor is populated from whatever pre-invocation controls the licensee operated, or from the artifact directly. MARS does not require an AIGP-format admission verdict to proceed. The governing specification and domain model must still be provided; MARS does not synthesize them from AIGP outputs.
10.2 Order-typed enriched prompt
What it is. The governed input artifact that the model executed on: the original prompt, plus the context traversed by AIGP’s pre-execution enrichment, plus a typed gap record noting any context that was required but absent from the available assets. The enriched prompt is order-typed and bound to its source by a recomputation witness.
What MARS does with it. MARS verifies what the model produced against what the model was given. The order-typed enriched prompt is the governed input artifact whose output MARS verifies. Having the enriched prompt — rather than only the raw original prompt — allows MARS to verify the output against the full context the model had access to, not only the surface-form prompt the user or caller submitted. This is particularly significant when AIGP’s context enrichment materially changed what the model saw: the verification performed by MARS is verification against the enriched input, which is the correct object of verification.
When absent. If AIGP’s enriched prompt is not provided, MARS verifies the output against whatever input artifact is available — typically the prompt as submitted to the model. MARS can still perform verification; the scope of that verification is bounded by the input artifact it holds.
10.3 Output validation verdict
What it is. A tri-state verdict — ADMIT, REFUSE, or REFER — produced by AIGP at the output locus, after the model executes and before the output is handed to MARS. This verdict is produced by AIGP’s output validation mechanism and, on the AIGP side, initiates the certificate path. The verdict is recomputable and witness-bound.
What MARS does with it. The AIGP output validation verdict feeds the grounded-verdict invariant (Certificate Field 4) of the conformance certificate as an additional admission signal. An AIGP ADMIT at the output locus is evidence that the output passed AIGP’s pre-certificate evaluation; a REFUSE carries a falsifier annotation that MARS records. The AIGP verdict does not replace MARS’s own evidence-gathering verification — it is an additional input that MARS weighs alongside its own analysis results when forming the grounded conformance verdict.
When absent. If no AIGP output validation verdict is provided, Certificate Field 4 is populated from MARS’s own evidence-gathering verification verdict. MARS’s analysis is complete without the AIGP signal. The AIGP verdict, when present, enriches Field 4 with a pre-invocation-side perspective; its absence does not leave Field 4 empty.
10.4 Retained admission witnesses
What they are. For each pre-invocation governance decision — the admissibility verdict, the context enrichment determination, the sycophancy gate evaluation — AIGP retains a recomputation witness: a structured derivation trace sufficient for an independent inspector to re-derive the decision from the order-typed inputs and the governing specification version in effect at the time. The witnesses are retained under AIGP’s witness retention discipline in an assumed-immutable store, stamped with the governing specification version under which each decision was rendered.
What MARS does with them. These witnesses are the soundness anchors for MARS-issued composed verdicts. The conformance certificate issued by MARS carries, in the recomputation-witness invariant (Certificate Field 7), the multi-stage witness chain plus the soundness-anchor chain. When AIGP-retained admission witnesses are available, they form the pre-invocation segment of that chain: the conformance certificate’s soundness is attributable not only to the MARS analysis that produced it, but to the AIGP admission decisions that governed the invocation from the beginning. An independent inspector can trace the certificate’s soundness back through MARS’s analysis to AIGP’s pre-invocation decisions, re-deriving every step.
When absent. If AIGP-retained admission witnesses are not provided, the soundness anchor for MARS-issued composed verdicts is the MARS-retained recomputation witness alone. MARS retains its own recomputation witnesses for the analysis acts it performs; these are structurally complete soundness anchors for the MARS certificate. The chain is shorter — it begins at the MARS analysis, not at the pre-invocation admission decision — but it is still a complete, independently verifiable chain for the post-invocation segment of the governed round-trip.
← AIGP: Causum’s pre-invocation governance specification · Section index · Operating MARS without AIGP →