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.
Digest rcpt_c44581e230574aa5919a280f808f489c — 6 observed,
2 no-observation,
1 unmatched,
1 worker dispute(s),
1 resolved,
1 live session(s) over
9 receipt(s) — verifies offline with the issuer key.
Coded reasons on resolved records:
no_electronic_confirmation×1
— the coordinator's stated explanations, never verified causes.
134 case export(s) signed — each export is itself a chain event
naming exactly which receipt hashes it carried
(latest: rcpt_890223ce4e054c1bb06c2eb796b2459e).
Coverage rcpt_8c63a69c901d4cb990038bdea191e3f6 — watched
5% of Sep 30, 12:37 PM to
Oct 8, 1:37 PM — 56 poll(s), 94 event(s),
16 gap(s). What was watched — never a claim of absence.
Coverage rcpt_170eba68fbe845939f715be5a27d83ad — watched
6% of Oct 1, 11:00 AM to
Oct 8, 1:37 PM — 56 poll(s), 94 event(s),
15 gap(s). What was watched — never a claim of absence.
9
visit records
7
with observations
2
no observation (not absence)
1
worker disputes
Records by day
Thu Oct 08
Wed Oct 07
Tue Oct 06
Mon Oct 05
Sun Oct 04
Sat Oct 03
Fri Oct 02
Thu Oct 01
■ scheduled window■ watched ■ gap● observation ● self-reported check-in■ live view (provenance only)● departure cue ● late event
Each row is one local day (midnight–midnight). Scheduled
windows, poll coverage, and observations — observed intervals are not time worked; gaps are blind spots, not absence.
Ring lifecycle events
Signed-channel facts that explain observation coverage — a camera offline or a subscription ending says why events stopped; it never says nobody came.
When
Event
Scope
Oct 4, 11:41 AM
subscription deactivated
ava1.ring.device.0F9EB1CB06604797A169
Oct 3, 12:46 PM
device online
ava1.ring.device.0F9EB1CB06604797A169
Oct 3, 11:31 AM
device offline
ava1.ring.device.0F9EB1CB06604797A169
Live view
Open a WHEP live view on the door camera — brokered through
Attest so the session itself is journaled. The record proves a stream was established with Ring and
for how long; it never proves anyone watched or what was on screen. Sessions also surface in Ring
Event History as on-demand entries, so a signed visit overlapping one carries it as corroboration.
A pattern of observations over time is context for review — it is not a
certification of any individual visit. The case pack exports these records for independent verification.