Resources

Pilot, verify and explain BOUNDA.

Use these resources to prepare the first boundary, explain the proof and brief internal buyers.

Sample Evidence Pack

Manifest, Unit Ledger, Consequence Graph, Proof Sufficiency, External Verify.

Client Pilot Kit

Selected boundary, data request checklist, timeline and success criteria.

Buyer Brief

CTO/CFO/Audit/Board language for the first Evidence Close.

App proof screenshots and JSON bindings

Command Center · Executive View

BREACHED — unit born after NO

Unit → Chain → Impact → Decision, Claim Authorization, Evidence Pack Ready.

JSON binding

BOUNDA_VERDICT.json → OneSentenceVerdict
CONSEQUENCE_UNIT_LEDGER_MAX.json → Reality Units
CONSEQUENCE_GRAPH.json → Chain view
PROOF_SUFFICIENCY.json → Claim Authorization
VERIFY_SEAL.json → External Verify

FAQ

Does BOUNDA replace observability?

No. Observability shows what happened. BOUNDA proves whether a rejected decision still created real units downstream.

What happens when receipts are missing?

BOUNDA returns UNKNOWN and blocks a clean claim.

Are PROXY units billable?

No. PROXY and UNKNOWN are never billed as measured reality.

Priority resources

Start with the proof object.

Sample Evidence Pack

Certificate, ledger, graph, manifest and verify command.

Client Pilot Kit

One boundary, two weeks, read-only receipts, one Evidence ZIP.

Proof of No Consequence

Rejected should mean zero downstream consequence.