§02e Appendix — AIGP↔Mars Bridge — The boundary, restated in AIGP terms
Mars® Spec › §02e Appendix — AIGP↔Mars Bridge › The boundary, restated in AIGP terms
← What this appendix covers · Section index · Mode 1 — analyzing AIGP-emitted data with Mars →
2. The boundary, restated in AIGP terms
§02e §2 fixes the pre/post-invocation boundary structurally: it is the point at which the model produces its output, not a clock time or a network hop. AIGP’s 17 governance stages (RFC-009 §5.3.3) straddle this boundary at a determinate point:
| AIGP stage | stage_name |
Side of boundary |
|---|---|---|
| 1–8 | identity, consent, registration, prompt submission/assembly, context authorization/retrieval, model selection | Pre-invocation |
| 9 | runtime_invocation |
The invocation itself — model executes |
| 10–11 | tool/agent authorization, intermediate reasoning | In-invocation (agentic) |
| 12 | output_generation |
The structural boundary — output is produced here |
| 13 | output_release |
First post-boundary act |
| 14 | post_invocation_record |
The Mode-1 handoff point — RECORD is emitted |
| 15–17 | persistence/memory, observation/audit, reflection/optimization | Post-invocation |
Everything at or before stage 12 (output generation) is pre-invocation with respect to the Mars® boundary contract — that is, it is upstream of the artifacts Mars® receives at the handoff. It is not a claim that Mars® is inactive during stages 9–12: stages 10–11 are in-invocation, and Mars® establishes the governed runtime across them, measuring and conforming the invocation as it proceeds (§02e §2, incremental validation). Stage 14 (post_invocation_record) is the canonical point at which AIGP-emitted evidence becomes available for Mars® ingest. Stages 15–17 are AIGP’s own post-invocation acts and are not part of the Mars® boundary contract; where they emit further evidence, it enters Mars® under the same Mode-1 rules as RECORD.
← What this appendix covers · Section index · Mode 1 — analyzing AIGP-emitted data with Mars →