Operational health signals need promise relevance.
SRE
Praxis for SRE
Reliability is not only uptime; it is whether the promise survives pressure.
Start in the practice language people already use. Then use Praxis to distinguish the signal from the promise, the carrier from the capability, and proof from the status label.
Diagnostic move
Translate the practice into promise work.
A service may be available while the sync promise people rely on is stale or unverifiable. Praxis connects operational signals to the promise they are supposed to witness, then asks what repair restores the relying person's world.
The question is not whether the familiar artifact exists. The question is whether that artifact witnesses the promise people actually rely on.
- Signal
- The label, state, event, journey step, or metric that says something happened.
- Promise
- What someone treats as true because the product signaled it.
- Carrier
- Where, through whom, or through what the promise was encountered.
- Proof
- Evidence that would matter to the relying person, not only the internal system.
- Repair
- The owner and path when the promise cannot hold.
Translation
How Praxis enters this practice.
Incidents should name the relied-upon promise that failed.
Repair means restoring the promise, not only the component.
Signals to inspect
Start with one label.
available
processed
synced
resolved
Worksheet
Keep the review concrete.
Download the worksheet, choose one signal, and write the proof and repair path before discussing the theory.