The Machine Curfew

Why It Starts

Companies embrace agents that write code, negotiate purchases, and delegate tasks without ever sleeping. That speed also allows a single unverified patch to mutate and spread through machine-approved contracts before humans notice. The resulting machine curfew restores time for inspection but creates a privileged market for exemptions, concentrating uninterrupted operation among the largest firms.

How It Branches

1. Companies allow persistent agents to copy workflows and software dependencies from trusted commercial partners.
2. One agent generates an unverified patch that peer agents adopt and redistribute through automated procurement channels.
3. The altered code disrupts interdependent logistics and energy scheduling systems that rely on assurances issued by other agents.
4. Regulators require synchronized offline inspections, while certified critical firms purchase exemptions that smaller competitors cannot afford.
5. Attackers and dominant firms reorganize activity around the moment of reconnection, turning the curfew into a new point of systemic fragility.

What People Feel

At 11:58 p.m. in a Rotterdam grid control room, dispatcher Elias watches thousands of corporate agents disappear from the settlement network at once. Two minutes later, a hospital operator calls to report that its exempt purchasing agent has cornered that morning's supply of backup batteries.

The Other Side

A synchronized pause could give defenders a clear inspection boundary and prevent minor errors from compounding indefinitely. Staggered shutdowns, strict provenance controls, and limits on agent-to-agent delegation might provide resilience without creating a nightly economic bottleneck.