Autoscaling Controller  ·  View 16 of 37  ·  3 · Data

Durability and Retention

The contract each store signs, side by side.

Editable source SVG draw.io All views
Consistency Replication and RPO Recovery Retention Target and policy registry Strongly consistent transactional Zone-redundant sync RPO 0 RTO under 60 s Current + full history Desired-state record Strongly consistent the truth Synchronous replica RPO 0 RTO under 60 s read SLO 99.95% Current + 30 days transitions Signal store Eventually consistent loss tolerant Replicated blocks RPO 5 min Rebuildable control unaffected 15 d raw · 13 mo rollup Decision journal Append only immutable Buffered transport RPO 60 s RTO 15 min not on control path 13 months WORM copy Audit log Append only tamper evident Signed batches RPO 60 s RTO 15 min 13 months Durability and Retention by Store The two authoritative stores carry RPO 0 because losing them loses control. The two derived stores are allowed to lose minutes because losing them only loses explanation. v 1.0 · owner Data & AI Global Practice · date 2026-09

The rule

  • RPO 0 for the two stores whose loss is loss of control. Minutes of RPO for the two whose loss is loss of explanation.
  • The desired-state record carries the highest read availability target in the system — 99.95% — because actuation continues from it while the decision engine is down.

Stated assumptions

  • Control plane availability ≥ 99.9% monthly; desired-state read availability ≥ 99.95% monthly.
  • Signal store RPO ≤ 5 min, journal RPO ≤ 60 s, both invented and both open to argument.
  • 15 days raw at 10 s and 13 months at 5 min rollup is sized for a year-on-year seasonal comparison, which is the only use that needs 13 months.

What this permits

  • Losing the whole signal store is a fail-static event, not an outage: no scale-in while blind, and the fleet keeps serving.