Your key, your browser
One credential: the API key. It goes to the mend.rest API through a same-origin pass-through and nowhere else, and this site keeps nothing. No key yet?
Task
Read from mend.status, mend.events and mend.report. Every field below is the service's own; this page adds colour and nothing else.
Receipts river
Every recorded event in sequence order. The pip between two cards is the sequence link: solid where the two events are consecutive, amber and named where they are not. Each card's declared digest is recomputed in this page and the result is reported honestly, including when this page cannot do the arithmetic.
Report
The deterministic fact projection, and the limits the service itself attaches to it.
Service
What the instance says about itself, from GET /healthz and mend.discovery.
- It verifies no signature cryptography. It renders what the service returned. Cryptographic verification is the offline verifier's job — see Verify.
- Its digest re-computation is a consistency check, not an attestation. A mismatch is drawn amber, never red: this page's JSON canonicalization can legitimately differ from the service's, and a difference it cannot attribute is an unknown, not an accusation.
- An error of observation is amber. A refused credential, a timeout, an unreachable service — these mean we could not learn. Red is reserved for a verdict of refutation about the work itself.
- It shows only what the handle you supplied returns. Absence of an event is unobserved, not didn't-happen.
- It stores nothing: no server-side session, no report cache, no credential, no analytics, no third-party request of any kind. The key is held in this tab and only mirrored into sessionStorage if you ask.