Public proof boundary

What is verified, and what is still waiting.

This page explains the current proof state for Mullusi and Mullu in plain terms. The website and product pages are published. Runtime/API service evidence remains AwaitingEvidence until signed witness endpoints publish.

See current status View Mullu Govern Contact Mullusi
Plain meaning

AwaitingEvidence means waiting for named proof.

It does not mean the product direction is rejected, broken, or cancelled. It means Mullusi will not claim a runtime service, customer access path, or proof stamp until the required witness endpoints are signed, reachable, and validated.

Decision summary

Published pages are available. Product services are not verified.

Website surface Published

The public website and linked routes are available.

Product boundary Published

Mullu Govern is described as the current public product path.

Runtime witness AwaitingEvidence

Health, gateway, and conformance witnesses are not closed.

Next action Signed endpoints

Product-service claims require reachable witness endpoints.

Reading guide

Read proof by claim, evidence, boundary, and gate.

Each proof block separates a published public surface from product-service evidence that still needs closure.

01

Claim

What the public page says is available, published, reserved, draft, or AwaitingEvidence.

02

Evidence

The record, route, registry, or witness that supports the current state.

03

Boundary

The exact line a visitor should not read past, including runtime and service limits.

04

Gate

The evidence condition required before the claim can move to a stronger state.

Current public evidence lanes.

Published

Website

The public Mullusi website and linked public routes are published and available.

Published

Product pages

Mullusi is the company umbrella. Mullu Govern is the current public product route 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.