Skip to content
Mars® Protocol

§02c Jupiter — Non-Language Bridge — What this layer covers

Mars® Spec › §02c Jupiter — Non-Language Bridge › What this layer covers

Section index · The non-language-provenance anchor (inbound boundary) →

Mars® Protocol — §02c: Non-Language Bridge

Version 1.0-draft

1. What this layer covers

This layer specifies the governed boundary machinery for moving between non-linguistic and linguistic representations in both directions:

  • Inbound boundary — the mechanism by which a non-linguistic engineering signal is lifted to a typed linguistic predicate, including the non-language-provenance anchor, the four-step bridge sequence, the downstream verification gate, and the NB1 enforcement constraint
  • Analysis of lifted artifacts — the §02a analysis battery (§02a §3) and battery execution discipline (§02a §3a) apply to lifted non-linguistic artifacts on the same terms as to any other artifact; this section specifies what is additional at the non-language boundary: the PV-gate anchor enforcement requirement, the R1 inbound constraint, and the R2 composition constraint
  • Outbound boundary — the mechanism by which a verified linguistic predicate authorizes a non-linguistic effect, including the actuation anchor, the downstream actuation gate, and the NB3–NB5 enforcement constraints
  • Named-authority standing — the registry and lifecycle for named human co-authorization
  • Scope-of-applicability certificates — single-link certificates, boundary-closure attestations, and N-hop composed certificates governing predicate re-use across domain boundaries
  • Interaction-protocol lift to order-typed form — the protocol-lift path for interaction-mediated targets whose internal IR is inaccessible
  • Bidirectional boundary closure — the structural requirement linking inbound and outbound boundaries

Dependencies. This layer depends on §01 (domain model — one or more, composable and independently operable; see §01 §1), §02a (base analysis and symbolic lift), and §02b (delta-attestation lifecycle and conformance certificate). The delta-attestation lifecycle (§02b §5) governs the amendment lifecycle for all registered artifacts this layer references. The conformance certificate (§02b §2) is consumed at the outbound boundary’s actuation anchor Field 1. Where multiple domain models are active, each carries its own registered artifact identity; anchors, certificates, and cascade records are scoped to the domain model version under which they were produced.

Section index · The non-language-provenance anchor (inbound boundary) →