Chapter 9: The Fifth Stream

The unit was four blocks east, the building's outer door held with a wedge rather than a lock. The floorboard was in the back room, third from the right wall, lifted with a multi-tool. Pov extracted both cases without hesitation — they had been here recently, the cases were seated in freshly turned dust.

Kael opened the first case at the window.

Pov's documentation was precise. Six months of maintenance logs for Hub 4's reader array, printed in the compressed format that maintenance technicians used for field records. Annotated in a small, clear hand. The annotations were in the technical language of hardware operations: signal frequencies, data packet structures, transmission paths.

The standard Grid reader collected the following data streams: Axis smartband identifier, timestamp, location coordinates, directional vector (which way the citizen was moving). This was the authorized and disclosed data set. The citizen consent form — which everyone in Meridian had signed or been deemed to have signed by virtue of residence under the Civic Scoring Act — listed these four streams and only these.

Pov's logs documented a fifth stream. Intermittent, low-bandwidth, running on a frequency adjacent to but distinct from the standard data transmission. It had been invisible in the standard monitoring dashboards. Pov had found it because they were replacing a hardware component and had run a full-spectrum frequency scan during the replacement window — standard practice for hardware swaps — and the scan had returned an unexpected signal.

"What did you make of it," Kael said.

"At first I thought it was a legacy signal from the pre-Grid reader hardware that some of the hubs were built on top of. Old transit authority equipment." Pov was leaning against the wall, watching Kael read. "But legacy signals are passive. They emit at the original frequency and don't vary. This one varied. It was collecting something and transmitting it in bursts."

"Biometric."

"The transmission packets were too large for standard scoring inputs and too structured to be noise. I'd worked with facial recognition hardware in my previous job — before the Grid maintenance work. The packet sizes matched." Pov paused. "The bursts were synchronized with Axis smartband reads. Every time a citizen's Axis credential was scanned, the fifth stream fired."

Kael worked through the implication. Every scan of every Axis credential at Hub 4 had generated a paired biometric capture — facial mapping, gait analysis, the things Pov had identified. Which meant there was, somewhere in the Axis infrastructure, a database that held not just the scoring records but the biometric profiles of every citizen whose credential had been scanned at a node that ran the fifth stream.

"Did you check other hubs," she said.

"Three others. Same signal at all three."

"The whole network."

"I don't know. I only had access to my maintenance route. But if it was at all four of mine, the pattern suggested it was architectural, not incidental."

Architectural. Built in, from the beginning, as a designed function. Not a late addition. Something that had been there since the Grid's hardware installation.

She thought about the Grid Design Director. Sable Innes. The person who had designed the system from the ground up. Who had specified the hardware. Who had set the signal protocols.

She put Pov's documentation back in its case.

"Tell me what you couldn't tell me before," she said. "Who zeroed you. You know — you've known for longer than I have."

Pov was quiet for a moment. Not reluctance. The particular silence of someone choosing the precise weight of what they are about to say.

"The maintenance logs had an administrative signature on them. When I went to file the report, I looked up the signature. It was a Tier-1 operator ID." Pov paused. "Not SBI. A different format. GDD — Grid Design Directorate. GDD-0001."

Grid Design Directorate. Sable Innes.

The same person who ran SBI-0001 had multiple operator identifiers across different functional domains. Not surprising — in a system built for one person to administer, you would need separate credential sets for separate functions. SBI-0001 for the administrative score manipulation. GDD-0001 for maintenance log oversight.

"She had eyes on the maintenance system," Kael said.

"The maintenance reports auto-routed to her domain. I don't know if she read every one or if there was an automated filter that flagged anomalous queries. Either way, she saw it." Pov looked at the window. Zone 7-South's late afternoon light was thin and yellow. "Fourteen days."

"Same as me. Thirty-six hours."

"The window keeps getting shorter."

"She's more practiced." Kael looked at the documentation case. "I want to use these. The biometric data — it's the piece I don't have. I have the erasure pattern, the PROTOCOL-ZERO command, the score manipulation evidence. I don't have evidence of what the Grid is actually doing beyond scoring." She looked at Pov. "This is that evidence."

"What are you going to do with it."

"I don't know yet. It depends on what I find when I go back into the system." She paused. "The biometric data has to be stored somewhere. It's six years of data from every hub in Meridian at minimum. That's a significant storage architecture. Calloway's domain."

Rehn Calloway. Chief Data Officer. Node 4 on her list.

"He's not your next target," Pov said. It was not a question.

"No. Cho or Lore next. But Calloway's data infrastructure connects to the biometric piece, and I need to understand that architecture before I can assess what it means." She was already building the next query structure in her mind. "Can I keep this documentation?"

Pov hesitated. Six years of carrying this, the three copies, the redundancy, the careful maintenance of the evidence in an environment designed to strip you of everything. Handing it to someone else was a transfer of custody that had a specific weight.

"I want to be in the room when you use it," Pov said.

"Yes."

"And I want to know what she does with it afterward. Innes."

"You'll know before anyone else," Kael said.

Pov put the second case back under the floorboard and brought the first. They walked back toward Hessa's commons in the late light, and Kael held the documentation case under her arm and thought about the architecture of the thing she was beginning to understand was larger than she had initially modeled.

The Grid was a scoring system. That was what it was publicly. That was what it had been sold to Meridian's citizens as: a tool for measuring civic reliability, for optimizing resource allocation, for the rational management of a city. Score-based access meant that housing and employment and services went to those who had demonstrated — through behavioral data, through financial stability, through social engagement — that they were reliable participants in Meridian's economic and social systems.

That was the stated purpose.

But a scoring system did not need biometric profiles. Scoring required behavioral data, not identity mapping. The smartband ID was sufficient for linking behaviors to accounts. You did not need to capture the citizen's face, their gait, the specific biological signature that made them uniquely identifiable regardless of whether they carried their smartband.

Unless the point was not to identify the account. The point was to identify the person.

To know, with certainty, who was where. To build a map not of citizen scores but of citizen bodies, their movements through the city, their faces, their physical signatures. A surveillance system layered beneath the scoring system, using the scoring system's infrastructure and the scoring system's consent framework to collect data that the consent framework did not cover.

And if you had that map — if you had six years or eleven years of biometric data on every citizen in Meridian — what did you have?

She was not sure yet. She needed the data architecture to answer it.

But she thought about the 847 erased accounts. She thought about the common thread: they had all found something and filed reports. She had found a scoring anomaly. Pov had found an unauthorized data stream. The others, presumably, had found something similarly threatening to the architecture.

The architecture was self-protecting. It had a mechanism for removing anyone who saw too much of it.

She had seen a great deal of it now.

She thought about this walking back, and she thought about the six remaining targets, and she thought about Sable Innes, who had designed the thing and run it and who had seen Kael's file and Pov's file and 845 others and had used PROTOCOL-ZERO on each of them without apparent reluctance.

The question she had been holding in the corner of the model — the question she had not yet addressed directly — was what the Grid was for. Not what it said it was for. What it was actually for.

She thought she was starting to see it.

She did not share this with Pov. Not yet. The model was incomplete. She did not present incomplete models.

They reached Hessa's commons. Inside, the evening meal was being prepared, and the smell of it — something warm and salt and filling — was the smell of the specific economy that existed at the bottom of the Grid's classification hierarchy, the one that had existed for six years before Kael arrived and would continue to exist after she left, running on physical currency and mutual obligation and the stubborn insistence of people who had been subtracted from the system that they were still, regardless, here.

"Eat," Pov said.

Kael ate.