§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 →