Operational record · established 2026-08-06
Why this site exists.
The boring, load-bearing answer: so production can prove itself continuously, with a page that costs nothing and risks nothing.
Purpose
A production verification fixture for CivSites — a real, published site that turns "is production healthy?" into a measurable, alarmed yes.
What it exercises
DNS, TLS, CloudFront, WAF, cache policy, the site resolver, server-side rendering, and the public CMS API — the complete path a resident’s browser travels.
Data handling
No customer or resident content is stored here, ever. The authoring account is internal, and the generated hostname holds nothing sensitive.
Operational use
Release verification uses these pages for rendering spot-checks. The alarm pair — availability-low and latency-high — feeds the production alerts channel.
Cadence
Three probes, once a minute, indefinitely. The label 77c83208 is durable; bookmark it.
A safe place to look.
When production feels wrong, open this site first. If it loads fast and looks right, the serving path is healthy — and the search moves inward.