Alpha status
A human-readable view of the public website, liveness and readiness endpoints, and agent-discovery surfaces. Uptime monitors should use /healthz; dependency monitors should use /api/public/health.
Current state
Public site online
This page avoids calling machine health endpoints during render so it remains useful even when a dependency check is degraded.
Public website
Published
alpha.ac
The public route surface is verified by SSR, link-header, asset, and screenshot smoke checks before deployment.
Machine health
Liveness + readiness
/healthz + /api/public/health
Use /healthz for SSR liveness and /api/public/health for Supabase-backed readiness. A readiness 503 means the website is reachable but a dependency needs attention.
Agent discovery
Published
alpha.ac
MCP, API catalog, llms.txt, Auth.md, DNS-AID, and readiness metadata are published from the canonical site.
Operational notes
What to fix next.
A 503 from /api/public/health means the SSR worker is reachable but one required dependency failed. The current known dependency risk is a stale or invalid Supabase service-role key in the production environment.
Supabase keys
Regenerate the service-role key for the active Supabase project, update the Vercel production variable, redeploy, and verify /api/public/health returns 200.
Terminal launch
Alpha Terminal is pre-launch. Keep terminal.alpha.ac unadvertised until a real deployment, DNS record, and access policy are ready.
Agent discovery
Keep MCP, API catalog, llms.txt, Auth.md, DNS-AID, and readiness metadata published from the canonical site.