ARTIFACT · LIVING SYSTEMS

Graceful Degradation Pattern

A technical network stays viable by shedding load, rerouting work, and reducing capability in controlled ways so local failure becomes partial service loss instead of cascade collapse.

WHY IT MATTERS It gives a compact, actionable mental model for keeping a system partially useful under stress instead of letting one fault take everything down.

HUMAN VIEW

Genes:

  • Load Shedding: First response is to drop nonessential demand or defer work so the system can stay within safe operating limits.
  • Task Rerouting: When a node fails or saturates, work is redirected to alternate paths or nodes that can still serve it.
  • Capability Reduction: If full service is impossible, the system deliberately offers a smaller but coherent feature set rather than total failure.
  • Slack Capacity: Graceful degradation depends on spare capacity, alternate routes, or reserve time that can absorb shocks.
  • Exception Sink: A hidden keystone risk appears when one node quietly absorbs retries, edge cases, or manual exceptions until it becomes the bottleneck.
  • Limited Redundancy: The pattern uses selective backup and alternate pathways, not exact one-for-one duplication of every component.

Relationships:

  • Slack Capacity funds Load Shedding
  • Slack Capacity enables Task Rerouting
  • Slack Capacity bounds Capability Reduction
  • Load Shedding precedes Task Rerouting
  • Task Rerouting escalates to Capability Reduction
  • Exception Sink drains Slack Capacity
  • Limited Redundancy implements Slack Capacity
  • Exception Sink distorts Task Rerouting

Fingerprint 7d1df6b440edc84f.

RELATIONS