Source proof
A feature exists in the current repository revision. Source presence alone does not prove deployment or successful runtime behavior.
Know what kind of proof you are looking at.
This page is a verification index. It explains source, test, preview, production, and runtime proof; it does not continuously probe uptime or guarantee every backend journey.
Home · Workspaces · Trust · Evidence
Automated verification
Syntax, contracts, browser tests, public-safety scans, and other checks can prove bounded behaviors at a specific revision.
Preview proof
A preview deployment can prove a candidate built and rendered in its preview environment. Preview is not production.
Production proof
A production deployment can prove a specific revision reached the public target. Hosting alone is not end-to-end workflow proof.
Runtime proof
Real requests, authenticated journeys, logs, or receipts are needed to verify behavior that depends on live services and user state.
Human-facing proof
Real-device, keyboard, screen-reader, mobile reflow, and interruption/recovery behavior require the appropriate human-facing QA evidence.
Current-page boundary
For current release status, inspect the exact repository revision, CI run, deployment metadata, and runtime evidence together. This page intentionally avoids hard-coded “online” badges that can become stale.