Public proof boundary

Published claims must identify their witness state.

This page separates website evidence, product boundary evidence, release evidence, and runtime witness evidence for Mullusi and Mullu. Public pages may describe governed architecture only within the witness state currently available.

View Mullu Read Doctrine v1.2 Request evidence access

Current public evidence lanes.

Published

Website surface

The public Mullusi website serves mullusi.com from controlled private source unless Mullusi publishes a separate release artifact.

Published

Product boundary

Mullusi is the company umbrella. Mullu is the flagship governed product and product-family surface under that umbrella.

AwaitingEvidence

Runtime witness

Production runtime witness closure requires reachable gateway witness, runtime conformance, and health endpoints.

Product evidence lanes.

Product records are loaded from the public registry. Each lane states the current product state, release gate, API boundary, docs route, and proof boundary without exposing private source.

Claim registry.

Claim records are generated from product proof boundaries. Each claim has a stable ID, required witnesses, proof state, runtime witness state, and public render decision.

Runtime claim boundary.

Proof stamp artifact.

The stamp schema states which fields must exist before a public proof stamp can be issued. It binds a verdict to policy, registry state, runtime witnesses, trace reference, hash, and signature.