Platform status

Component status without leaking operational secrets.

This page publishes the platform-level status surface for outbound calling, database persistence, private recording archives, webhook processing, and recent incident communication.

Call execution runtime

Operator monitored

Outbound call execution runs through the platform adapter. Public status does not expose API keys, provider call IDs, raw payloads, or provider costs.

D1 database

Platform-owned

Call jobs, pricing snapshots, profile versions, credit ledger records, and normalized artifact state are stored as platform facts.

R2 recording archive

Private archive

Recordings are archived to private storage and served through authenticated platform download routes. R2 bucket names and object keys are not public API fields.

Webhook processing

Internal reconciliation

Inbound runtime events are verified and normalized for platform reconciliation. User outbound webhook delivery is not a public v1 capability.

Detailed health checks stay admin-only

Operators can run live checks for runtime reachability, webhook authentication, schema readiness, and recording archive writes from the admin settings page.

Recent platform incidents

Customer-visible incidents are published here at component level. Incident notes must describe user impact and recovery state without exposing provider raw payloads, internal identifiers, or storage paths.

Status is a publication boundary

This page is not the billing source of truth and does not replace call history, credit ledger entries, authenticated recording downloads, or admin-only provider diagnostics.