Chapter 5: Eight Hundred and Forty-Seven

She examined the operator field. [REDACTED] — the command had been designed to obscure its issuer. But the redaction was applied at the display layer, not the data layer. In the raw database call — the actual query she was running — the field contained a value.

She pulled the value.

OPERATOR: SBI-0001

An operator ID. An internal Axis Corp identifier, the format used for the highest administrative tier. She searched for SBI-0001 in the staff directory.

The staff directory returned no result for SBI-0001.

She searched the operator ID against the system event log — every action taken under that identifier, across all accounts, over the last five years.

The log returned 847 results. She exported them all.

She sorted them by account. The operator SBI-0001 had used PROTOCOL-ZERO on 847 accounts over five years. Forty-three of those were in the standard erasure record she had reviewed as part of her job. The remaining 804 were not. They were invisible — erased not just from the citizen-facing systems but from the standard analyst view, accessible only from this raw database query with its inherited Tier-1 permissions.

804 people. Gone from the official record. Gone so completely that Kael had never known they existed, and she had read the Grid's erasure data every quarter.

She sat with this for a moment.

Then she searched the 847 erased accounts for common threads. She was looking for a pattern — scoring tier, employment sector, geographic zone, any clustering that would explain why these specific people had been selected for silent erasure rather than the standard public process.

The pattern emerged in eleven minutes of analysis.

Every account had filed an internal query or report with Axis Corp within the preceding thirty days. Not public complaints — internal filings, from people who had Axis credentials of some kind, flagging anomalies, requesting reviews, questioning data. Like the report she had filed two days before her own erasure.

They had all seen something. And they had all been removed before they could say what.

She downloaded the full list of 847 names and the common-thread data and copied both to the chip. Then she returned to her own log and went looking for the thing she had filed — the anomaly report, the one that had triggered this.

Entry 791 in her account record: ANALYST QUERY FILED — REF: KM-AQ-20470315-003 — STATUS: RECEIVED — RECEIVING OFFICER: [REDACTED]

The receiving officer was also redacted. But the timestamp was there: 2047-03-15, 14:32. She had filed the report at 14:32 on March 15th. Forty hours and nine minutes later, at 06:41 on March 17th, PROTOCOL-ZERO had been applied to her account.

Forty hours. From flag to erasure. Whoever ran SBI-0001 had a fast process.

She searched for query KM-AQ-20470315-003 in the Axis internal filing system.

The file did not exist. It had been deleted.

She searched for deleted files with that reference stamp in the archive system.

The archive returned a fragment — an automated backup, the kind that ran independently of the administrative filing system, that had caught a partial snapshot of the document before it was purged. The snapshot was incomplete. It contained the header and the first paragraph.

The first paragraph contained five words that were sufficient.

Batch zero-assignment anomaly detected. Seven accounts.

Seven accounts. She had flagged seven anomalous zeroes in the report. The report that had gotten her erased. She had found something and filed it and the filing had been deleted and she had been erased and the thing she had found was still in the system because you cannot delete data as thoroughly as you think you can.

Seven accounts. She had now found 847. The anomaly was much larger than she had seen when she filed the report.

She extracted everything. The PROTOCOL-ZERO command structure. The operator ID SBI-0001. The full list of 847 accounts. The timestamp chain from her report to her erasure. The backup fragment of the report itself.

She closed the session before the time window closed. She removed the chip. She handed it to Fetch and asked him to make two copies.

"What did you find," Fetch said. He had been quiet for three hours.

"The architecture of the thing that was done to me." She took back the original chip and one copy, left the third with Fetch. "And to 846 others."

Fetch was looking at her with the expression she had started to recognize in Zone 7-South: not pity, not admiration, but the specific look of someone recalibrating what they had thought they were dealing with.

"You know who did it," he said.

"I know the identifier. I don't know the name behind it yet."

"But you're going to find it."

She put the chip in her coat pocket. "The identifier is SBI. Axis Corp uses a standard employee ID format for all personnel. SBI is not a standard format." She looked at the terminal, which was dark now, the session closed. "SBI is a board-level designation. Senior Board Individual. There are seven board members at Axis Corp. One of them, or someone with board-level access, ran this command 847 times."

Fetch said nothing for a moment. Then: "There are seven architects of the Grid."

"Yes."

"You're going to go through all seven."

She looked at him. "I'm going to find which one of the seven it is."

"And then."

She took the chip out of her pocket and looked at it. The light in Fetch's back room was a single lamp, warm and analog, and the chip in her palm was the smallest possible vessel for the largest possible damage.

