Skip to content
Mars® Protocol

§02c Jupiter — Non-Language Bridge — Bidirectional boundary closure

Mars® Spec › §02c Jupiter — Non-Language Bridge › Bidirectional boundary closure

← The actuation anchor (outbound boundary) · Section index · Outbound enforcement constraints (NB3, NB4, NB5) →

5. Bidirectional boundary closure

The non-language-provenance anchor (§2) and the actuation anchor (§4) together constitute bidirectional boundary closure. A deployment that implements the inbound boundary without the outbound boundary does not achieve bidirectional closure.

Closure requirement. Any deployment governed by this specification that routes certified outputs to non-linguistic effects must implement both the inbound boundary (§2) and the outbound boundary (§4). A deployment that processes inbound non-linguistic signals through the non-language-provenance anchor but routes certified outputs to non-linguistic effects without an actuation anchor is a structurally incomplete deployment. The structural incompleteness must be declared in the governing specification and reflected in the scope of every conformance certificate issued under that deployment.

A deployment that never routes certified outputs to non-linguistic effects — one whose certified outputs are consumed solely by human-facing presentation, logging, or further linguistic processing — is not required to implement the outbound boundary. The governing specification must declare which output classes are routed to non-linguistic effects.

← The actuation anchor (outbound boundary) · Section index · Outbound enforcement constraints (NB3, NB4, NB5) →