Magenta Canon — Evidence Viewer
A read-only view over the public trust endpoints. Nothing here is taken on trust — verify it yourself below.
Hosted evidence vs sample evidence
This page is the live hosted evidence surface. It reflects the current in-memory state of the public evaluation instance, which is ephemeral — it may be empty and it can reset on restart (see the durability badge below). An empty hosted view does not invalidate the proof: the reproducible sample evidence bundle is committed to the repository and drives the proof walkthrough, so a stable artifact is always available to verify — independent of this hosted instance.
See also: /proof · /claims-register.json · /trust.
Deployment
Witness — latest signed tree head
The witness signs a Merkle tree head over every recorded decision. consistent means the tree size equals the receipt count — a gap would signal a witnessing fault.
Recent agent-action receipts
Loading…
| # | action | timestamp (UTC) | receipt_hash |
|---|
Each receipt binds its decision and parameters as cryptographic hashes
(decision_hash, action_hash). Both allowed and blocked actions are
recorded. The human-readable per-decision detail — ALLOWED / BLOCKED, the reason,
the amount — is bound but not yet rendered here: surfacing it from the evidence is the
DecisionRecord roadmap (see docs/demos/FINTECH_REFUND_DEMO.md). What enforces
today is the delegated capability / amount-ceiling gate; the operator-policy layer (tiered review,
policy versioning) is roadmap, built with a design partner.
Verify it yourself
Download the exact evidence bundle and check it with the standalone verifier — which imports nothing from this server and makes no calls to it.
From a granted private checkout of the repository, run the standalone verifier:
Loading…
Expected: INTEGRITY VERIFIED — the bundle is internally consistent and its signed tree head checks out under the key carried in the bundle. Tamper with one byte of the bundle and it returns VERIFICATION FAILED. Spec: docs/MAGENTA_VERIFICATION_SPEC.md.
Origin assurance is a separate, stronger claim — and this page cannot establish it for you.
The check above proves the bundle has not been altered. It does not prove which
deployment produced it. Origin assurance requires the witness public key obtained through an
independent trusted channel — not from this server — and then pinned:
--expected-witness-key <independently-obtained-key>, which upgrades the verifier result to
ORIGIN AND INTEGRITY VERIFIED. The key shown under Witness above is
observed data displayed by this instance, not an independent trust anchor: a server
serving a forged bundle could serve a matching key. Pinning a key this page handed you proves only
that this instance is consistent with itself.