distributed-failure-cataloguelisted

# Distributed Failure Catalogue ## Purpose Turn a symptom into a name, and a name into the skill that owns the fix. Distributed failures recur in a small number of shapes; an engineer who can name the shape reaches the right mechanism in minutes instead of rediscovering it during an incident. This skill deliberately **does not teach the fixes**. Every entry ends at an owner, because a catalogue that also explained the remedies would drift out of step with the skills that own them. Destructive cleanup is the explicit exception, with bounded guard guidance below. Its value is recognition and routing — and, for a design review, a list of concrete failures to argue a design against rather than a general appeal to robustness. ## Workflow This is a protocol/operations catalogue, with no Java language minimum. The scheduled-task reference uses the Java 25 API documentation for a long-standing contract. Inspect the target runtime, scheduler/framework, client retry defaults and deployment configuration before applying version-sensitive claims; this skill does not authorize upgrades or fault injection. Reuse the incident record, accepted service contract and known owner before collecting more evidence. During an outage, bound classification by the response time available and hand off to the authorized incident owner/runbook without delaying containment for a complete catalogue walk. Carry the evidence, unresolved discriminator and remaining time into that handoff. 1. **Write dow