Status at a glance
Show the public operational posture from the same coarse summary source used by the status service and KV latest cache.
PHASE 5F · PUBLIC-SAFE DASHBOARD PROTOTYPE
Operational cockpit without exposing the cockpit.
This page turns the live status summary and KV latest-cache work into a visible product surface while keeping private events, secrets, raw logs, quotas, and mutation controls out of the public site.
PUBLIC PRODUCT SURFACE
What Phase 5F makes usable
Phase 5F packages the previous infra work into a dashboard-shaped layer: readable status, webhook posture, data boundaries, and a clear path toward protected operations.
KV latest cache
Document the edge-readable latest status value without exposing private event streams or raw health data.
Webhook posture
Make the public boundary visible: HMAC-protected hooks, WAF blocking for unsigned webhook POSTs, and safe health-report summaries.
Protected cockpit gates
Define what must stay behind Access/auth before any future private dashboard, mutation controls, D1 history, or R2 archive is enabled.
DATA FLOW
One public signal, several future surfaces
The public dashboard prototype is intentionally static. It describes the safe read path now, and leaves future live binding to a protected Worker or dashboard after the auth model is approved.
status APIbuilds public summary
/summary.jsoncoarse public schema
KV latestedge-readable cache
/dashboardpublic-safe prototype
future cockpitAccess/auth required
BOUNDARY CHECK
What this page deliberately does not do
The prototype creates product clarity without expanding the attack surface. It does not expose private controls or internal operational material.
- Reads only public-safe concepts and links
- Keeps raw events, secrets, headers, and payloads out
- Leaves VPS, VPN_ZZ, Tunnel, DNS, and WAF untouched
- Requires Access/auth before private cockpit or mutation controls
- Requires separate authorization before D1 history or R2 archive