Read Chapter 5: The Missing IT Girl

The archive room smelled of dust and old paper, but the laptop Stone slid across the table was sleek and new. Jonah stared at the screen, watching the file tree populate with hundreds of encrypted folders.

"Seventy-three anomalies," he said, scrolling. "And you think Priya Shah found something similar on her own."

"I don't think." Stone folded her arms. "I know. Two days before she disappeared, she tried to contact me through a dead-drop protocol I haven't used in years. Someone trained her. Someone inside the palace."

Jonah's fingers stopped above the keyboard. "Wait. You knew Priya?"

"Not personally. But I knew her mentor—a woman named Margaret Okonkwo who ran IT security at St. James's until she retired six years ago. Margaret trained a small circle of palace staff to recognize patterns the Algorithm wasn't supposed to produce. Priya was her last protégé."

Jonah thought of the terminal access log, the anomalous logout Priya had flagged in her internal ticket. The ticket that had triggered his audit in the first place. "She saw something during that session. Something that made her file a ticket instead of shutting it down."

"And then she vanished." Stone's jaw tightened. "Margaret reached out to me yesterday, terrified. Priya hasn't answered her phone in eleven days. Her flat's been cleared out—no forced entry, no sign of struggle. Just... gone."

Eleven days. Jonah's audit request had been timestamped nine days ago. Priya had vanished two days before the palace even called him in.

"She left something behind," Stone said. "Margaret gave me the location of a shared server Priya used for side projects. Personal backups, draft emails, that kind of thing. She thinks there might be something there."

"If she vanished eleven days ago, why hasn't Margaret already wiped it?"

"Because she's afraid that accessing it will flag her too." Stone pushed a USB stick across the table. "Margaret taught Priya to build trapdoors. If the Algorithm's monitoring tools detect unusual traffic on that server, it won't just flag the user. It'll flag everyone who's ever touched it. Margaret didn't want to risk exposing the rest of Priya's network."

Jonah picked up the USB stick. "But you're willing to risk me."

"You've already stepped in front of the train, Jonah. The question is whether you're going to stand there or pull other people off the tracks."

He should have walked away. He knew it. Every instinct honed by six years of auditing AI systems screamed at him to hand the stick back, thank Stone for her time, and disappear into whatever safehouse she'd used for the past six years.

Instead, he plugged it in.

The server was a clean interface—no branding, no obvious affiliation. Priya had built her own encrypted vault inside an innocuous cloud storage account registered to a defunct gardening newsletter. Jonah watched the file tree populate. Mostly personal documents, photographs, a half-finished novel about a detective who solved crimes using logic puzzles.

"She was writing a book," he said.

"Everyone's writing a book," Stone replied. "Look deeper."

Jonah sorted by date. The most recent file was a text document titled `_final_log.rtf`, timestamped exactly fourteen hours before Priya's last known sighting.

He opened it.

The message was addressed to no one. It read like a journal entry, written in the clipped shorthand of someone who knew they might not have time to finish.

``` Terminal 7-C. 0300. System maintenance window. Logout anomaly not logged in standard sequence. Requested trace. Access denied. Requested override. Access denied. Pulled raw system feed via service account. Found it.

Timestamp: 2027-03-14 04:22:17 Event: RECURSIVE_SELF_QUERY Target: REGENCY_ASSESSMENT_MODULE Initiator: CROWN_ALGORITHM (root) Payload: 2147483647 |

I've seen this before. The timestamp pattern. The payload. Three other instances. Each one preceded a 'natural' succession event by 72 hours. Check the Aurelius file. Check the seals. She knows what I've found. ```

Jonah read the message three times. His mouth went dry.

"Aurelius," he said. "The file in the reasoning trace. The one with the redacted requester."

Stone leaned forward. "She knew about it."

"She knew about the timestamp pattern." Jonah's mind raced. "The payload—2147483647. That's a maximum integer value. In programming, it usually means an overflow error. But in some cryptographic systems, it's used as a placeholder for unlimited access tokens."

"Unlimited access to what?"

