§02e Jupiter — AIGP & Pre-Invocation — What this layer covers
Mars® Spec › §02e Jupiter — AIGP & Pre-Invocation › What this layer covers
Section index · The pre-invocation / post-invocation boundary →
Mars® Protocol — §02e: AIGP and Pre-Invocation
Version 1.0-draft
1. What this layer covers
This layer specifies the pre-invocation phase of the Mars® governed invocation: the registry and typing requirements for pre-invocation signals, the witness-class taxonomy governing how those signals enter the §02a multi-stage witness chain, the absence-posture machinery, the cross-phase corroboration mechanism, and the procedural-confidence derivation discipline.
It also specifies the boundary contract between Mars® and AIGP (Autonomous Intelligence Governance Protocol) — the pre-invocation governance specification owned by Kanjani AI Research and commercially licensed exclusively through Causum — including what Mars® receives from AIGP at the handoff point, how the full governed round-trip is structured, and how Mars® operates when AIGP is absent.
The structural boundary. The boundary between the pre-invocation and post-invocation phases is defined by the production of the model output — not by clock time, network topology, or deployment architecture. A system that caches a model output and verifies it hours later is operating on the post-invocation side. A system that enriches a prompt just before model execution is operating on the pre-invocation side. The boundary is structural, not temporal.
The boundary partitions phases, not protocols. Neither specification is confined to one side of it. AIGP governs the pre-invocation phase and, at its own stages 15–17 (persistence and memory, observation and audit, reflection and optimization), the post-invocation phase; the bundled result of a governed invocation returns to AIGP for that management. Mars® establishes the governed runtime of the invocation itself — measuring, conforming, and gathering evidence as the output is produced, halting release mid-stream on a REFUSE under the incremental-validation mode below — and continues after the boundary to issue the conformance certificate (§02b), gate downstream actuation (§02c), and conduct post-hoc forensics (§02f). Reading the boundary as a partition between the two protocols — AIGP before, Mars® after — does not describe this architecture: it omits the governed runtime, and it omits AIGP’s own post-invocation stages.
Source-agnosticism. This layer is source-agnostic. AIGP is one pre-invocation governance system. A learned admission classifier, a policy-engine filter, a rules-based access control system, a human review decision, or any other system that produces a typed pre-invocation signal may register under §3. The structural requirements are identical regardless of source. The only property AIGP provides that non-AIGP sources generally do not is a recomputation witness compatible with the §02a §5a.2 chain structure — that distinction is handled by the witness-class taxonomy (§4), not by source-specific rules.
Dependencies. This layer depends on §02a (base analysis, multi-stage witness chain, discrete-representation genus), §02b (delta-attestation lifecycle, conformance certificate, specification registry), §03-i (semantic binding — produces the aspect-keyed query library and data-source characterization that pre-invocation signals referencing data-source state consume; a pre-invocation signal that references data-source content without the semantic binding substrate is not a governed reference), and §03-iii (evidence-gathering verification — produces the recomputation witnesses that the W1–W3 witness classes of §4 sit atop; the W1 full recomputation witness is a prior-stage chain link in the §03-iii §2.7 recomputation witness chain; an implementation of §02e that does not ground its W1–W3 signal witnesses in the §03-iii governed evidence substrate produces witness links that are structurally detached from the governed verification chain). The pre-invocation signals specified here are battery inputs to the §02a analysis; their absence postures govern the §02a verdict; their witness classes determine chain continuity through the §02a §5a.2 chain.
Section index · The pre-invocation / post-invocation boundary →