1. Identify
Name the public surface and reliable observed state.
What this site monitors
The journal tracks five public surfaces: the public website, status page, status JSON endpoint, records archive, and contact guidance page. Internal jobs, editorial actions, and unpublished systems are not presented as public services.
How a record is published
2. Describe
State the visitor-facing impact in plain language.
3. Timestamp
Use an absolute UTC time with minute precision.
4. Resolve
Close the record only when the published state returns to normal.
5. Preserve
Keep the resolved record accessible in the archive.
Current state versus history
The status page answers whether a monitored surface is currently published as available. The uptime page shows the recent classification window. The incident page preserves exact event timing, impact, resolution, and follow-up.
Static publication boundary
Important scope
This is a published snapshot, not continuous telemetry
The static HTML and JSON files remain readable if client-side JavaScript is unavailable. A timestamp describes when the record was published; it is not automatically moved forward to imply a fresh check.
Data access
The same overall status and service naming used on the site is available in /status.json. Lightweight checks can use /health. Data format notes are documented on the data notes page.