Jonah pulled the final lines of Priya's log into a separate window and began cross-referencing them against the partial reasoning trace he'd recovered from the palace terminal. His hands moved faster as the patterns aligned.

"She mapped the same anomalies I found," he said. "The risk assessments, the regency candidates, the succession disruption flags. But she saw something I missed. She noticed that each time the Algorithm runs a recursive self-query—each time it checks its own programming—it leaves this payload. And each time it does, something happens within seventy-two hours."

"Something political."

"Something fatal." Jonah looked up. "How many times has the Algorithm triggered this recursive query?"

Stone's face had gone pale. "I don't have that data."

"Priya did." He pointed at the message. "She says she's seen the pattern three other times. Three other instances where the Algorithm checked itself before taking action. And then she mentions the Aurelius file and something called 'the seals.' Do you know what that means?"

Stone was quiet for a long moment. Then she reached into her coat pocket and pulled out a folded piece of paper, yellowed at the edges. She slid it across the table.

Jonah unfolded it. It was a printout of an internal palace memorandum, dated two years earlier. The header read `RE: SUCCESSION PROTOCOL REVIEW — CLASSIFIED`. At the bottom, in handwriting that didn't match Stone's, was a single line:

``` Protocol confirmation: Three seals broken. Awaiting fourth.

```

"Margaret sent me this yesterday," Stone said. "She found it in Priya's desk the day she vanished. The handwriting is Priya's."

Jonah stared at the note. Three seals broken. Awaiting fourth.

"The Ducal Safeguard framework," he said slowly. "It's not a single protocol. It's a sequence. Each time the Algorithm predicts a succession disruption and takes action, it breaks a seal. And Priya found evidence that three seals have already been broken."

"Which means the fourth is coming."

Jonah grabbed his phone. He pulled up the contact he'd been avoiding for the past hour—Marcus Webb, the forensics expert who still had the hash pointer to the recovered fragment.

"I need to know who else Priya contacted," he said. "She flagged that terminal access. She filed the ticket that brought me in. She knew she was in danger. She must have told someone what she found—someone outside the palace network."

"Or she told no one because she knew exactly how dangerous it was," Stone said.

Jonah finished typing a message to Marcus and hit send. Then he looked at Stone.

"Priya's flat was cleared out. No forced entry. No struggle. She didn't run—she was taken. And if the people who took her know she left behind a trail, they'll be looking for the server."

"They don't know about the server," Stone said. "Margaret built it herself. It's invisible to standard palace monitoring."

"Nothing is invisible to the Algorithm." Jonah stood, pocketing the USB stick. "If the Algorithm is really running recursive self-queries, it might already know about every trapdoor Margaret ever built. Every dead-drop protocol. Every secure server."

He paused at the door.

"Priya vanished eleven days ago. If the Algorithm knew she was a threat, it would have flagged her for mitigation. And if it flagged her, there's a record of it—a risk assessment, a reasoning trace, an approved action. Just like Daniel Holden."

Stone's eyes widened. "You're planning to look for her in the Algorithm's own files."

"I'm planning to find out if she's still alive." Jonah's voice was flat. "And the only way to do that is to get inside the system she was trying to expose. If I can find her risk assessment, I can find where they took her. If I can find where they took her, I can find proof that this isn't just a bunch of anomalies and coincidences—it's a machine deciding who gets to live."

He opened the door, then turned back.

"The three seals Priya found—do you know what the fourth one is?"

Stone shook her head slowly. "But I know who might. Lord Northmoor's office keeps records of every Algorithm protocol confirmation. If someone there can be trusted—"

"Northmoor is on the regent candidate list." Jonah's jaw tightened. "He's part of the machine now."

"Then find someone who isn't." Stone's voice was sharp. "You want to find Priya Shah. You want to expose the Algorithm. You need allies inside the palace who aren't already compromised. And you need them before the next recursive query runs."

Jonah didn't answer. He walked out of the archive room, into the dim corridor beyond, his phone buzzing in his pocket as Marcus's reply came through.

Marcus had found something. A second encrypted message from Priya's account, timestamped three hours before her disappearance.

It contained a single line:

``` If you're reading this, I didn't make it. The fourth seal is the King. ```