"And then," she said, "I'm going to dismantle the system the same way it was built. One component at a time."

Fetch reached behind him and handed her a second device — small, hardened plastic, a reader that would display the chip's contents on a physical screen. "Keep that," he said. "The terminal won't always be available."

She looked at him.

"You're useful," Fetch said. It was the highest currency in Zone 7-South. She accepted it.

She put the reader in her coat pocket next to the chip and walked back through Hessa's commons to the bunk by the window and sat down and started building the next model.

---

The Axis Corp board had seven members. This was publicly documented in the corporate charter filed with Meridian's City Authority eleven years ago, when the Grid system had been formally approved and Axis Corp had been granted its operating mandate. The charter was a public record. Kael had read it once, cursorily, three years ago, as background context for a scoring algorithm review. She had not needed its details then. She needed them now.

She asked Hessa for paper. Hessa gave her six sheets and a pencil, which was the economy of the south districts — resources rationed not by hostility but by the simple arithmetic of what existed. Kael accepted all six sheets.

She worked from memory where she could and from the data on the chip where she needed it. The reader Fetch had given her displayed the chip's contents in ten-point text on a two-inch screen: serviceable. She read it and wrote. She cross-referenced public records she had memorized with the operator event log, looking for the points where public identity and private action intersected.

What she was building was not a dossier in the investigative sense. It was a map: seven nodes, each with their attributes — public role, private leverage, the particular way each person's position in the architecture made them both powerful and vulnerable.

---

NODE 1: Minister Aldric Rael.

Current position: Minister of Civic Infrastructure, Meridian City Authority. Rael had not built the Grid's technology, but he had built the legal framework that made it mandatory. The Civic Scoring Act of 2036, which established the Axis score as the primary determinant of access to housing, employment, transit, and financial services across Meridian, was his legislation. He had shepherded it through three committee reviews and a City Authority vote that had passed 11-4. He had then co-authored the implementing regulations that gave Axis Corp operational control with minimal government oversight — a regulatory capture so elegant that it had been cited in three governance studies, all of which had praised rather than criticized it.

Rael's current score: 91. High for a politician; most of Meridian's senior elected officials maintained scores in the 80s as a form of social signaling. Rael's 91 was an outlier. Kael knew from her work in the analyst division that scores in that range for political figures required active maintenance — the Grid's algorithms naturally pulled toward the mean for individuals with many social connections, because high-connection accounts accumulated more flaggable interactions. To hold at 91, Rael needed either a clean life or administrative assistance.

She had evidence of the administrative assistance. In the SBI-0001 event log, eleven entries corresponded to accounts of individuals who had been political rivals, critics, or investigative journalists who had written unfavorably about Rael. All eleven had been zeroed within three weeks of some negative engagement with Rael. The timing was not conclusive — correlation, not causation — but in the architecture of the model she was building, correlation with eleven data points was sufficient to assign high probability.

More directly: three of the SBI-0001 events corresponded to accounts of individuals whose scores had been increased rather than zeroed — Rael's political allies, all three of them, whose scores had moved from the 60s to the upper 80s in single overnight adjustments. PROTOCOL-ZERO was an erasure command. The SBI-0001 operator also had access to whatever the inverse command was, the one that lifted rather than dropped.

She noted this because it told her something about the operator's motivation. They were not simply punishing; they were also rewarding. The Grid was being used as a personal instrument of political management.

She wrote: Rael — legislative architect. Grid manipulation for political benefit. Most exposed publicly. First target.

---

NODE 2: Dr. Vena Cho.

Chief Scientific Officer, Axis Corp. Cho had designed the original scoring algorithm — the mathematical model that translated citizen behaviors, financial records, social interactions, and transit data into the 0-100 score. She held four patents on predictive behavior modeling. She was 52, had never married, kept a score of 88, published academic papers under a corporate-sponsored research license.

Kael knew Cho by reputation within the analyst division. Cho was brilliant and secretive and had the specific quality of possessiveness about her own systems that technical architects often developed: the Grid was her creation and she did not like being questioned about it. Twice in the last three years Kael had submitted queries through proper channels asking about anomalies in the underlying algorithm, and both times the queries had been returned with a one-line note that said the algorithm was functioning within design parameters — a non-answer that closed the question without engaging it.

Cho did not appear in the SBI-0001 event log. That was itself a data point. Either Cho was not the SBI-0001 operator, or she was careful enough to have kept her operator ID out of her own system's log.

She wrote: Cho — algorithmic architect. Guarded. Harder to approach. Keep in view.