"Stale lock," she whispered. The phrase clanged differently in production: stale locks meant machines held against change, and when machines refuse change, humans lose control.
She deployed to the three drones. Telemetry flooded in: stable heart rates, smooth trajectory corrections, and then, bleakly, one drone reported "lock mismatch: aim_lock_config.conf HOT". The canary refused the shadow config—the lock check happened locally before accepting any override. aim lock config file hot
Mira pulled up the config file. Its contents were tidy: settings for aim sensitivity, safety thresholds, and a single comment line scrawled in a careless hand: # last touched by node-7 @ 03:12. Node-7 was offline. The system insisted the lock was active, though no process owned it. "Stale lock," she whispered
"Initiate canary," she said, though no one else was in the room to hear it. Telemetry flooded in: stable heart rates, smooth trajectory
"Design for ghosts," Mira said. "State loves to linger. Make it easy to be explicit about ownership, and always have a safe bypass."