Landing, service, pricing, legal, support, and request-access pages are served from the Clarity domain.
Covered by public route tests, sitemap coverage, robots policy, and production build.System status
Clarity status should be public and easy to verify.
This page reports public service posture and the synthetic checks operators should retain before sending first-client traffic through the room.
Monitored components
Status is tied to launch evidence.
Components that depend on live Stripe, Supabase, R2, SMTP, or retained production evidence stay marked as monitoring until the target launch artifacts pass.
Deal Team, partner, investor, room selection, and document viewer paths are covered by regression checks.
Covered by role-routing, room-isolation, security, accessibility, mobile viewer, and watermark tests.Stripe Checkout, Customer Portal, webhook sync, failed-payment recovery, and webhook failure alerts exist in code.
Live card acceptance still requires retained Stripe catalog, webhook, schema, checkout, portal, and replay evidence.Private document upload, viewer access, storage-capacity gates, autoscale guardrails, and closeout evidence are implemented.
Production launch still requires target R2/Supabase evidence, representative corpus upload proof, and archive verification.Document digest, activity alert, invitation delivery, billing payment, and webhook failure notices retain delivery evidence.
Production launch still requires SMTP ownership, digest smoke evidence, and failed-delivery monitoring evidence.Launch command center, approval evidence, backup readiness, restore drill, retention, watermark, and closeout gates are in code.
Final launch status requires retained target-environment artifacts and owner approvals.Synthetic checks
What operators should monitor.
Public status JSON/api/statusHTTP 200 with no-store JSON and no secret valuesEvery 5 minutesPublic purchase path/pricingHTTP 200 and visible subscription, annual, room, and storage pricingEvery 10 minutesRole-aware login/auth/loginHTTP 200 and visible investor, partner, and Deal Team login lanesEvery 10 minutesReadiness gate/api/admin/security/readinessHTTP 401 externally, HTTP 200 for an authenticated admin evidence runBefore every release and daily during launchBilling webhook registrationnpm run billing:stripe-webhookRegistered, enabled, and subscribed Stripe webhook endpoint reportBefore accepting paid checkout trafficNotification deliverynpm run notification-digest:smokeDue digest run with zero failed deliveries unless an approved exception is retainedBefore launch and after SMTP changes