§02a Jupiter — Base Analysis — What this layer is
Mars® Spec › §02a Jupiter — Base Analysis › What this layer is
Section index · The governing ground truth →
Mars® Protocol — §02a: Base Analysis
Version 1.0-draft
1. What this layer is
The base analysis layer defines what formal analysis means within the Mars® architecture, and establishes the machinery by which an artifact is analyzed against a governing ground truth to produce a recomputable verdict.
Formal analysis, as defined here, is not any single method. It is a conjunction: analysis that is (a) order-governed, (b) performed by a composable battery of methods, (c) where any symbolic lift of linguistic material is bound back to its source for audit, (d) where divergence between a deterministic method family and a probabilistic method family — not within a single family — is recorded as a measurable signal, (e) where the result spans one or more orders, perspectives, and sources combinatorially, and (f) where every verdict is paired with a recomputation witness enabling independent re-derivation. Each individual method in the battery is prior art; same-kind ensembling and single-architecture hybrids are prior art; the load-bearing distinction is this conjunction.
Three independent specifications compose this layer, each independently deployable:
- The discrete-representation specification — forms the machine-evaluable representation substrate over which analysis is performed, including the intermediate representations (IRs) and multi-stage pipelines that produce it (§5, §5a)
- The analysis methods specification — governs the analytical battery applied over that substrate across three layers (pre-IR, IR-level, post-IR), producing a verdict and recomputation witness chain (§3, §5a)
- The analysis output specification — receives the battery’s results and produces the typed verdict, gap referrals, and analysis battery record consumed by §02b
This layer is the governed, auditable, self-completing analysis substrate on which all higher layers are built. It does not manage the conformance certificate, the delta-attestation lifecycle, the non-language boundary, or the pre-invocation phase — those are specified in §02b–§02e.
Dependencies. This layer consumes the formal domain model from §01 (Juno). Its outputs feed §02b (certification and attestation), §02c (non-language bridge), and §02e (AIGP and pre-invocation).