Chapter 4: The Terminal

The interface took two days to find.

Not because the Zero community lacked technology — they had more than Kael expected, scavenged and jury-rigged and routed through signal loops that the Grid's surveillance infrastructure did not monitor because the Grid did not believe anything worth monitoring existed down here — but because Kael had to earn the access to it. This was Pov's calculus, and it was sound: you did not hand a forty-eight-hour refugee your most valuable tool until the refugee had demonstrated they were not a liability.

She demonstrated it by doing what she had always done. She analyzed.

In the first forty-eight hours she learned the Grid surveyor routes by walking them herself, carefully, three complete circuits. She produced a paper map — Hessa had a supply of paper, hoarded and rationed, another thing Kael would not have predicted — with times and coverage overlaps marked. She identified a new surveillance pattern: a fourth surveyor, not in the community's existing knowledge base, running an offset route through the eastern edge of Zone 7-South.

She presented the map to Pov on the second morning.

Pov looked at it for a long time without speaking, which in Pov's register was equivalent to effusive praise.

"There's a terminal," Pov said. "Back room. Off-Grid hardware, modified. One person knows how to operate it. His name is Fetch. He decides who uses it."

"What does Fetch want," Kael said.

"For you? Information. If you know the Grid's internal architecture, he wants everything you're willing to give."

"I'm willing to give it after I've extracted what I need."

Pov almost smiled. "I'll tell him that. He'll probably respect it."

---

Fetch was sixty, wiry, with the specific nervous energy of someone who had been underground long enough to have developed a constant situational vigilance. He had been a network engineer before his zero — he offered this without elaboration, as a credential, which Kael accepted the same way — and he maintained the terminal the way Hessa maintained the communal kitchen: as a personal domain that functioned because he understood it better than anyone else and refused to let it deteriorate.

The terminal was a pre-Grid workstation that Fetch had retrofitted with components sourced from three different generations of discarded city infrastructure. It ran an operating system that had not been updated in nine years, which meant it operated outside the current Grid protocol stack entirely, invisible to the network it was probing because it spoke a slightly wrong version of the language — close enough to parse, wrong enough to avoid the authentication handshakes that would flag an unauthorized access.

"You need the Axis Core network," Kael said, looking at the terminal.

"Can you get in."

"Not directly. But I have a chip with cached credentials from when I was inside the network. A valid session token that won't have been revoked yet because the revocation cascade focuses on external access points — the smartband interface, the citizen portal. The internal analyst credential is a different certificate chain." She paused. "It has a window. Probably three to five days from erasure before the system runs a full audit and catches the orphaned session."

Fetch looked at the chip in her hand. "How long ago were you erased."

"Two days."

Fetch sat down at the terminal. "Then we have today."

---

The session opened.

Kael had expected resistance — had modeled three probable failure points in the authentication sequence — but the token worked on the first attempt, which told her something important: the person who had zeroed her had not thought to manually revoke her internal credentials separately from the citizen-facing cascade. They had pulled the standard erasure lever and assumed the automated systems would handle the rest. They had not checked the analyst certificate chain.

That was an oversight. Oversights were data.

She navigated the Axis Core network the way she had navigated it for seven years: precisely, without wasted motion, pulling only what she came for. Fetch watched her work in silence, which she appreciated. He was taking notes on paper. She let him.

First she pulled her own account record. The complete version, the backend view that citizens never saw — not the sanitized dashboard but the raw event log, the full history of every score adjustment, every flag, every administrative action taken on account KM-4471-ALPHA over seven years.

The log was 847 lines long. She started from the bottom, the most recent entries, and read backward through time.

Entry 847: ADMIN ACTION — SCORE RESET — NEW VALUE: 0 — OPERATOR: [REDACTED] — TIMESTAMP: 2047-03-17 06:41:22 — AUTHORIZATION: PROTOCOL-ZERO COMMAND — AUTH LEVEL: TIER-1

She stopped.

Protocol-Zero Command.

She had never seen that term in seven years at Axis Corp. She knew the Grid's scoring protocols by function code and name — PROTOCOL-ONE was the standard scoring algorithm, PROTOCOL-TWO was the appeals adjudication process, PROTOCOL-THREE through NINE were various automation and audit functions. PROTOCOL-ZERO was not in the documentation she had access to.

But it was in the backend log. It existed. Someone had used it.

She copied the entry. Then she went looking for PROTOCOL-ZERO in the system's command library.

It took twenty-two minutes to find. It was not in the standard command library. It was in a protected subroutine stored in the Tier-1 administrative partition — a partition she had not had access to as a senior analyst, but which the orphaned session token apparently reached via a permissions inheritance flaw she had not previously known existed. She noted that flaw. It was the kind of thing she would have flagged in a security review three months ago. She did not file the report now.

PROTOCOL-ZERO was a manual erasure command. Not the standard zero-assignment process, which required a three-step review chain and left an audit trail. PROTOCOL-ZERO was a direct override: it bypassed the review chain, bypassed the audit trail, and wrote a single final entry into the account log before closing the record permanently. The final entry was the one she had just read.

But it did not completely close the record. The event log remained — a standard logging function that PROTOCOL-ZERO's designers had apparently failed to account for, or had underestimated, or had considered acceptable because the logs required Tier-1 access to read and Tier-1 was presumed to be the same people who would use the command.

They had not anticipated that an erased analyst would access their own log from a compromised session token on a nine-year-old off-Grid terminal in Zone 7-South.