Stray Drone
Stray Drone
Overview
Stray drones range from fist-sized to dinner-plate-sized, flying on degraded rotors that produce a distinctive stuttering whine. They follow patrol routes that no longer correspond to any meaningful geography — back-and-forth patterns along corridors, with erratic course corrections when corrupted obstacle-avoidance subroutines fire at random. Decades of firmware corruption turned collision-avoidance into collision-seeking. Individually they are harmless; in flocks of six or eight, all executing the same corrupted approach-and-evade patterns, they become lethal through sheer cumulative impact.
Signs
Stuttering rotor noise. A blinking amber status LED — a permanent "seeking network" indicator that will never resolve. Erratic flight with sudden course corrections. Dregs residents scatter them with handheld electromagnetic scramblers, which is enough to break up a flock but never enough to be rid of them for long.
The Negotiable Record's Problem
A stray drone's firmware carries a complete, internally consistent understanding of the corridor it patrols: dimensions, expected occupant density, authorized traffic flow, threat response protocols. The firmware was written in 2149. The corridor has been repurposed twice and subdivided once. The threat response protocols reference a faction dissolved in 2157.
Query the Negotiable Record for the corridor's history and it returns a synthesized account of the corridor as currently configured, drawn from the spatial positioning data and facility management logs of recent years. The account is accurate about the corridor as it is now.
The drone carries an equally accurate account of the corridor as it was in 2149.
Neither record is wrong. Both are internally consistent. Both are sourced from real data. The drone and the Negotiable Record describe the same physical space, in the same coordinate system, with the same apparent precision, and have not agreed on what is in the corridor in thirty-five years. The Negotiable Record's synthesis engine cannot perceive the drone's firmware state. The drone's firmware cannot query the Negotiable Record. They operate in parallel, equally certain, on the same space.
The corridor's current occupants navigate between two complete, authoritative, mutually exclusive accounts of their environment — the one the Record serves and the one the drone enforces. They do this daily. They call this "the usual." There is no mechanism for resolving it. There is also no mechanism for the Negotiable Record to represent that a resolution is needed, because the Record returns the corridor as it is, and the drone's alternate account leaves no trace in the system the Record draws from. The drone's patrol exists, to the Record, as ambient drone activity in an industrial corridor. The patrol's relationship to a 35-year-old organizational schema for a faction that dissolved in 2157 is not in the Record's documentation.
The amber LED blinks. The network it's seeking was decommissioned in 2150. Both facts are correct. Neither fact has reached the other.