Post-2.0 reliability work needs one explicit roadmap item rather than an implied launch promise.
Scope:
- Rotating worker termination during activity execution.
- Bounded packet loss and latency injection between workers and the runtime.
- Deliberate clock drift.
- Concurrent double-lease injection across two workers.
- Multi-region and split-brain behavior.
Acceptance:
- The roadmap assigns the targeted chaos program to the 2.1 planning horizon and states that these cells are outside the 2.0 evidence envelope.
- Each future cell defines the user-visible invariant and the evidence needed to claim support.
- Multi-region and split-brain work remains deferred while the product targets single-region deployments.
- If the launch market changes to multi-region or high-availability buyers before stable 2.0, this item is reclassified as a release blocker and the operating-envelope claim is reviewed before launch.
Post-2.0 reliability work needs one explicit roadmap item rather than an implied launch promise.
Scope:
Acceptance: