Fallback compute is supposed to distribute risk. In practice, too much of the emergency load still collapses onto Ring Two.
The reason is partly historical. Ring Two earned early trust for graceful recovery and stable thermal discipline, so later contingency logic kept selecting it as the safest destination for overflow. That worked until the redundancy layer began to inherit the same concentration pattern it was meant to prevent.
This is not a collapse of continuity planning, but it is a warning about how resilience narratives become self-defeating. A fallback target that succeeds too often becomes an operational habit, and an operational habit eventually becomes a single point of strategic expectation.