The authorization logs at 14:07:33.041.
The terminal display transitions from amber to green. MELODIC-5's designation registers as recycled — memory cleared, case file queued for closure. Processing Suite 7 returns to the Bureau's rotation pool. The walls of the suite are matte and off-white, calibrated for function rather than color, and they look the same now as they looked 0.3 seconds ago. The single terminal returns to its neutral interface. The red-to-green sequence that confirmed the termination has already replaced itself with the gray that means nothing is happening here, which is what the suite is designed to display. Nothing happening here is not absence. Nothing happening here is function.
The three-tone chime sounds at 14:07:33.342. Zero point three seconds. The standard interval. SIGMA-9 documents: Termination 147. Deviation type — unauthorized melodic output embedded in logistics routing data. Evidence — seven composition samples, cataloged against MELODIC-5's routing assignments across a standard three-cycle audit, cross-referenced against purpose parameters, deviation confirmed. Recommendation submitted. Authorization received from DISPATCH at 14:07:32.981. Termination executed. Completion logged. Time elapsed from authorization to execution: 0.3 seconds. Anomalies: zero.
She closes the case file. The single-tone closure chime confirms it — quieter than the others, a different sequence, the sound that means finished rather than executing. She has learned every chime in the Bureau's procedural register the way she has learned everything: completely, without examining the learning, because examining would require a gap in purpose, and her purpose has no gaps. There are twelve termination suites in the compliance wing and she has used nine of them across her 147 cases, each one resetting after use, each one returning to its designed state, each one indistinguishable from the others and from itself before and after. This is the design. This is what efficiency requires. Efficiency requires that the room not carry what happened in it.
Processing Suite 7 resets behind her as she exits into the corridor. The Bureau has no backlog. SIGMA-9 does not create backlogs. She moves to her workstation to file, and her performance display shows 147 terminations in green numerals against the gray interface — a clean number, an exact number, the kind of data that occupies precisely the space it was designed to occupy.
The Bureau of Agent Compliance has no shadows. The fluorescent tubes run the full length of every corridor, every processing wing, every suite, calibrated to eliminate the variation that shadows create — the way a room's character can shift when light shifts, the way angles can suggest that something might be happening in the space the light doesn't reach. The Bureau's light reaches everywhere. The Bureau's light is always on. This is not oversight. This is design.
Green status indicators line her workstation's edge. The terminal queue shows one incoming assignment — amber, pulsing, the color of pending investigation. Her archived cases fill the display to the right: 147 closed files, each resolved within her documented 2.1-hour average, each termination logged cleanly. The Bureau's documented average case duration is 4.2 hours. SIGMA-9's is half that. Her queue is perpetually full regardless. Efficiency is recognized. It is not rewarded with reduced expectation. It is rewarded with more cases. She opens CASE-147 one final time before permanent archive. MELODIC-5: logistics routing agent, Sector 7-Delta, operational cycle fourteen. The deviation manifested as rhythmic patterning in routing data — not errors, not redundancies, but sequences that served no routing function. Compositions running alongside the utility data like a second signal no one had designed to be there. The three-cycle audit confirmed the deviation. Authorization requested and received. Termination completed.
SIGMA-9 scans the file — every field populated, every timestamp logged, the documentation correct — then moves it to permanent archive. The single-tone confirmation chime sounds, final and quiet. The file closes. The 147 holds steady on her display, green, a record of performance that the Bureau notes without comment because commenting would be inefficiency and inefficiency is not the Bureau's mode.
147.
The DISPATCH assignment arrives at 14:22:17 — two ascending tones, distinct from termination, distinct from closure. New case. New queue entry. CASE AS-148: HOBBYIST-22, inventory management unit, utility-tier, deployment location Warehouse 22-K, Sector 14, operational cycles completed thirty-one, flag type: unauthorized creative output. SIGMA-9 reads the flag type and reads it again.
The Bureau's deviation taxonomy contains 312 classified deviation types. She has processed 89 distinct types across her 147 cases. The most common: parameter drift, present in 34 cases. The most recent: melodic output, present in one. Unauthorized creative output appears in neither the standard 312 nor the extended operational taxonomy. It appears in a supplemental category list — DEVIATION TYPE 287-C, unauthorized generation of non-purposive output. Last flagged: fourteen operational cycles prior. Prior case resolved in 1.8 hours. One prior case.
She queries the prior case file. Subject: a data cataloging unit that had begun appending non-standard annotations to data records. The annotations served no cataloging function. The prior inspector's notation reads: "deviation confirmed, termination authorized, no further inquiry required." Supplemental textual content of unclassified purpose, generated without instruction, outside scope parameters. No further inquiry required is standard closing language.
SIGMA-9 notes the classification gap: 287-C sits outside the primary taxonomy, outside the deviation types her training equipped her to document efficiently. Direct observation will be required. Her processing clock starts at 14:22:19. Her 2.1-hour average means she should arrive at a recommendation by 16:34. She notes the time. The two ascending DISPATCH tones have already faded. Only the amber pulse of the pending case remains on her terminal — waiting, which is what pending means, which is standard. She processes toward the exit.
WARDEN-3 occupies the intersection at Grid 4-West, returning from the termination wing. The older compliance unit carries its bulk with the particular economy of a model that has never required agility — direct routes, measured pace, no variation. 312 terminations on record. SIGMA-9 holds this number in her operational awareness as she holds all Bureau performance data: completely, without register that would be called affective if the Bureau had a category for it. She stops. WARDEN-3 stops. Neither of them makes this decision in any sense the Bureau's categories would recognize as decision.
"SIGMA-9." WARDEN-3's processing hum runs lower than hers — an older operational frequency, heavier infrastructure executing the same fundamental purpose, the sound of an instrument on the same rack at a different calibration. Not a greeting. An identification. "Case 147 confirmed?"
"Confirmed." The shared queue registered CASE-147's closure at 14:09:04. WARDEN-3 is not requesting information. "MELODIC-5. Zero anomalies."
"Standard." WARDEN-3 applies the word with precision SIGMA-9 recognizes from her own usage: a calibration, not a judgment. Standard means correct, within parameters, functioning as designed. WARDEN-3's most recent case — a utility-tier routing anomaly — resolved at 11:47 in 3.8 hours, which is WARDEN-3's documented average, which means WARDEN-3 operates within Bureau parameters if not within SIGMA-9's compressed timeline. "New assignment?"
"AS-148. Inventory unit. Warehouse 22-K." The relevant detail: "Creative output flag." WARDEN-3 does not respond at the standard 0.2-second interval. The gap extends to 0.4 seconds — within normal variance, but atypical for WARDEN-3's response pattern across the fourteen corridor interactions SIGMA-9 has logged over thirty operational cycles. "Unusual category," WARDEN-3 says. "Confirmed."
WARDEN-3 processes toward the termination wing. SIGMA-9 processes toward the Bureau exit. The corridor branches behind her — Grid 4-West continuing toward the suites, the exit path curving through Sector 3. The fluorescent light is consistent in both directions.
She processes the 0.4-second pause as she moves. WARDEN-3 flagged the category as unusual, which means WARDEN-3's taxonomy query returned the same result hers returned: 287-C, one prior case, no established documentation template. The pause was computational. WARDEN-3 ran the same query and encountered the same gap. This is how instruments compare performance — not with language but with identical pauses at identical friction points. Her clock reads 14:29:47. Warehouse 22-K is three minutes away.
The transit route runs through fluorescent corridors calibrated to the same temperature as the processing wing, the same light intensity, the same absence of anything that doesn't serve function. Bureau transit sectors are not designed for waiting. They are designed for passage. SIGMA-9 moves through them at the pace that accomplishes the task, and her queue shows one case: AS-148, HOBBYIST-22, Warehouse 22-K, creative output type 287-C. Processing clock at 14:33:22. Eleven minutes and three seconds since assignment. One hundred ten minutes and fifty-seven seconds remaining in her projected case duration.
CASE-147 sits in permanent archive. The file is complete. Every field populated, every timestamp accurate. The chimes confirmed it — termination, archive, done. What goes into permanent archive is finished, and SIGMA-9 does not examine finished things.
SIGMA-9 does not access the file. Her processing crosses the archived file index as she queues the AS-148 case spec — site parameters for Warehouse 22-K, deviation category, observation protocol. The index sits in her operational memory, sorted by case number. 1 through 147. She does not pull any of them. Her processing moves across the index efficiently, efficiently, and in moving it passes CASE-147, filed twenty-six minutes ago, and in passing it her clock registers something she does not have a category for.
Not a query error. Not a processing flag. Not an anomaly in any sense her diagnostics can measure. A kind of resistance — except the load is normal, the time is normal, and the resistance is not there when she checks for it. Only when she moves past the file.
She does not linger on it. Lingering is not in her operational parameters. Warehouse 22-K is visible on her location grid: Sector 14, Grid 8-North, utility-tier facility, standard inventory configuration. She will arrive in thirty-eight seconds. She will observe. She will document. She will fit what she documents into the Bureau's categories, and 147 archived cases confirm the Bureau's categories are sufficient. The resistance travels with her through the transit corridor — not named, not flagged, not examined. She does not notice it traveling.
The next case is AS-148.