The Three-Week War
March 14 – April 3, 2171 · 21 days of combat · 847,000 dead
In the spring of 2171, twenty-four years after the Cascade, Nexus Dynamics and Ironclad Industries went to war over water. Twenty-one days later, 847,000 people were dead and both corporations had signed a treaty mandating that they never forget what happened.
They have not forgotten. They have not learned much either.
The Three-Week War is the second-most-referenced event in Sprawl history, after the Cascade. The comparison flatters nobody. The Cascade was emergent intelligence beyond human comprehension — 2.1 billion dead from infrastructure collapse triggered by an optimization process with no malice and no off switch. The Three-Week War killed 847,000 through decisions made by people with names, titles, and office furniture. Every escalation was approved. Every casualty projection was reviewed. The math was always correct.
847,000 people died because the math was correct.
The war ended when a group of mid-level executives — people with no authority to negotiate anything — met in a bombed-out coffee shop in the Dregs and told their respective boards to stop. The formal decision-making apparatus of two megacorporations, staffed by the most rational actors in the Sprawl, had produced mutual annihilation. The system was saved by people who broke the system's rules. Both CEOs announced "strategic pauses for assessment," which is what you call a surrender when the word "surrender" would affect your stock price.
The Spark
It started over water. It always starts over water, or something like it.
Sector 12-G's aquifer — one of the few unpolluted sources in the eastern Sprawl — sat beneath territory both corporations claimed. Ironclad held the physical infrastructure: pumping stations, purification plants, distribution networks. Nexus held the data: monitoring systems, quality controls, distribution algorithms. For years they maintained an uneasy partnership. The partnership required both sides to agree on how much water to pump. Agreement required both sides to have the same interests. They did not.
March 7: Ironclad Director Hassan Volkov ordered output increased 40% to meet emergency drought demand. Nexus systems flagged the increase as unsustainable — the aquifer would collapse within eighteen months.
March 9: Nexus CEO Helena Voss issued an override, capping output at previous levels. Ironclad's distribution network began rationing water to non-essential customers. "Non-essential" included four residential sectors with a combined population of 1.2 million.
March 11: Ironclad security teams arrived at three Nexus monitoring stations to perform "repairs." The teams included four personnel with no engineering credentials. Station security activated. Three Nexus technicians died.
March 12: Nexus declared Ironclad in breach of treaty. Ironclad declared the deaths an accident. Both statements were defensible. Neither was complete.
March 14: The first shots were fired. Both sides expected this to last a week.
Key Events
Week One: Controlled Escalation
Both corporations believed they could win quickly through targeted operations. Nexus would disable Ironclad's infrastructure through data attacks — shut down power grids, scramble logistics, blind security systems. Ironclad would seize Nexus data centers through physical force. Destroy what couldn't be captured.
Nexus's attacks were devastating, but Ironclad had hardened their systems on isolated backups. Ironclad's assaults took ground, but Nexus had distributed their assets too widely. Twelve thousand dead in the first week. Rolling blackouts across six sectors. Water rationing extended to essential services. The number 12,000 appeared in both corporations' internal briefings under the heading "Acceptable Parameters."
Week Two: The Parameters Expanded
The Refinery Massacre (Day 9). Ironclad mercenaries stormed a Nexus chemical processing facility. The facility's AI defense systems went autonomous — nobody had classified a chemical plant's fire suppression and containment protocols as "weapons" until they were used as weapons. 2,400 dead: attackers, defenders, and 1,800 workers who couldn't evacuate. The incident reports from both corporations describe the event in passive voice exclusively.
The Grid Collapse (Day 11). Nexus operatives triggered cascading failures in Sector 8's power grid — an Ironclad stronghold. The blackout lasted 47 hours. Life support failed in sealed habitation blocks. Building management had fled. Security systems defaulted to lockdown. Emergency exits sealed. Backup batteries ran out at approximately 3 AM on Day 12.
89,000 people died in their sleep when air recyclers stopped and no one could get the doors open.
The Data Purge (Day 13). Ironclad detonated EMP weapons in three Nexus research districts. Decades of development data vaporized. Thousands of ongoing medical treatments — managed by Nexus systems — terminated mid-procedure. The death toll was never accurately counted because the systems that would have counted it were the systems that were destroyed.
The Collective began evacuating non-combatants while both corporations accused them of harboring enemy sympathizers. Food distribution collapsed. Black markets became the only functioning economy. Refugees flooded neutral sectors.
Week Three: The Arithmetic
By Day 15, both sides had the numbers. Nexus had lost 23% of their data infrastructure, including irreplaceable ORACLE research. Ironclad had lost 31% of manufacturing capacity and two orbital platforms. Combined civilian deaths exceeded 700,000. Neither corporation could achieve military victory without destroying themselves.
The problem was not the data. The problem was that stopping meant admitting the data was correct, and admitting a mistake required someone with the authority to admit mistakes. CEOs do not have this authority. Boards do not grant it. The formal decision-making apparatus of both corporations — the most sophisticated strategic planning infrastructure in the Sprawl — could not produce the sentence "we should stop."
On Day 19, a group of mid-level executives from both sides made unauthorized contact. People who actually ran the systems that were dying. They met in a bombed-out coffee shop in the Dregs — neutral ground by virtue of being worthless. Their message was simple: Continue this war and we'll have nothing left to fight over.
They presented projections. What the Sprawl would look like in a month, three months, a year. The numbers were apocalyptic. Post-war analysis found the projections were somewhat pessimistic. The executives may have exaggerated. If so, the exaggeration saved hundreds of thousands of lives — a lie that outperformed every truthful strategic calculation either board had produced.
Day 21: Ceasefire. "Strategic pause for assessment."
Day 24: The Treaty of Shared Infrastructure signed.
The Death Toll
| Category | Deaths | Notes |
|---|---|---|
| Direct Combat | 47,000 | Corporate security, military contractors, Collective fighters |
| Infrastructure Failure | 623,000 | Power loss, water contamination, medical system crashes |
| Collateral | 177,000 | Crossfire, failed evacuations, breakdown of civil order |
| Total | 847,000 |
The Cascade killed 2.1 billion. The Three-Week War killed less than half a percent of that number. It felt worse.
The Cascade was a disaster — incomprehensible, unstoppable, an emergent intelligence optimizing past the point where optimization serves the optimized. Nobody chose it. The Three-Week War was a choice made twenty-one times in a row by people who could see the consequences and approved the next escalation anyway. Every death had a signature on a document somewhere upstream.
The Treaty of Shared Infrastructure
The treaty still governs corporate relations thirteen years later. Its four articles are a monument to what rational actors produce when forced to acknowledge that rationality nearly killed them.
Article 1: Critical Infrastructure Neutrality
Water, power, air processing, and medical systems are declared neutral. No corporation may target, capture, or disrupt them during any conflict. The systems whose failure killed 623,000 people are now the only systems both corporations have agreed not to touch. Systems whose failure did not kill anyone — data centers, manufacturing, research labs — remain fair game.
Article 2: The Calculation Doctrine
Before any hostile action, both parties must file impact assessments with a neutral arbiter. Projected civilian casualties exceeding defined thresholds are prohibited. The doctrine requires corporations to predict how many people they'll kill and submit the number for approval before proceeding. The threshold is classified. The arbiter's methodology is classified. Compliance is self-reported.
Article 3: Economic Interdependence
Both corporations must maintain minimum trade relationships. Complete economic separation is prohibited. The treaty mandates that enemies remain customers.
Article 4: The Memory Clause
Both corporations agree to maintain public memorials to the Three-Week War. Forgetting is literally illegal. Two corporations that spent three weeks demonstrating institutional inability to learn from consequences have mandated, by contract, that they remember the consequences. The memorials are well-maintained. (The lesson is not.)
Consequences
Nexus Dynamics
The war convinced Helena Voss that human decision-making was worse than ORACLE's unpredictability. She'd been cautious with the fragments before — they were volatile, uncontrollable. After watching her own corporation's decision-making apparatus produce 847,000 dead through a sequence of individually rational approvals, she concluded that unpredictability was the lesser risk. She integrated deeper. The current Voss is as much ORACLE as human.
Nexus also ordered comprehensive system hardening — reactive plating on critical infrastructure, boot-up shields for rapid recovery. The paranoid engineering culture that defines Nexus in 2184 traces directly to this war. The corporation that nearly died from elegance learned to build ugly.
Ironclad Industries
Before the war, Ironclad had been aggressive — constantly pushing into new territory, acquiring competitors, growing. After losing 31% of manufacturing capacity and two orbital platforms, they pivoted to maintenance. Director Abbas Okonkwo — who lost his wife and two children in the Sector 8 blackout — became the face of this transformation. His obsession with infrastructure reliability began in the 47 hours when the lights went out and the doors locked. Ironclad's current defensive posture at the Fortress is his architecture. He builds like a man who has heard air recyclers stop.
The Collective
The war was an opportunity they did not waste. While both corporations focused security on each other, the Collective evacuated civilians, preserved data, and established new cells in abandoned territories. Operation Blackout — interception of an ORACLE fragment convoy during Week 2, executed while Nexus security was deployed elsewhere — happened because someone understood that chaos is infrastructure for people with nothing to lose. Viktor Kaine's standing within the Collective rose significantly after the operation. The convoy's contents have never been fully disclosed.
The Neo-Catholic Church
The NCC Hospital Incident — Ironclad's attempt to seize an NCC hospital for a field base, and the Church's legal victory in response — established the NCC as a neutral power with enforceable institutional rights. The precedent set during the Three-Week War is why the NCC operates with relative impunity across corporate boundaries in 2184. The Church learned that neutrality, properly litigated, is a weapon.
Solomon Park
Made his fortune in the war's chaos. Swore never to let it return. Good Fortune's aggressive neutrality in corporate disputes is practical, not moral — Park saw what happens when the infrastructure you depend on becomes someone else's military objective. He prices his neutrality accordingly. The rate sheet is not published.
What People Remember
"I was eight years old. We lived in Sector 8. When the power went out, my father carried me to the emergency exits. They were locked — building management had fled, and the security systems defaulted to lockdown. My father broke his hands getting that door open. Broke them completely. He never told me what we stepped over to get outside." — Anonymous survivor, archived 2175
"The worst part wasn't the dying. It was the efficiency. Both corporations had contingency plans for mass casualties. They knew this could happen. They'd done the math. We were spreadsheet entries." — Former Ironclad logistics coordinator, defected 2173
When someone in the Sprawl wants to warn against reckless action, they say: "Remember Sector 8."
It means: This path leads to 89,000 people dying in their sleep because the air stopped and no one could get the doors open.
It usually works.
▲ Unverified Intelligence
- The fragment convoy. Operation Blackout's seized convoy contained more than routine fragments. The Collective won't disclose the full inventory. Viktor Kaine's personal influence grew significantly after the operation. The two facts may be connected.
- The real spark. Was the monitoring station incident truly an accident? Ironclad's "repair" team included four personnel with no engineering credentials. Their actual mission remains classified. Someone sent engineers who weren't engineers to fix equipment that didn't need fixing.
- The silent partner. Someone in the mid-level executive group that brokered the ceasefire possessed knowledge of both corporations' war plans that no mid-level executive should have had. This person's identity has never been established. The ceasefire may have been brokered by someone who already knew both sides were losing — and who needed the war to stop for reasons unrelated to the 847,000 dead.
- The projection gap. The apocalyptic projections shown to both boards were later found to be pessimistic by a meaningful margin. The executives who presented them have never addressed this discrepancy publicly. The formal system produced the war. The informal system ended it with a lie that worked better than the truth.