Define eligible checkout attempts and successful completion
Availability reports count health checks as customer success.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- SLI design
Estimated field mix
- Site reliability100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional checkout service reports process uptime while customers experience failed orders and slow confirmations.
Setup prerequisites
- Create synthetic request and order-event traces plus a local query or metrics fixture; no production telemetry required.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Define eligible attempts and completion deadlines.
- Exclude synthetic probes from customer denominators.
- Document validation failures and abandoned checkouts separately.
Implementation constraints
- Do not exclude service failures to improve the ratio.
Verification to include
- Classify representative success and failure traces.
- Reject a denominator that includes only completed orders.
Deliverables
- SLI event contract.
Rollout and recovery
Review event semantics before publishing an objective.
Value of the work
For the engineer: Practice SLI semantics, alert evaluation, and reliability tradeoffs.
For the team: Align reliability discussions with customer outcomes and explicit measurement limits.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.