The Archivist lived in a building that had been three different buildings before the corruption merged them. The ground floor was a library—shelves of physical books that occasionally reformatted themselves into scrolls or jade slips or, once, a stack of floppy disks that David recognized from photographs but had never seen in person. The second floor was a hospital ward, empty beds with monitors displaying vital signs for patients who didn’t exist. The third floor was a classroom, complete with desks and a chalkboard covered in equations that solved themselves and then erased the solutions.

  The Archivist occupied all three floors simultaneously.

  She was a woman—or had been, before the corruption had extended her existence across multiple spatial layers. Her body sat in a chair on the library floor, but her shadow was visible on the hospital floor above, cast by a light source that didn’t exist on that level, and her voice echoed in the classroom as if she were lecturing to invisible students.

  Her account tag read: [PLAYER — Status: SUSPENDED — Duration: 2,847 cycles].

  "Two thousand eight hundred and forty-seven cycles," David said, reading the tag. "How long is a cycle?"

  "Nobody knows anymore. The time-keeping functions are corrupted. It could be days. It could be years." The Archivist’s voice was calm, precise, with the particular clarity of someone who’d had a very long time to organize her thoughts. "You’re the first new arrival in... many cycles. And you’re flagged."

  "I’m flagged. I need to clear the flag, but I can’t do direct system manipulation without triggering the Anti-Virus."

  "And you think the Penitentiary holds the answer."

  "I think the Penitentiary is a collection of corrupted system code that the main architecture can’t process. Which means it contains exceptions—edge cases the system doesn’t know how to handle. And edge cases are vulnerabilities."

  The Archivist smiled. It was a strange expression on a face that had been rendered for almost three thousand cycles—the muscles moved correctly, but the skin texture lagged by a frame, creating a brief, uncanny-valley disconnect.

  "You think like a programmer."

  "I am a programmer."

  "Then you’ll understand what I’m about to show you." She stood from her chair and walked to a section of the library that David’s True Sight identified as the highest-density data region in the building. The shelves here were packed not with books but with crystallized rule fragments—each one a preserved sample of a rule the Warden had enforced during a patrol cycle.

  This text was taken from Royal Road. Help the author by reading the original version there.

  Thousands of them. Catalogued, labeled, organized by dungeon of origin, star rating, rule type, and compliance outcome.

  "I’ve been collecting these since I arrived," the Archivist said. "Every time the Warden patrols, I capture the rule it enforces and add it to the database. Over two thousand samples."

  David looked at the collection. His CS training saw it immediately: this was a dataset. A training set. With two thousand labeled samples of the Warden’s rule selection, he could build a predictive model—not a perfect one, given the corruption, but a probabilistic one that gave him better-than-random odds of predicting each patrol’s rule before the preview window.

  "You’ve been building a dataset for almost three thousand cycles. Why haven’t you used it to escape?"

  The Archivist’s smile faded. "Because predicting the rules isn’t the hard part. The hard part is the boundary. The one-way membrane. Nothing leaves the Penitentiary. I’ve tried every rule-based exploit I can think of. The membrane isn’t governed by dungeon rules—it’s a property of the corrupted space itself."

  "What about the Warden’s authority? It’s a system process. When it patrols, it must have access permissions that cross the boundary."

  "It does. But those permissions are attached to the Warden’s identity, not to the space. You’d need to become the Warden to inherit them."

  David was quiet for a moment. Then he looked at Michael.

  Michael was leaning against a shelf, his coin turning between his fingers. He’d been listening without interrupting—his preferred mode of operation, absorbing data while others generated it.

  "You’re going to try to hijack a system process," Michael said. Not a question.

  "I’m going to do something more precise than that." David turned back to the Archivist. "Show me your dataset. All two thousand samples. I need to find a pattern in the Warden’s rule loading sequence—specifically, I need to find a cycle where it loads a rule that contains an identity transfer or authority delegation clause."

  "A rule that lets you take control of the enforcer."

  "Exactly. Somewhere in the decommissioned dungeon database, there’s a rule that was designed to allow authority transfer—a boss fight where killing the boss means inheriting its title, or a succession mechanic, or a coup d’état event. If the Warden loads that rule during a patrol, I can trigger the compliance condition and inherit its permissions."

  "Without direct hacking. Without triggering the Anti-Virus."

  "Because I wouldn’t be modifying the system. I’d be playing by the rules. The corrupted, broken, randomly loaded rules of a garbage-dump prison warden—but rules nonetheless."

  The Archivist stared at him for a long time. Then she walked to her shelves and began pulling crystallized fragments from their slots, placing them on a table that flickered between oak and steel.

  "I’ve catalogued 2,847 rule cycles. Approximately 340 unique dungeon sources. Let’s start filtering."

  David sat down. Michael sat beside him. The Archivist spread the dataset across the table like a map of broken worlds.

  And David began to read.