Coverage report
01Overview
What dormouse watched, what happened, and what was delivered in this window. Click a card to jump to its section.
02Coverage by source
How often each source was checked and how the actual cadence compares to the promised one. A dash under coverage means the source joined the watch too recently to owe a full cycle. The CSV export carries the full per-outcome breakdown.
| Source | Checks | Success | Coverage | Longest gap | Status |
|---|
03Meaningful changes
Everything that changed and mattered, newest first. Classified changes carry a severity and a one-sentence summary; the rest show exactly what appeared and what fell off the page.
04Watchdog events
Staleness alerts raised when a source went too long without a successful check. Silence is a coverage gap, so dormouse treats it as a finding, not an absence.
05Integrity proof
This report is only as good as the record behind it. Dormouse stores every fetched page addressed by the hash of its content, and chains every check to the one before it, so a rewritten or deleted entry breaks the chain and is detected. The sweep below ran at generation time against the full history, not just this window.
How to verify this independently
Each audit-trail entry stores a SHA-256 hash over its own fields joined to the previous entry's hash. Recomputing the chain from the first entry must reproduce the chain head shown above. Any altered, inserted, or deleted entry changes every hash after it. Snapshots are addressed by the SHA-256 of their content, so the stored copy of any page version can be re-hashed and compared. The verification tooling ships with the dormouse engine as the verify command.