Public operations receipt

See how the monitor is doing.

A one-minute check cadence is only useful when the collection boundary is visible. This page separates collector freshness from source-content freshness, then exposes the timing measurements and limits behind the public signal.

All timestamps are shown in UTC. Private source addresses, credentials, and account telemetry are never published.

Live receipt

Loading

The latest collection state is not yet available.

Collection cadence—s

Independent server-side checks; your computer can be offline.

Last successful checkNot recorded

Age: —s. This is collection freshness, not source-change latency.

Source fetchHTTP —

— public items parsed in —ms.

Official public corroborationHTTP —

— accepted claims parsed in —ms.

A separate official public-account lane is shown as corroboration only; an empty claim set is not evidence that no reset exists.
Direct public laneHTTP —

— qualifying reset claims parsed in —ms.

The direct public interpretation is not recorded yet. Last direct check: Not recorded. Raw source content is not published.
Parallel X relayHTTP —

— qualifying reset claims parsed in —ms.

The parallel relay state is not recorded yet. Last relay check: Not recorded. This lane is not independent proof.
Source content freshness—s old

Newest accepted source item: Not recorded.

This is separate from the collector's last successful check.
Fastest qualifying lanePending

—ms fetch · — qualifying lanes.

A qualifying lane returned at least one accepted public item; this does not claim delivery latency.
Evidence coverageUnavailable

— corroborating · — context · no private telemetry.

Late corroboration retained— public events

Secondary public claims are saved after the primary lane finishes, without delaying the first signal.

Latest source time: Not recorded. Latest observation: Not recorded.
Source relationship— distinct origins

— independently verified · — community/corroborating.

Same-origin relays and unverified reports remain visible without upgrading the evidence state.
Observation ledger— measured

— baseline · — total source fingerprints.

A baseline is not a latency claim; measured rows require a new eligible source timestamp pair.
Email alert pathNot configured

Confirmation and confirmed-reset alerts share the guarded delivery path.

Runtime configuration is not available yet.
Measured source-to-observation timingNo qualifying event yet

Median Pending sample · p95 Pending sample · latest Pending sample.

Timing is recorded only when a new primary event has an explicit source time and first-observed time. Window: —s. Excluded: —.
Accepted source-set changes—

No accepted source-set change has been recorded in the current window.

A semantic fingerprint is kept private; only the public change result is exposed.
Boundary: A fresh monitor check proves collection health, not that every personal account has reset.
Verify a receiptShare an evidence cardIntegrate the public packet

What the receipt can prove

It can show that the collector is reachable, when its last successful check completed, what public items were parsed, and whether any accepted primary event has a recorded source-to-observation interval. It cannot prove that every Codex account changed, and a collection check is not a delivery SLA.

Use the same facts in a tool

For a dashboard or automation, use the JSON health receipt, the reliability report, the compact public packet, or the integration guide. The public endpoints are read-only and credential-free.