Reliability
The system doing what it's supposed to, consistently — related to but distinct from availability (a system can be 'up' but returning wrong data).
Why we need this / what value this brings
Uptime alone doesn't guarantee correctness — a 'reliable' system does the right thing consistently, not just responds.
When to use this
When defining what 'working' actually means for a critical flow (e.g. booking), beyond just 'the server responded'.
How to use or implement this
Write SLOs against business-meaningful outcomes (booking successfully created and confirmed), not just HTTP 200 rates.
Research questions
- What SLOs would define 'reliable' for Localz's booking flow specifically?
Empty folder — drop notes, links, and findings here as you research.