Operational Status

Status and incident visibility for policy ops.

Public snapshot of runtime readiness, metrics ingestion, and incident communication paths for decide. This page is refreshed from live endpoints and protects restricted internal counters.

Availability metrics on this page are monitor-scoped telemetry for listed endpoints and are not a contractual SLA statement.

Last updated: March 4, 2026 (UTC). Source links: /api/runtime-config, /api/metrics, /api/uptime, /api/compliance-export?format=json.

View compliance JSON Report an incident

Live service snapshot

Status checks are sourced from /api/runtime-config and /api/metrics. Some metrics remain token-gated by design.

Runtime config

Checking

Loading runtime readiness and blocker state.

Metrics ingest

Checking

Loading metrics endpoint status.

Incident channel

Active

For urgent issues, email [email protected] with subject security incident or runtime incident.

Last checked: pending.

Public Monitor Suite

External monitor coverage for public decide endpoints, sourced from UptimeRobot monitor status.

Interpretation rule: monitor status reflects configured probe behavior for each endpoint, not full-system guarantees beyond published runtime scope.

Primary runtime monitor (UptimeRobot)

Checking

Loading uptime monitor ratios.

Last 24 hours --

--

Loading monitor suite.

Monitor Status Interval 30d uptime 90d uptime Endpoint
Loading monitor suite.

A healthy suite should show all key runtime and notary endpoints as Up. Uptime windows reflect trailing 30d and 90d ratios.

Readiness breakdown

Signal Current value Interpretation
Commercial readiness Pending Derived from configured intake, checkout, alerting, and confirmation channels.
Active blockers Pending Non-empty blocker list indicates rollout follow-up is required.
Metrics endpoint mode Pending Public view may be limited while full counters remain token protected.
Metrics update timestamp Pending Fresh timestamps indicate event ingestion is active.
Uptime ratios (30d / 90d / all-time) Pending Sourced from UptimeRobot monitor-specific API telemetry.
Estimated downtime (90d) Pending Derived from 90-day uptime ratio.

Compliance export

Download the latest compliance CSV from /api/compliance-export and inspect JSON summary data from /api/compliance-export?format=json.

Endpoint health

Checking

Loading compliance export summary.

Snapshot details

  • Generated atPending
  • Record countPending
  • SourcePending
  • WindowPending
  • request_idPending
  • Top-level fieldsPending

JSON preview

Pending.

Incident response policy

Communication path

Customer-facing updates use [email protected]. High-priority incidents are acknowledged with request_id-linked context for follow-up.

Escalation trigger

Delivery failures and readiness blockers trigger immediate operator review and retry/route fallback workflows.

Public transparency

This page reflects current operational mode and whether observed issues are blocking commercial rollout.