Skip to content

§02e Appendix — AIGP↔Mars Bridge — Mode 2 — AIGP underpinning Mars's AI initiatives

Mars® Spec§02e Appendix — AIGP↔Mars Bridge › Mode 2 — AIGP underpinning Mars’s AI initiatives

← Mode 1 — analyzing AIGP-emitted data with Mars · Section index · What each side must provide for the bridge to be conformant →

4. Mode 2 — AIGP underpinning Mars’s AI initiatives

Mars® performs AI invocations at three loci. Each is a governed invocation whose pre-invocation phase is AIGP.

Mars® AI use AIGP governance object Effect
Probabilistic battery methods (§02a) REQUEST (CHECK) before, RECORD after Each method call is admitted and recorded; the AIGP admission witness becomes the pre-invocation link for that method’s sub-chain
Evidence-gathering traversal (§03-iii) scope-envelope (model/data-source allowlist, budgets, autonomy_level) The traversal agent operates under default-deny scope; out-of-scope KB/data-source access is denied
Governed data / benchmark generation (§03-iv) ANTICIPATE/VERIFY + scope-envelope Generation outcome is checked against declared expectations; the generation agent is budget- and autonomy-bounded

Chain integration (BR4). For every internal Mars® AI invocation governed by AIGP, the AIGP admission witness is prepended to that operation’s §02a §5a.2 witness chain as a pre-invocation link (§02e §5.2), carrying its witness class per §3.5. A Mars® conformance certificate whose derivation used AI internally therefore carries, within its recomputation witness (Field 7), the governed provenance of that AI use.

Non-circularity (BR5). Because the internal AI call’s admission is governed and recorded externally to the model, the Mars® verdict does not rest on the internal model’s self-assessment. This satisfies AR4 (no signal-required gap suppressed) and the broader prohibition on model-internal confidence as a gating signal at the level of Mars®’s own AI use, not merely at the level of the subject under analysis.

Scope-envelope as actuation bound (BR6). The autonomy_level of the generation agent (OBSERVE/SUGGEST/ACT_WITH_APPROVAL/ACT_AUTONOMOUS) constrains which §02c actuation classes the resulting artifact may drive. An artifact produced by an OBSERVE- or SUGGEST-level agent may not, without an intervening authority act, satisfy the downstream actuation gate for an autonomous effect.



← Mode 1 — analyzing AIGP-emitted data with Mars · Section index · What each side must provide for the bridge to be conformant →