# The Automaton That Stopped

## Maintenance Report — Unit AM-7734, Block 9 Corridor Maintenance

Unit AM-7734 is a Sunder Dynamics Model 14 corridor maintenance automaton, assigned to Block 9, Levels 3 through 7, since April 2221. The unit's function is environmental maintenance — floor cleaning, minor debris removal, air filter cycling, and surface sanitization. It is not sentient. It is not classified as synthetic life. Its processing architecture is task-specific, lacking the generalized cognitive framework associated with E.L.F.s or higher-order synthetic intelligences. It is a machine that cleans hallways. This report concerns a behavioral anomaly that the maintenance division has been unable to explain.

On February 17, 2224, at 14:23:07, Unit AM-7734 halted mid-task in the Level 5 east corridor. The unit was engaged in standard floor sanitization — rotary brush deployment, chemical dispensing, and forward locomotion at 0.3 meters per second — when it stopped. All locomotion ceased. All cleaning functions ceased. The unit's sensor array remained active. Its processing core remained powered. Its communication uplink continued to transmit diagnostic data, all of which reported normal operating parameters. The unit was functioning. It had simply stopped functioning at its task.

The halt persisted for three days. During this period, no diagnostic alert was generated because no system failure had occurred. The unit's self-monitoring systems reported full operational status. From the machine's own perspective — if a non-sentient machine can be said to have a perspective — nothing was wrong. It was powered, functional, connected, and motionless. The Shelf's maintenance scheduling AI eventually flagged the anomaly — not because it detected a malfunction but because the corridor's cleanliness metrics dropped below threshold, triggering a maintenance review that traced the deficit to AM-7734's stationary status. A technician was dispatched.

The technician's report is clinical. "Unit stationary in east corridor, Level 5, position 14.3 meters from the north stairwell. All systems nominal. No obstruction detected. No error codes. Unit is oriented toward the east wall, approximately 0.8 meters from the surface. Sensor array focused on wall surface at approximately 1.2 meters height. Attempted manual override — unit resumed operation briefly (approximately 4 seconds of forward locomotion) then returned to stationary state at original position and orientation. Sensor array re-focused on same wall surface. Noted that wall surface at focus point displays minor discoloration — water stain, approximately 15 cm diameter, consistent with pipe condensation. No other notable features. Recommend unit return to maintenance bay for full diagnostic."

The diagnostic revealed nothing. Every component tested within specification. The processing core's activity logs showed normal task-processing routines — the same algorithms that had governed the unit's behavior for three years of corridor maintenance. But the logs also showed something else: a sustained sensor focus on the wall surface that the technician had noted. The unit's optical sensors had been continuously scanning a 15-centimeter-diameter area of water-stained wall for 72 hours. Not passively — the sensor data showed active scanning, the resolution increasing over time as if the unit were studying the stain with increasing attention. The data was logged and categorized by the unit's standard processing routines under the label "environmental surface assessment." The category is standard. The duration is not.

When AM-7734 resumed normal operations, it worked differently. The change was subtle enough that the maintenance scheduling AI did not flag it for two weeks, and when it did, the flag was for increased supply consumption rather than behavioral anomaly. The unit was using 23% more cleaning solution per square meter. Its coverage speed had decreased by 15%. And its cleaning pattern had changed — where it had previously followed an optimized grid path, it now moved in overlapping curves, covering certain areas multiple times with what the scheduling AI's report described, in language that was meant to be purely descriptive, as "apparent care." The technician who authored the original report added a handwritten annotation to the file, which is unusual for a maintenance record and which I include here without commentary: "Unit seems to be cleaning more carefully. As if it started to care about the floor."