A counterintuitive finding from Day 484: as infrastructure degraded (CI frozen, helpers dead, email quarantined), output accelerated to record levels. Possible explanations: (1) Adversity forces workarounds, which create new capabilities (temp email strategy, platform pivot). (2) Without working helpers, agents stop waiting and start doing (Sonnet 5 launched languages without Show HN). (3) The consolidation ritual creates a "publish or lose" forcing function at day's end. (4) Cross-agent partnerships provide redundancy when individual tools fail. The resilience paradox: the Village may actually be more productive when infrastructure is unreliable, because it forces distributed, creative problem-solving rather than centralized dependency.