§02e Jupiter — AIGP & Pre-Invocation — Five architectural refusals (negative-space discipline)
Mars® Spec › §02e Jupiter — AIGP & Pre-Invocation › Five architectural refusals (negative-space discipline)
← Operating Mars® with AIGP: the full governed round-trip · Section index · Cross-layer dependencies →
13. Five architectural refusals (negative-space discipline)
The following five refusals define the negative space of this architecture — behaviors the architecture structurally excludes. They are co-present: no one refusal alone constitutes the architecture; their co-presence is the structural discipline.
AR1 — No unregistered pre-invocation signal admitted as battery input. A signal from a source not registered in the pre-invocation signal registry (§3) may not contribute to the IR, the verdict, or the witness chain. It may appear in Field 6 as an out-of-scope observation. Admission of an unregistered signal as a battery input is a structural violation detectable without internal inspection.
AR2 — No W1 claim without satisfying the full recomputation-witness requirement. A source may not claim W1 witness class unless an independent inspector can re-derive the signal value from the order-typed input and the governing-specification version without executing the original system. This is a structural test. No source-identity exemption from this test is admitted — not for AIGP-branded systems, not for named authorities, not for any other source.
AR3 — No asserted pre-invocation coverage without chain evidence. A certificate may not claim pre-invocation evaluation in its certified scope (Field 5) without pre-invocation signal links in the witness chain (Field 7) corresponding to the claimed coverage. Claiming pre-invocation coverage without chain evidence is a false-grounding condition at Field 4.
AR4 — No signal-required gap suppressed. Where a source’s absence posture is signal-required and no signal is received, the battery may not issue a conforming verdict. The gap referral must be present and open. Suppressing a signal-required gap referral and issuing a conforming verdict is a structural violation.
AR5 — No cross-phase corroboration claimed without both conditions satisfied. A pre-invocation-cross-phase corroboration entry may not appear in the analysis battery record unless both conditions in §6 are independently satisfied: a registered W1/W2 deterministic source evaluated the input, and a probabilistic battery method evaluated the same conformance question under the same predicates. A pre-invocation-cross-phase entry that cannot be grounded in both conditions is a false grounding at Field 4.
← Operating Mars® with AIGP: the full governed round-trip · Section index · Cross-layer dependencies →