Snapshot of the live attest demo product — served from a local Ring emulator. Struck-through links and disabled controls are live-app routes. Run attest demo for the real thing; back to the demo page.
Attest.
Local / test data · configured summary provider: template
LOCAL REPLAY — not a live visit. Event clock: 2026-10-08T20:37:03.318922+00:00. Security expiry and signature issuance use real time.

Integrity posture

The runtime's own audit — the same checks attest status runs offline, rendered live (raw JSON for scripted checks). This page describes the evidence system's health, not whether any worker was honest.
✓ Self-audit passes — receipt chain and mutation journal both verify.

Receipt chain

✓ 447 receipts, chain intact across 1 signed key rotation
447 signed receipts · latest sequence #447

Mutation journal

✓ 931 entries, intact
452 signature-pinned heads · head 9b5eaef840dd…
4 newest entries not yet covered by a signed head — `attest anchor` pins them

Transparency log

✓ 134 signed checkpoint(s)
313 receipts in the Merkle tree · head 3e2c6c630814…
latest checkpoint rcpt_a5e4ebcc9a5… · Oct 15, 3:06 PM — covers 311 leaves
2 receipt(s) not yet covered by a checkpoint — attest checkpoint signs them in
Inclusion + consistency proofs at /api/log/* — attest monitor pins this head and catches a rewrite.
No witness pins yet — another deployment can ask this one to cosign via /api/witness/cosign.

Signing key

local key file — plaintext at rest
Issuer qRNo7hHrwwi2zNlV… · clock mode replay
Lineage 2 keys — retired via signed key_rotation/adoption pivots
⚠ 1 issuer key(s) revoked — 9 receipt(s) sit inside suspect windows (annotation, not erasure)

Delivery inbox

0 pending · 0 in flight · 0 failed
Failed deliveries are kept until requeued or explicitly purged via retention.

Webhook intake

✓ HMAC-verified — 3600s freshness window
Stale signed bodies and replays beyond the window are refused (401) even when the dedupe tombstone is gone.

Signed attestations on record

KindCountLatest issued
case export134Oct 15, 3:06 PM · receipt
coverage attestation2Oct 9, 11:45 AM · receipt
key adoption1Oct 9, 11:44 AM · receipt
key revocation1Oct 9, 11:45 AM · receipt
key rotation1Oct 9, 11:44 AM · receipt
late event1Oct 15, 6:18 AM · receipt
log checkpoint134Oct 15, 3:06 PM · receipt
pack comparison18Oct 15, 3:06 PM · receipt
pack verification10Oct 14, 4:46 PM · receipt
period digest1Oct 9, 11:06 AM · receipt
verification report1Oct 9, 11:06 AM · receipt
verifier manifest134Oct 15, 3:06 PM · receipt

Site-level chain events — the ledger's signed record of watching, summarizing, exporting, and consent.

Watching evidence per site

SitePoll observationsMost recent pollLatest lifecycle event
Alvarez residence 56 Oct 8, 12:36 PM subscription deactivated · Oct 4, 11:41 AM

Poll rows prove watching, not events — "we checked" is a different claim from "something happened". Lifecycle events are the channel's signed account of why observation stopped or resumed; an explained gap is still silence, not absence.

Store contents

Visits9 closed=7 no_observation=2
Evidence rows57
Reviews5
Late events retained2 arrived after close — kept for review, never silently dropped
Coverage events3 Ring lifecycle facts (offline/subscription/link) explaining gaps
Live-view sessions1 a stream was opened — records when and how long, never what it showed
Dedupe keys45
Grants8 6 check-in · 1 review · 1 family
What this page proves: the signed chain links, the mutation journal replays cleanly, and issued receipts pin the journal head at signing — a store edited outside the pipeline shows up here (receipts signed before pinning leave that one check uncovered). What it doesn't prove: physical attendance, identity, or time worked — those are the records' own claims boundary, unchanged.