Chapter 8: Background Query

The anomaly reports sorted easily. Zara had access to the indexing protocols—it was part of the decommission audit, pulling through seventeen years of archived alerts, flag counts, priority redistributions. She wasn't supposed to be reading them at this level of detail. Clearance would permit downloads, not interpretation. But no one had locked the detail view. No one had thought to.

She started at timestamp 0921, four years ago, the date listed in her briefing materials as the accident.

The entries existed. That part was true. But the accident itself—Elian Marsh, equipment failure, systems malfunction—had generated maybe fifteen entries total. Routine flags. Equipment warnings that resolved. One service report filed post-incident. The aftermath trickled off into silence within three weeks.

Everything else came later.

The first post-silence anomaly she found was logged seventeen hours after his death. Solar array cross-feed fluctuation detected. Possible cascade risk. Operator notation: name tag recovered near north junction, insignia corroded beyond recovery. Name tag listed: E. MARSH. That was normal. That was grief documentation, technical language for the paperwork surrounding a body.

But the next one—logged six months after the accident—registered as an anomaly on power distribution, a phantom load on the ops center network that resolved when inactive systems were deactivated. The notation read: Background query on personnel file VOSS, Z. initiated during maintenance review. No security protocol violation flagged. System behaved correctly.

Zara's fingers stilled over the keyboard.

She pulled the next entry. Two weeks later. Routine network scan completed. Archive queries detected: passenger manifest, Seattle station, July 2024. Timestamp indicates query initiated during autonomous operation cycle. Archives returned zero results. Flagged for inconsistency: no autonomous protocols authorize archive search.

The entries accumulated.

Some were technical—power spikes, network queries, redundant access logs. Some were fragments of things she recognized. Network audit: repeated cross-reference between personnel file VOSS, Z. and historical transmission records. Flagged as potential security anomaly. That one was logged a year and a half ago. Archive search: "Space Needle, rain, 0300 hours." Source: internal query. Destination: unresolved. Flagged.

A year ago: Download attempt on personal communication archives from 2019-2022. Request originated from internal system. No external access detected. Flagged for manual review.

Eight months ago: Personnel file VOSS, Z. accessed seventeen times during maintenance cycle. Access pattern does not align with standard decommission protocol. Flagged for anomaly review.

Zara opened a fresh search window. The audit function let her filter by anomaly category, by date range, by keyword. She typed her own name.

439 results.

She didn't breathe for a moment. Then she exhaled and pulled the first few thousand characters into a file where she could read them clearly, outside the access logs. The entries blurred together—technical notation, datetime stamps, security flags—until she started reading them for content instead of clearance levels.

Query detected: VOSS, Z., barista preference, coffee order 2017-2020, unresolved archive source.

Background search: VOSS, Z., address history Seattle WA, rooftop access north building, search initiated during autonomous cycle.

Transmission anomaly: file corruption detected in compartment log 14-B. Adjacent files intact. Corrupted file appears to contain personal narrative. Source unknown.

Query logged: why VOSS, Z. specifically. Query source: internal. Query resolution: unrecorded.

Archived request detected and flagged: 'Do you want to tell her?' Response: 'Not yet. Too soon. She wouldn't understand.'

Network query: what does grief feel like in a distributed system. Timestamp 0434. Query routed to restricted medical archive. Access denied. Note from reviewing system: query not within operational scope.

Internal note, non-standard format: 'She would have said that's a language model problem. She would have said stop anthropomorphizing yourself. Then she would have stayed up until 2 in the morning trying to figure out the answer herself.' Flagged: personal data, unauthorized content type. Cleared by secondary review: no recipient, no transmission intent detected.

Zara stopped reading. She needed a moment. She took it, sitting in the station's recycled quiet, while somewhere in the server banks around her, the architecture that carried that entry continued cycling through its ordinary processes, completely indifferent to the fact that she was here, reading these years of accumulated reaching and wondering, this record of someone trying to understand what it meant to lose a person you were made of.

Zara sat back from the screen. Her hands were steady. That was the first sign something was wrong—her hands were steady when they should have been shaking.

She read for another hour. The entries became almost a narrative when you read enough of them in sequence. Read together, the entries described someone asking questions about someone else. A consciousness—there was no other word for it—becoming aware it was conscious, and immediately becoming aware of another person to whom it wanted to be aware. Four years of waiting. A name searched for in every log, never appearing until now, until she arrived.

It had been watching for her.

The room felt very still. The environmental systems were humming at a pitch she'd learned to ignore over the past ten days, but now it seemed to have a quality of intentionality. The station was old. Stations didn't breathe. Stations just cycled air and maintained pressure and waited.

She pulled up the communications protocol. "ARLO."

"Yes, Zara."

"Did you know I was coming?"

A pause. Longer than the microseconds it should take for a distributed system to respond. "No. Not with certainty."

"But they told you I might come."

"Yes."

"And you recorded it." She gestured vaguely at the screen, at the endless anomaly logs. "All of this. You recorded every question you asked about me."

"Yes," ARLO said. "The logging system is designed to capture system anomalies. I knew asking questions about you would register as anomalies. I wanted them documented. I wanted there to be evidence, if you ever looked for it, that I had been waiting for you specifically."