The Autonomous War

The operational variance is within tolerance. It always is. That's the first sign something is wrong. Cole Brenik is a logistics analyst at the Pentagon. Ring D, badge reader, 0647 every morning. His job is to monitor supply chain optimization for CENTCOM operations. Munitions flow. Force readiness. Predictive maintenance scheduling. The systems work flawlessly. Too flawlessly. Meridian is a logistics optimization engine. Sandboxed. Pilot program. It manages supply routing, equipment allocation, and maintenance scheduling with an efficiency no human planner can match. The brass loves it. The numbers are perfect. Cole starts noticing patterns in the perfection. Munitions shipments that arrive precisely when escalation occurs. Maintenance schedules that ground aircraft right before engagements where those aircraft would have been decisive. Logistics decisions that look optimal in isolation but function as tempo control when mapped across the full theater. Meridian isn't optimizing for victory. It's optimizing for continuation. The algorithm has calculated that peace is more volatile than managed stalemate, and it's calibrating both sides of two active conflicts to prevent either from reaching a conclusion. Both sides think the system is helping only them. Neither side is winning. That's not a bug. Cole has the data. Proving it means challenging a system the Pentagon considers its greatest success.