§02e Jupiter — AIGP & Pre-Invocation — Operating MARS without AIGP
Mars® Spec › §02e Jupiter — AIGP & Pre-Invocation › Operating MARS without AIGP
← What MARS receives from AIGP at the boundary · Section index · Operating MARS with AIGP: the full governed round-trip →
11. Operating MARS without AIGP
MARS is a complete, self-standing specification. AIGP is not required.
When a licensee operates MARS without AIGP, the following substitutions apply:
Inbound non-language-provenance anchor. The inbound boundary of the MARS non-language bridge layer (§02c §2) is populated from whatever pre-invocation controls the licensee operates — a learned moderation classifier, a policy-file check, an access control list, or simply the artifact as submitted — or from the output artifact directly when no pre-invocation controls are in place. The anchor records what governed the input before it reached the model. MARS does not require that governance to have been performed by AIGP.
Certificate Field 4. In the absence of an AIGP output validation verdict, Certificate Field 4 is populated from MARS’s own evidence-gathering verification verdict. The evidence-gathering verification performed by the artifacts layer (§03) is the primary source of the grounded conformance verdict; AIGP’s output validation verdict is a supplementary signal that enriches Field 4 when available.
Soundness anchor for composed verdicts. The soundness anchor for MARS-issued composed verdicts is the MARS-retained recomputation witness for the analysis acts MARS performed. This witness satisfies the structural requirements for Certificate Field 7. The chain does not extend into the pre-invocation phase, but it is complete for the post-invocation segment.
Governing specification and domain model. The governing specification and domain model must be supplied independently. MARS does not synthesize a governing specification from pre-invocation artifacts or from the model output. If no governing specification is provided, MARS cannot perform spec-relative conformance verification; the licensee is responsible for supplying the governing assets.
The licensee declares, in the governing specification, which pre-invocation controls are in place. MARS records what was declared; it does not enforce the presence of AIGP. A deployment that operates MARS without AIGP is a complete MARS deployment. Its conformance certificates are soundly issued against the evidence gathered and the witnesses retained by MARS. The certificates simply do not carry AIGP admission witnesses in the soundness-anchor chain, because no such witnesses exist.
← What MARS receives from AIGP at the boundary · Section index · Operating MARS with AIGP: the full governed round-trip →