A Boeing E-3 Sentry AWACS aircraft, serial number 81-0005, sat parked at Prince Sultan Air Base in Saudi Arabia on March 27, 2026. By morning it was a charred skeleton. The aircraft itself was valued at roughly $300 to $500 million. Its replacement, the E-7 Wedgetail, will cost over $700 million. The attacker spent pocket change. This is not a story about drones. This is a story about what happens when the economics of attack and defense diverge by four orders of magnitude, and why every person building critical infrastructure, digital or physical, needs to internalize the math.
The Compression Trap
Here is the framework. I call it the Compression Trap, and it works like this.
When the cost to destroy an asset compresses toward zero while the cost to build and maintain that asset stays flat or rises, the defender enters a losing loop. Every dollar spent on protection buys less safety over time. Every dollar the attacker spends buys more destruction. The gap does not close. It widens.
Three variables define the trap. First, the Replacement Lag: how long it takes to rebuild what you lost. Second, the Production Asymmetry: Iran produces Shahed drones at industrial scale, exporting thousands in a single deal to Russia alone. The U.S. cannot produce a single new E-3. Third, the Defense Tax: Prince Sultan Air Base had Patriot batteries, fighter intercepts, and layered perimeter security. The March 27 salvo of 6 ballistic missiles and 29 drones overwhelmed all of it. Defending against cheap swarms costs more than launching them.
The Compression Trap is not unique to warfare. It shows up anywhere centralized, expensive systems face distributed, cheap disruptors. Think of a $200 million data center versus a $50 botnet attack. Think of a $10 million brand reputation versus a $0 deepfake. The pattern is identical.
The Asymmetric Flywheel Nobody Wants to Discuss
Let me pull from a concept I keep returning to: asymmetric advantage as a compounding force. In business strategy, we celebrate asymmetry when it favors us. Nvidia's CUDA moat. Costco's $1.50 hot dog as a loss leader that locks in membership revenue. Apple's ecosystem switching costs. These are asymmetric advantages that compound in the builder's favor.
But asymmetry compounds in both directions.
The Shahed-136 is a plywood-and-fiberglass airframe with a small engine and a GPS guidance unit. Iran builds them the way a factory builds furniture. No rare materials. No classified supply chain. No 18-month congressional appropriation cycle. The 2019 Houthi drone attack on Saudi Aramco's Abqaiq facility halted 5.7 million barrels per day of oil production, roughly half of Saudi output, using drones that cost a tiny fraction of the defenses they bypassed. That was the proof of concept. March 27, 2026, was the scaled deployment.
Now consider the defender's position through the lens of impermanence, a concept from Eastern philosophy (anicca in Pali, mujo in Japanese) that strategists ignore at their peril. Every complex system is impermanent. The E-3 Sentry entered service in the late 1970s. The airframes still flying are approaching 50 years old. The assumption that these assets would remain safe on the ground at a "hardened" base was not a calculated risk. It was institutional inertia dressed up as strategy.
I think the real lesson here is not about drones versus planes. It is about the mental model that treats expensive, centralized assets as inherently more capable than cheap, distributed ones. That mental model is breaking. The 70% rule for decision velocity applies: if you wait for 100% certainty that your centralized architecture is obsolete, you have already lost the asset.
Here is the contrarian view, and it deserves honest engagement. Admiral Brad Cooper, CENTCOM commander, reported in his March 25 briefing that precision strikes have degraded Iran's drone and missile launch rates by more than 90%. He linked this to the destruction of over two-thirds of Iran's missile, drone, and naval production facilities. The U.S. itself deployed low-cost one-way attack drones in Operation Epic Fury, reversing the asymmetry against Iranian targets. The AWACS was hit on the ground during a maintenance window, a tactical failure, not a structural inevitability.
These points are valid. It is unclear whether the March 27 strike represents a permanent shift or a one-time breach that better base dispersal and counter-drone systems will prevent. The U.S. retains overwhelming air superiority. After drone strikes hit RAF Akrotiri in Cyprus on March 2, Greece deployed frigates equipped with counter-drone systems and F-16 jets to bolster the island's defenses, while British warplanes scrambled to intercept additional incoming drones. The Western alliance is adapting.
But here is what the contrarian view misses. Even if you win the tactical exchange, the economic exchange still bleeds you. Shooting down a $20,000 drone with a $3 million Patriot interceptor is a "win" that costs you 150 times more than it costs your adversary. Deploying $100 million in layered base defenses to protect aircraft that should not be parked in the open is a tax on your entire force structure. The Compression Trap does not require the attacker to win every engagement. It only requires the attacker to make defense more expensive than the defender can sustain.
This is the same logic that governs cybersecurity economics. The attacker needs to find one vulnerability. The defender needs to cover all of them. The cost curves are structurally divergent.
Salary buys furniture, equity buys your future. In strategic terms: tactical wins buy time, but architectural decisions buy survival. The architectural decision here is whether to keep concentrating irreplaceable assets in fixed locations or to distribute capability across cheaper, more numerous, more replaceable nodes.
2031
Five years from now, three shifts will have reshaped how nations and companies think about critical infrastructure.
First, the drone-to-defense cost ratio will force a redesign of military basing. The U.S. Air Force's Agile Combat Employment concept, which disperses aircraft across smaller, less predictable locations, will move from PowerPoint to doctrine. Fixed mega-bases like Prince Sultan will become logistics hubs, not parking lots for irreplaceable aircraft. The up to 26 E-7 Wedgetails the Air Force has envisioned acquiring will operate under fundamentally different deployment assumptions than the E-3s they replace.
Second, counter-drone technology will become its own market category. Directed energy weapons, electronic warfare systems, and AI-driven swarm defense will attract billions in procurement. Anduril, Raytheon, and a wave of startups are already building here. But the Compression Trap predicts that attackers will adapt faster than defenders can deploy. Expect a permanent arms race, not a solution.
Third, and this is where it matters for builders outside the military, the same asymmetric economics will accelerate in digital infrastructure. My read on this: by 2031, AI-generated cyberattacks will compress the cost of breaching a system to near zero, just as drone swarms compressed the cost of destroying physical assets. The organizations that survive will be the ones that designed for distributed resilience from the start, not the ones that bolted on defenses after the first breach.
The compounding flywheel favors whoever builds cheap, distributes wide, and replaces fast. Centralization is a liability when destruction is cheap. This is not a military insight. It is a systems design principle.
What to Build This Weekend
You do not need a defense contract to apply the Compression Trap framework. Here is how to stress-test your own infrastructure this weekend.
Step one: map your single points of failure. Use Manus to run a research workflow that audits your tech stack. Ask it to identify every system where one failure would halt operations. Database, DNS provider, authentication service, payment processor. List them.
Step two: calculate your replacement lag. For each single point of failure, estimate how long it would take to rebuild or switch if it disappeared tomorrow. If the answer is "weeks" or "we could not," you are sitting on your own E-3 Sentry. Write the number down.
Step three: build one distributed backup. Pick the single point of failure with the worst replacement lag. Use Lovable to vibe-code a minimal fallback. A static status page. A backup data export tool. A simple webhook relay. It does not need to be pretty. It needs to exist. 80% done is 100% freaking awesome when the alternative is zero percent done when the attack hits.
Step four: automate the monitoring. Use Perplexity's Comet browser in agentic mode to set up a recurring check on your critical services. Have it ping your endpoints, verify uptime, and alert you in Slack or email. This takes 30 minutes and costs nothing.
The Compression Trap teaches one thing above all: the cost of building resilience is always lower than the cost of rebuilding after a catastrophic loss. Use it.