Skip to main content

SLO/SLA Targets

Objective: Define non-functional requirements (availability, latency, freshness) for core services (C2-01 … C2-12). Note: SLO = target objective; SLA = contractual guarantee (applies to public APIs only). This document ensures operational reliability and performance transparency across all service domains.


C2-IDServiceMetricTargetWindowNotes
C2-11Public API Gatewayp95 latency (read)≤ 200 ms30dEdge cache allowed
C2-11Public API Gatewayavailability≥ 99.95%30dMulti-region setup
C2-02Proof of Contribution (PoC)ingest p95≤ 300 ms30dIdempotent POST
C2-02PoCevent durability99.999%30dAt-least-once delivery + deduplication
C2-01Resonancebatch compute≤ 5 minhourlySliding window recompute
C2-07Metricsdashboard freshness≤ 60 s lagrealtimeStreaming preferred
C2-03Governancevote record p95≤ 400 ms30dSigned, append-only
C2-04Treasurypayout creation p95≤ 500 ms30dExcludes on-chain latency
C2-05Identity (PoCI)verification p95≤ 300 ms30dCached verifiable proofs
C2-06HubsCRDT sync convergence≤ 5 s95thUnder normal connectivity
C2-08Ethicspreflight evaluation p95≤ 800 ms30dModel cache enabled
C2-10Securityincident alerting≤ 60 srealtimeSIEM → PagerDuty
C2-12Resonance Board / UITTFB≤ 150 ms30dCDN + SSR enabled
  • Error Budgets: 1−SLO per window; alert thresholds at 25%, 50%, and 75% burn.
  • Escalation: Pager rotation; 15-min acknowledgment; 1h mitigation for Sev-1 incidents.
  • Monitoring: Prometheus + OpenTelemetry traces; public status page for SLA-bound endpoints.

Prepared by: the coherosphere collective