Failure Contract Drill

Failure Contract Drill

animation
edge-fog

Failure Contract Drill

For one critical workload, name the degraded states before the design review ends: slow, unreachable, stale, overloaded, compromised, and updating. A named failure mode can become a bounded design. An unnamed failure mode becomes an outage.

flowchart LR
  Workload[Choose critical workload] --> States[Name slow, unreachable, stale, overloaded, compromised, updating]
  States --> Owner[Assign owner and local fallback]
  Owner --> Limits[Set bounds, timers, priorities, and evidence]
  Limits --> Fault[Test by disconnecting, delaying, overloading, and updating tiers]
  Fault --> Observe[Check alarms, buffers, timestamps, and recovery behavior]
  Observe --> Revise[Revise contract before field release]

Note

Paper ownership is not enough. Run the drill with cables unplugged, clocks skewed, queues filled, and updates interrupted so the contract proves what operators will see.

Data Path

How readings, events, batches, summaries, and retained evidence move when links are healthy and when links fail.

Control Path

Which tier can command actuators, reject unsafe states, or make local decisions without waiting upstream.

Management Path

How devices receive configuration, credentials, firmware, container updates, and rollback instructions.

Failure Path

What the system does during gateway failure, cloud disconnection, clock drift, overload, or partial rollout.

Back to the chapter