It took David eleven hours to process the Archivist’s dataset.

  Not because the volume was overwhelming—his SSS-rank cognitive capacity could handle the throughput. But because corrupted data required interpretation, and interpretation required context, and context for rules from dungeons he’d never entered required inference from partial information. It was the most demanding analytical task he’d performed since entering the Rules World, and by the end of it, his nose was bleeding and his hands were shaking and his mental reserves were at 15%.

  Michael helped. Not by analyzing the rules—he didn’t have the talent for that—but by organizing the physical fragments, maintaining a sortable index, bringing David water from a tap that only worked on Tuesdays and occasionally dispensed something that was not water, and gently redirecting David’s attention when the cognitive strain caused his focus to drift.

  A debugger watching the blind spots.

  The Archivist helped more directly. Her 2,847 cycles of observation had given her an intuitive understanding of the Warden’s patterns that supplemented David’s analytical approach. Where David saw data, she saw behavior. Where he modeled probability distributions, she felt rhythms.

  Together, they found it.

  Rule fragment #1,892. Source: a decommissioned 7-Star dungeon called "The Throne of Ashes." The Archivist had captured it during a patrol 400 cycles ago. The Warden had loaded it, enforced it, and moved on. No one had survived compliance because no one had understood what the rule required.

  The fragment read:

  [Rule 11 of "The Throne of Ashes": When the throne is vacant and the claimant stands in the sovereign’s shadow, the claimant may speak the words of succession. If the words are accepted, authority transfers. If rejected, the claimant is unmade.]

  "A succession mechanic," David said, holding the crystallized fragment up to the light. "The Throne of Ashes was a dungeon built around a power-transfer event. Rule 11 is the coup clause—it lets a player challenge the dungeon’s boss for authority."

  "The Warden loaded this rule 400 cycles ago," the Archivist said. "There’s no guarantee it will load again."

  "It doesn’t need to load the exact same rule. It needs to load any rule with a compatible logical structure—an authority-transfer conditional. The Warden’s database contains fragments from 340 dungeons. At least seven of them have succession or authority-transfer mechanics." David set the fragment down. "Based on the loading frequency distribution, one of those seven should come up within the next fifty patrol cycles. Probably sooner."

  "And when it does?"

  "I stand in the Warden’s shadow—which is a metaphorical requirement that probably translates to physical proximity during the rule’s execution window. I speak the words of succession—which will be dungeon-specific and need to be derived from whatever partial rule text is visible in the preview. And I either inherit the Warden’s system permissions or I’m ‘unmade,’ which is the dungeon’s way of saying deleted."

  "Fifty-fifty," Michael said from behind them, his coin turning between his fingers.

  "Better than fifty-fifty if I read the preview correctly. Worse than fifty-fifty if I don’t."

  "And if you succeed? If you inherit the Warden’s permissions?"

  David looked at the Archivist. "Then I become a system process. Not a player pretending to be an administrator—an actual, recognized system entity with permissions that the Anti-Virus can’t flag, because they’re legitimate. I can leave the Penitentiary. I can operate in the Abyss without the Hounds tracking me. I can access Consortium infrastructure without spoofing credentials."

  "You’d be a Trojan horse," the Archivist said. "A human consciousness wearing a system process’s identity."

  "Exactly."

  The Archivist was quiet for a long time. When she spoke, her voice had lost its academic composure. Something older was underneath—something that sounded like hope, and like the fear of hope.

  "If you become the Warden... the boundary membrane answers to the Warden’s authority. You could open it."

  "I could open it."

  "The inmates could leave."

  David looked at her. The woman who’d spent 2,847 cycles cataloguing rules in a prison for things the system couldn’t delete, building a dataset that she’d never been able to use because the problem wasn’t prediction—it was authority.

  You could be reading stolen content. Head to Royal Road for the genuine story.

  "Everyone leaves," David said. "That’s the plan."

  The ground vibrated. The sky tiles flickered. The loading tone began.

  David stood up. "That’s the next patrol. Let’s see what it’s running."

  He walked to the center of the plaza, where the Warden’s approach would bring it closest. Michael and the Archivist followed at a distance.

  The preview window opened. Two seconds. Fragmentary code assembling in the air.

  David read it.

  Not a succession rule. A temperature regulation rule from a decommissioned arctic dungeon. Compliance requirement: maintain body temperature above 35°C for 90 seconds. David huddled in his coat, activated his SSS-rank thermoregulation, and rode it out.

  The Warden passed. The cold faded.

  "Not this time," David said, returning to the library. "We wait for the next one."

  And so they waited. Patrol after patrol. David read each preview, complied with each rule, survived each cycle. The rules came in random order: a silence rule, a counting rule, a rule that required all entities to face magnetic north (which shifted every three seconds in the Penitentiary’s corrupted geography), a rule that prohibited the color blue (David covered his jeans with his coat).

  Each patrol that wasn’t a succession rule was data. David added it to his model. The probability distribution narrowed.

  On the fourteenth patrol, the preview window showed fragments from a 6-Star dungeon called "The Parliament of Shadows."

  [...Rule 8: When the Speaker falls silent, the first voice to speak inherits the Speaker’s mandate...]

  "This is it," David said. His voice was calm. His heart rate was not. "Authority transfer. Voice-activated. I need to be the first to speak after the Warden’s tone ends."

  The Warden entered the plaza. Its geometric form cycled through impossible shapes. The tone sustained—the rule’s audio trigger, the equivalent of the Speaker’s voice.

  David stood in the Warden’s path. Close enough that the entity’s corrupted geometry grazed his perception field, close enough that his True Sight could barely process the density of scrolling code on its surface.

  The tone stopped.

  Silence. Absolute silence. The entire Penitentiary held its breath.

  David spoke.

  "I claim the Speaker’s mandate."

  The words left his mouth and entered the system’s execution environment. For a fraction of a second—a single processing cycle—nothing happened. The rule was evaluating. Checking the claimant against the succession criteria. Verifying that the Warden’s "silence" condition had been met. Determining whether to transfer or to unmake.

  David felt it: a cold probe in his consciousness, as if the system was reading his account file, checking his permissions, assessing whether he was eligible for the role he was claiming. The Anti-Virus flag pulsed in his interface. The system saw it. The system considered it.

  And then the rule executed.

  Not because David had hacked it. Not because he’d exploited a vulnerability or spoofed a credential or injected code. Because the rule said what it said, and David had complied with its conditions, and the system—even corrupted, even broken, even running in a garbage dump at the edge of reality—followed its own rules.

  [Authority Transfer: ACCEPTED.]

  [System Process "Penitentiary Warden" — Identity transferred to Player No. 7749.]

  [Administrative permissions updated.]

  [Anti-Virus flag status: RESOLVED. Player recognized as authorized system entity.]

  The geometric Warden’s form began to decohere. Its shapes slowed, simplified, and dissolved into raw data that streamed toward David—not attacking, not invading, but merging. The permissions settled into his system interface like new software being installed: access to the Penitentiary’s boundary membrane, authority over the local rule engine, and—most critically—a clean system identity that the Anti-Virus recognized as legitimate.

  David stood in the center of the plaza, his eyes closed, feeling the new permissions integrate. When he opened them, the red warning icon was gone. In its place: a clean, blue designation.

  [Player No. 7749 — System Role: Warden (Ashen Penitentiary)]

  Michael was the first to speak. "Did it work?"

  David raised his hand. The boundary membrane—invisible, omnipresent, the one-way wall that had trapped every inmate for thousands of cycles—shimmered. Became visible. And then, responding to his authority, opened.

  A doorway. Leading outward. To the Abyss. To the Midnight Express. To everything that came next.

  Around the plaza, the inmates were staring. The woman with translucent arms. The man with the independent shadow. The child reading the blank book. The old NPC Warden who’d guided David here.

  And the Archivist, standing at the edge of the crowd, 2,847 cycles of catalogued data behind her, tears running down a face that rendered them one frame late.

  "The boundary is open," David said. His voice carried across the broken city, amplified not by magic but by the Warden’s authority, which treated his words as system announcements. "Anyone who wants to leave can leave. The exit is real. I won’t close it."

  He turned to Michael. "Get back to the train. Start the engine. We’re leaving."

  "And them?" Michael gestured at the inmates.

  "The exit stays open. They choose for themselves. I’m not their warden. I just inherited the title."

  He began walking toward the boundary. Behind him, slowly at first and then in a flood, the inmates of the Ashen Penitentiary began to follow.