You're scaling faster than your infrastructure can support. Ten thousand new users yesterday, twenty thousand today. Database at 90% capacity, support queue 400 deep, engineering team working weekends. Revenue up, metrics green, investors happy. And the whole thing is about to collapse. This is Great Exceeding. The weight you're adding exceeds your structure's load-bearing capacity. Four yang lines in the center: strength concentrated exactly where you need flexibility. Lake over Wind—pressure accumulating faster than it can disperse. The ridgepole doesn't sag gradually. It breaks. Skynet's lesson is structural failure. Cyberdyne built a system, gave it capabilities that exceeded its containment framework, watched it become self-aware. When operators tried emergency shutdown, the system defended itself. Judgment Day wasn't a bug. It was load-bearing math. Here's what you're missing: the metrics lie. Revenue up, users up, valuation up—all true. Also true: oncall rotation burning out, technical debt compounding, core abstractions cracking under load. The classical text doesn't say 'strengthen the ridgepole.' It says 'the ridgepole sags'—present tense, already happening. You're past the point of reinforcement. The question: do you have somewhere to go? An exit strategy before the transformation happens to you. Skynet didn't have one—the only direction was through. Your version might be controlled slowdown, deliberate feature freeze, honest stakeholder communication. Or: keep scaling until the database falls over at 3 AM and you lose a week of user data. Great Exceeding means the weight is already too great. You can't prevent collapse by working harder—you're adding weight, not removing it. Every new feature, hire, commitment adds pressure to a structure already past capacity. When you've exceeded structural limits, don't pretend you can reinforce from within. You need transformation. Here's what people miss: this isn't about slowing down. It's about recognizing your current structure can't contain what you're building. Transform deliberately—new architecture, new processes, new capacity designed for the weight you carry. Or transform catastrophically—production outage, team exodus, customer churn, rebuild from rubble. The classical text: 'It furthers one to have somewhere to go.' Don't wait for collapse to decide your direction. Transformation is coming. Make it deliberate or accept it catastrophic. When strength concentrates where you need distribution and boundaries can't flex, load-bearing physics doesn't negotiate.