Reliability Review

This is a Hermes-native reliability-review workflow skill.

Why This Exists

reliability-review exists because a reliability claim is cheap to write and expensive to check: it holds an SLO to its arithmetic and a postmortem to its structure, and keeps remediation separate from the review.

Do Not Use When

• The user only needs a generic status report or leadership deck.
• No service, incident, SLO, metric, or reliability source boundary is available.
• The request is implementation of remediation rather than review of reliability evidence.
• The incident is still open and the user needs severity declared, a commander assigned, a running timeline, and recovery verified; use omh-live-incident-response and review it once it is closed.
• The ask is a go or hold verdict before launch; use omh-production-audit.

Examples

Good example: