Chapter 16: The Ghost Architect

The question of how to reach Sable Innes was, technically, not complicated.

What was complicated was the calculation around what came after.

Innes was not like the other six. Rael, Lore, Mast: public figures, exposed through public-facing journalism, their exposure contained by the same institutional structures that had protected them. Cho, Calloway, Fane: corporate and civic officials, their exposure requiring more technical apparatus but still processable through existing investigative frameworks. All six had vulnerabilities that were legible within the city's normal institutional machinery — the press, the regulatory structure, the political accountability mechanisms.

Innes had none of these. She was an administrative ghost. No public record, no citizen score in the accessible database, no media profile. The Grid Design Directorate existed as a footnote in an eleven-year-old regulatory document. Innes's name existed in Kael's model, derived from organizational logic and operator ID correlation and Pov's maintenance report documentation — but Kael had no direct evidence linking the name Sable Innes to SBI-0001 or GDD-0001 or PROTOCOL-ZERO. She had organizational inference. She needed confirmation.

And then she needed to figure out what confirmation made possible.

The press exposure that had worked for the previous six required a public identity to expose. If Innes had none — if she existed only inside the system, visible only from within it — then the standard exposure package would not function. You could not print a dossier on a person the city had no record of.

Unless you had access to the records that the city did have.

Innes was in the Grid. Just not the public-facing Grid. She was in AUXDATA and the GDD administrative partition and the Tier-1 system that ran PROTOCOL-ZERO. She existed in the system at the highest level, and she had protected that existence precisely by keeping it invisible to everyone below Tier-1.

Kael no longer had Tier-1 access. The orphaned session token was dead. The credential chain was closed. She had been cut off from the network she needed.

She had one other option. It was the option she had been thinking about since day three in Zone 7-South, setting it aside because the earlier targets had not required it, returning to it now because the last one did.

---

On the second day after the triple publication, she sent a message to Axis Corp.

Not through the system — she had no system access. Through a physical channel: Dennar, whose licensed appearance allowed him to approach the building's public intake desk on Commerce Level 3, which accepted physical documents from any Meridian resident including those presenting as non-residents for documented legal purposes.

The document she sent was a formal internal communication, formatted in the template she had used for seven years of analyst correspondence. The header was Axis Corp standard. The routing was addressed not to a department but to a specific internal identifier: GDD DIRECTORATE — ATTENTION: GRID DESIGN DIRECTOR.

The body was brief.

I have compiled a complete record of PROTOCOL-ZERO operations, AUXDATA contents, SELC Protocol documentation, and the Population Optimization Directive. This record includes evidence linking all functions to the GDD-0001 and SBI-0001 operator identifiers. I have verified your identity as the operator. I am prepared to release this material in its complete form, including your personal identification. Before I do, I am requesting a meeting. Reply through the standard internal communications channel using the analyst session token KM-4471-ALPHA — I will receive the reply.

She had not told Fetch this was coming. The session token was dead for the network, but the communications protocol that used the token for identity verification operated on a different authentication path — one that would accept the dead token as a caller ID even if it could not open a data session. She had verified this in the last hour at Fetch's terminal before the session closed. A reply to her token would reach Fetch's terminal address, which was still running, still receiving.

She sent the message and waited.

---

The reply came in eighteen hours.

It came to Fetch's terminal as a communication package addressed to KM-4471-ALPHA. The package was encrypted with the standard Axis internal key. Kael had the decryption protocol memorized — it was in the analyst documentation she had read and retained the way she retained all operational information.

The decrypted reply contained two words and a location.

Tomorrow. Level B3.

Level B3 of Axis Corp's main building was the subterranean infrastructure level — the server room complex, the utility systems, the network hardware that was the physical body of the Grid. It was not a location designed for meetings. It was a location designed to be unwatched, unmonitored, the one space in the building where the surveillance architecture did not surveil because the surveillance architecture was the infrastructure.

She read the location twice. She thought about what it meant that Innes had named it. It meant Innes understood what Kael was and was not — what she had, what she could verify, what her vulnerabilities were. It meant Innes was not afraid of the meeting in the way that a person who intended to resolve the meeting through institutional channels would be. It meant Innes was proposing a space where no one would watch, which was either an offer of privacy for genuine negotiation or a preparation for something that required the same absence of surveillance.

Kael thought about which it was for a long time. She concluded: both. Innes wanted to know what Kael had. Innes also wanted the option to resolve the situation without further institutional exposure.

---

She thought about the forty-three floors of licensed space between her and Level B3. The scanners in every lobby, every corridor, every elevator. The biometric readers that Pov had found — live, active, capturing everything. A zero walking into Axis Corp's building would set off every access control system in the structure before she reached the lobby desk.

She spent one day building her access plan. It used Sev — whose knowledge of service corridors and maintenance access was, in this case, precisely applicable. The Axis Corp building had a utility connection to the city's underground service network, a maintenance channel that predated the Grid's installation. It was unmapped in the Grid reader array because it was infrastructure, not citizen space. Sev knew the channel. She had worked in building maintenance in the sector before her zeroing.

Kael also spent the day writing the Innes package in full. Not the exposure document — the complete record: every element of everything she had found, annotated, cross-referenced, with the chain from PROTOCOL-ZERO through AUXDATA through SELC to the Population Optimization Directive's Priority Relocation program. Complete. Conclusive. Including the section she had been building toward since day one: the identification of Sable Innes as the operator of SBI-0001 and GDD-0001, the designer of the system, the person who had run it for eleven years and protected it by erasing 847 people who had found any part of it.

She made four copies. She gave one to Pov. One to Oltan. One she put in Quil's keeping. One she carried in the lining of her coat.

She told all three: If I am not back in forty-eight hours, the package goes to Tola Ries. All of it. Everything.

---

She reached Level B3 through the utility channel at 23:00. Sev brought her to the access point and waited at the channel entrance — if Kael did not return by 02:00, Sev would leave and activate the forty-eight-hour provision.

The utility access panel opened into a concrete anteroom between the server housings. The server room itself was behind a heavy door with a biometric lock that was active — she could hear its low frequency hum. She did not attempt the door. She stood in the anteroom and waited.

Sable Innes came through the server room door at 23:11.

Kael had built a model of what Innes looked like based on no data. She revised the model immediately. Innes was older than she had projected: late sixties, compact, with the kind of physical presence that came not from size but from the specific density of someone who had spent decades being the person that other people in a room adjusted themselves to. Her clothes were institutional, high-quality, the kind that existed in a register above branded without being ostentatious. She carried nothing visible — no device, no case, no smartband.

She looked at Kael for a moment before speaking.

"You've been thorough," she said.

It was not what Kael had expected. She had modeled the opening as a negotiation move — an offer, a threat, an assertion of power. A compliment was harder to respond to strategically.

"The system is legible," Kael said. "If you look carefully enough."

"Most people don't." Innes stepped forward and took a position that was parallel rather than confrontational — not facing Kael but beside her, both of them facing the wall. "Seven years you looked carefully, and you found one anomaly. Most analysts take much less time to find nothing."

"You built the anomaly detection into the system's reporting."

"Yes. To catch the ones who looked carefully." Innes was quiet for a moment. "You're angry. You're being very controlled about it."

"I'm not angry," Kael said. "Anger is imprecise."

Innes glanced at her sideways. "Forty-eight hours from the score drop to Zone 7-South. Twenty-two days to the first target package. Fourteen weeks since. Six architects. A complete data extraction under an orphaned session token. Eleven secondary sources. And now here." She paused. "If that's not anger, what is it."

"Work," Kael said.