Operational Risk Review

When to use

• Preparing a service for production and want to know what breaks when a flow gets stuck
• After a dev-cycle: pressure-test the newly built flows for recovery gaps
• Incident retro: formalize which failure modes have a rescue path and which do not
• You need operational runbooks or a backlog of "missing rescue mechanism" gap specs

Skip when

• Prototype / throwaway PoC not heading to production
• Pure library or SDK with no integration boundaries (no external calls, queues, or webhooks)
• Single-question check (use a targeted read instead of the full review)

Related

Complementary: ring:auditing-production-readiness (broad readiness scoring), ring:mapping-service-resources (resource inventory), ring:running-dev-cycle (optional end-of-cycle hook)

What this produces

For every failure scenario, a tier and an actionable artifact: