Skip to content

§02e Appendix — AIGP↔Mars Bridge — What each side must provide for the bridge to be conformant

Mars® Spec§02e Appendix — AIGP↔Mars Bridge › What each side must provide for the bridge to be conformant

← Mode 2 — AIGP underpinning Mars’s AI initiatives · Section index · Externally-observable properties (bridge series) →

5. What each side must provide for the bridge to be conformant

5.1 Mars® side

  • Register the AIGP source with an accurate source-class decomposition (§3.1) and witness-class declaration honoring BR-H (§3.5).
  • Order-type or disambiguate AIGP order-agnostic signals before IR-level consumption (§3.4).
  • Record pre-invocation-cross-phase divergence for every co-evaluated question (§3.7).
  • Prepend AIGP admission witnesses as pre-invocation chain links for Mode-2 internal calls (§4, BR4).

5.2 AIGP side

  • Emit RECORD/TRACE with content hashes sufficient for W2 (already satisfied by RFC-009 §5.3).
  • For any signal AIGP wishes Mars® to treat as W1, emit a derivation trace sufficient for independent re-derivation from the order-typed input and the policy/spec version — not merely an HMAC/D-DNA signature. Absent this, the signal is W2/W3 and is annotated as such (BR-H).
  • Declare governance mode (ENFORCE vs REPORT) in emitted evidence so Mars® can apply the correct absence posture (§3.6).
  • Reference Mars® as the declared post-invocation consumer of AIGP evidence (reciprocal pointer; see the AIGP repository reference).


← Mode 2 — AIGP underpinning Mars’s AI initiatives · Section index · Externally-observable properties (bridge series) →