Mission Control
v3.3.3.5-hf11 VM
Protocol telemetry and anchoring
Current Merkle Root
Suggested demo flow: Seed Demo DataAnchor Root to activate the ticker and viewer.
Evidence Throughput
Receipts
Anchors
Events
Leaves
Receipts are immutable, signed objects; Merkle roots batch receipts for anchoring & inclusion proofs.
Kill-Switch Status
Recovery is staged; re-enable requires negative tests + quorum approvals (demo simulated when backend lacks quorum).
Mission Brief
What the demo proves + a fast runbook (3D viewer lives only in the Viewer tab)
Integrity Guarantees
Signed receipts (Ed25519) → non‑repudiation
Merkle batching → tamper‑evidence + inclusion proofs
Anchor checkpoints → audit references (roots)
Encrypted payloads → proof without leaking sensitive content
Purge certificates → retention enforcement (auditable tombstones)
60‑Second Demo Flow
1) Seed Demo Data → create receipts for 3 rails
2) Rails → Healthcare → run a “Bad Claim” (policy refusal)
3) Run “Fixed Claim” → accepted → Anchor Root
4) Viewer → Merkle / Continuity → click node → Proof Inspector
5) Evidence → Quick Verify → signature + inclusion proof
Last Action
Last Receipt
Anchor Ticker
Clickable checkpoints (opens inspector)
No anchors yet. Click “Anchor Root”.
Auto Template Builder
One-click template generation to standardize payloads and accelerate demos.
Build Diagnostics
Deployment validation & runtime build metadata
Displays the active UI artifact served at /, the backend build identifier, and the availability of local /vendor/* dependencies used by the 3D viewer. Includes raw /api/build output for audit/debug capture.
Operational note: after deployments, a hard refresh may be required to clear cached assets.