Skip to content

§02b Jupiter — Certification & Attestation — What this layer covers

Mars® Spec§02b Jupiter — Certification & Attestation › What this layer covers

Section index · The conformance certificate →

Mars® Protocol — §02b: Certification and Attestation

Version 1.0-draft


1. What this layer covers

This layer specifies four things:

  • The conformance certificate — the terminal artifact of governed analysis; a typed, cryptographically-signed integrity certificate satisfying nine structural invariants, produced from the verdict and recomputation witness supplied by §02a
  • The bounded-analysis record — a first-class registered artifact distinct from the conformance certificate, issued when the analysis question is irreducible under the available governing specification and the declared analysis battery; carries its own structurally-defined invariant set (analogous to, but distinct from, the conformance certificate’s structural invariants) and is treated by downstream gates as a non-passing result, not as a non-conforming verdict
  • The delta-attestation lifecycle — the foundational amendment-governance primitive for all registered artifacts in the Mars® architecture; governs how every registered artifact evolves over time, how that evolution is classified, and what cascade obligations that classification imposes on downstream artifacts and certificates
  • The deployment manifest — the versioned registered artifact that closes the open-variable gap across the architecture; declares, through a set of independently registered and delta-attested sub-records, the governing selector, KB selector, data source selector, battery selector, runtime configuration, and classification function in effect for a deployment; the version an inspector pins a certificate against

Dependencies. This layer depends on §01 (domain model — one or more, composable and independently operable; see §01 §1) and §02a (base analysis). Every other Jupiter section references this one for the delta-attestation lifecycle. The lifecycle is not a feature of the boundary machinery; it is the substrate on which the validity of every registered artifact rests. Where multiple domain models are active, each carries its own registered artifact identity and its own delta-attestation chain; they compose and co-exist without one invalidating the other.



Section index · The conformance certificate →