The checkpoint is saved only in this browser until you clear or export it.
Inspect what a forward cursor can and cannot show.
Request an anonymous public event window, review continuity signals and keep an opaque checkpoint in this browser. The lab exercises polling and resume semantics; it is not an outbound webhook product.
Requests run only after an explicit inspect or resume action. No endpoint receives pushed events.
The feed contains already-public evidence records, not raw scans or operational source diagnostics.
Move the cursor only after reviewing the window.
Start from the current public window or resume from a checkpoint previously saved in this browser. Requests are never retried automatically.
No automatic fetch, retry, polling interval or push delivery runs from this page.
No feed request has run.
No event window has been requested.
Inspect the current window to establish an observation, or import a valid checkpoint below and explicitly resume from its opaque cursor.
No checkpoint content is sent anywhere. Only its opaque cursor is used when you explicitly choose resume.
Four explicit steps from inspection to resume.
The sequence keeps local observation, checkpoint storage and the next feed request distinguishable.
- 01Inspect
Request the current public window without a cursor. No request runs on page load.
- 02Review findings
Check event identity, ordering, duplicates and initial-window truncation before moving the cursor.
- 03Checkpoint
Save the returned opaque cursor in this browser or export the checkpoint JSON for your own records.
- 04Resume
Explicitly poll from the saved cursor and compare the resumed window with the local checkpoint.
A local continuity report is bounded evidence.
A clean local report is not proof of exhaustive monitoring, network delivery, endpoint identity or legal/compliance status. The public cursor can expose duplicates, ordering regressions and a truncated initial window; it cannot prove that every external policy update exists.
- No endpoint registration, webhook subscription, push delivery or delivery receipt
- No automatic retry processing or server-side replay store
- No server-side checkpoint storage
- Endpoint identity, tenant workspace or signing-key management
- Monitoring coverage, network delivery or service-level commitments