Skip to content
Mars® Protocol

§02e Jupiter — AIGP & Pre-Invocation — Operating Mars® with AIGP: the full governed round-trip

Mars® Spec › §02e Jupiter — AIGP & Pre-Invocation › Operating Mars® with AIGP: the full governed round-trip

← Operating Mars® without AIGP · Section index · Five architectural refusals (negative-space discipline) →

12. Operating Mars® with AIGP: the full governed round-trip

When both AIGP and Mars® are deployed, the following sequence constitutes the full governed round-trip:

  1. AIGP evaluates the inbound prompt against the governing specification. The result is a tri-state pre-execution admission verdict — ADMIT, REFUSE, or REFER — accompanied by a recomputation witness. A REFUSE or REFER at this stage stops or diverts the invocation; the model does not execute.

  2. On ADMIT: AIGP produces the order-typed enriched prompt and the admission recomputation witness. For context-starved prompts, this step includes pre-execution traversal of knowledge bases and data sources; the enriched prompt carries the traversed context and any typed gap record. For prompts that are not context-starved, the enriched prompt is the original prompt typed and witness-bound.

  3. The model executes on the enriched prompt, under the Mars® governed runtime. The model sees the governed input artifact, not only the surface-form prompt. This phase is not ungoverned: Mars® measures and conforms the invocation as it proceeds, and where output is produced incrementally under the declared incremental-validation mode (§2), release is gated per increment and a REFUSE halts release mid-stream with a typed partial-emission event. Agentic acts within the invocation — tool and agent authorization, intermediate reasoning — are in-invocation acts governed here, not deferred to the output locus.

  4. AIGP evaluates the model output at the output locus, producing a tri-state output validation verdict — ADMIT, REFUSE, or REFER. On the AIGP side, this verdict initiates the certificate path and gates the sycophancy evaluation. The output, together with the AIGP output verdict and the retained admission witnesses, is handed to Mars®.

  5. Mars® receives the output, the AIGP output verdict, and the AIGP-retained admission witnesses. Where AIGP emits the Order-Typed Recomputation Witness Profile, the pre-invocation signal registry (§3) records the AIGP source as a W1 source and the pre-execution admission verdict enters the §02a §5a.2 witness chain as the first pre-invocation link with the AIGP recomputation witness as its W1 witness record. Where the profile is not emitted, the same link enters as W2 or W3 and the witness-class annotation records precisely where recomputability ends.

  6. Mars® performs evidence-gathering verification (§03) against the governing specification. The analysis battery evaluates the output; the symbolic lift produces the order-typed representation; the battery execution discipline (§02a §3a) sequences the verification acts under its declared ordering constraints. The result is a grounded conformance verdict.

  7. Mars® issues the conformance certificate (§02b §2). The grounded-verdict invariant (Certificate Field 4) carries the grounded conformance verdict together with the AIGP output validation verdict as a co-attestation. The recomputation-witness invariant (Certificate Field 7) carries the multi-stage witness chain for the Mars® analysis acts, with the soundness-anchor chain extending back through the AIGP-retained admission witnesses to the pre-execution admission decision.

  8. The certificate is consumed at the downstream actuation gate (§02c §4). The actuation anchor receives the certificate and governs whether the downstream act proceeds, is held, or is refused.

  9. The governed result is returned to AIGP for post-invocation management. The bundled result — the grounded verdict, the certificate, and the retained witness chain — is presented back to AIGP, whose own post-invocation stages (persistence and memory, observation and audit, reflection and optimization; §9) operate over the completed invocation. Findings arising there are typed inputs to post-hoc processes, including the Mars® post-hoc forensic layer (§02f), and may surface reinforcement signals under the symmetric reinforcement mechanism (§03-iii §2.8). This step closes the loop: the pre-invocation gate that admitted the invocation is also the layer that records and reflects on its completed result.

The full round-trip is end-to-end recomputable. An independent inspector holding the governing specification version and the retained witnesses — AIGP’s admission witnesses and Mars®’s analysis witnesses — can re-derive every verdict in the chain, from the pre-invocation admission decision through the grounded conformance verdict in the certificate, without trust in any component of the deployment.

← Operating Mars® without AIGP · Section index · Five architectural refusals (negative-space discipline) →