"Surprisingly" being relative when you had a resistance member who worked as a filing clerk and Code Vision that let you see security vulnerabilities like they were highlighted in neon.
I sat in my room at The Wanderer's Rest, surrounded by tax records going back ten years. Not noble tax records—those were predictably corrupt and unhelpful. No, these were system maintenance records. The magical equivalent of infrastructure reports. Documentation of every time the Covenant Operating System had experienced failures, degradations, or critical errors that required administrative intervention.
And nobody had thought to correlate them with the privilege grant timeline.
Until now.
"You've been awake for sixteen hours," Pip said from the doorway.
"I know."
"Corvina says you promised to sleep."
"I will. After I finish this section." I didn't look up from the timeline I was constructing. "There's a pattern here. I can feel it."
Pip entered, set down tea I hadn't asked for but probably needed, and looked at my work. His Code Vision was developing nicely—he could probably see about fifty-five percent of magical structures now, maybe sixty on a good day. But more importantly, he was learning to think like a hacker. To see patterns in data.
"What pattern?" he asked.
I pointed at the timeline. "System failure events. Magical infrastructure degrading. When magic stops working properly in certain areas." I traced my finger along the dates. "Five years ago: Major ward collapse in Sanctum City's Noble Quarter. Emergency repairs required. Three nobles granted system privileges the following week."
"Coincidence?"
"Keep listening. Four years ago: Mage Academy experiences mass spell failure. Students' magic not responding correctly. Takes two weeks to stabilize. Six nobles granted privileges during the crisis."
Pip leaned closer, studying the timeline. "And you think the privilege grants are connected to the failures?"
"I think the privilege grants are responses to the failures." I pulled out another document—the privilege registry data we'd stolen from Cromwell. "Look at the dates. Every time there's a major system failure, privilege grants spike in the following weeks. It's not random. It's systematic."
I'd been cross-referencing for hours. Tax records showing system failures. Privilege registry showing grant dates. Noble financial records showing who paid and when.
And the correlation was perfect.
SYSTEM FAILURE EVENT ANALYSIS
Year 1243, Q2:
- Event: Ward system collapse, Eastern District
- Severity: CRITICAL (45-minute full failure)
- Privileges Granted: 8 (within 2 weeks)
- Recipients: All in affected district
Year 1243, Q4:
- Event: Mana network disruption, Southern Province
- Severity: MAJOR (degraded service 3 days)
- Privileges Granted: 12 (within 1 week)
- Recipients: All in affected province
Year 1244, Q1:
- Event: Spell amplification failure, Mage Academy
- Severity: MAJOR (2-week instability)
- Privileges Granted: 6 (during crisis)
- Recipients: All Academy staff or donors
CORRELATION: 94.7%
CONCLUSION: Privilege grants respond to system failures
HYPOTHESIS: Privileges are emergency access to compensate for degraded infrastructure
"They're not selling privileges for profit," I said slowly, the understanding crystallizing. "They're selling them because the system is breaking down. When infrastructure fails, they grant nobles elevated access so they can maintain baseline functionality despite the degradation."
Pip stared at the timeline. "That's... that's worse than corruption."
"Much worse. Corruption is abusing a functional system. This is desperately patching a failing system with illegal workarounds because you don't know how to actually fix it." I started pulling out more documents. "And look at the frequency. Five years ago, there were two major system failures. Four years ago, five failures. Three years ago, eight. Two years ago, fifteen. Last year, thirty-two."
"It's accelerating."
"Exponentially." I drew a graph showing the failure rate. A clear exponential curve. "The Covenant Operating System is collapsing. Slowly, but consistently. And instead of fixing the underlying problems, the gods are selling temporary access privileges to wealthy nobles so they can work around the failures."
"Can you prove it? That the system is failing?"
"I can prove the correlation between failures and privilege grants. I can show that grants cluster around crisis events. I can demonstrate the acceleration pattern." I gestured at all the evidence. "But proving causation—proving that privileges are granted specifically to compensate for system failures—that requires internal communications. Meeting minutes. Divine correspondence."
"Which we don't have."
"Not yet." I started organizing the timeline into a presentable format. "But we have enough for pattern demonstration. Any statistician would look at this correlation and conclude there's a relationship. The question isn't whether they're connected—it's what the connection means."
Pip picked up one of the tax documents, studying it with his developing Code Vision. "What does this say? The magical annotation on the side?"
I looked where he was pointing. Saw the coded notation—looked like standard administrative markup, probably invisible to normal vision.
"Priority classification," I read. "System maintenance records are categorized by urgency. Green for minor issues, yellow for concerning trends, red for critical failures requiring immediate attention."
"And this one is...?"
I checked the color coding through my Code Vision. "Red. Marked as critical. Dated two months ago." I read the full entry. "Critical mana network degradation in the Capital District. Affecting approximately 23% of magical infrastructure. Emergency intervention required. Status: Temporarily stabilized through privilege access expansion."
There it was. Explicit acknowledgment. The system failures were being addressed through privilege grants. Not as corruption, but as emergency measures.
"So they're admitting it," Pip said. "In their own records. That they're using privilege grants as system patches."
"They're not admitting it publicly. This is internal documentation. Administrative records that aren't supposed to be seen by civilians." I pulled out another dozen documents with similar markings. "But yes, their internal communications show they're fully aware this is happening. They know the system is failing. They know privileges are emergency measures. They just don't want anyone else to know."
"Why not? If the system is failing, wouldn't they want help? Want people working on fixing it?"
"Because that would mean admitting they don't know how to fix it themselves." I thought about The Compiler, about Administrator Prime, about gods who inherited a system they didn't fully understand. "They're supposed to be all-powerful. All-knowing. Divine administrators maintaining perfect order. If they admit the system is failing and they can't fix it, what does that make them?"
"Incompetent?"
"Frauds. Gods who aren't actually divine, just powerful mages running someone else's code. That's a legitimacy crisis they can't afford." I started cataloging the evidence. "So instead, they patch. They grant emergency privileges. They charge nobles for the service to offset costs. And they hope nobody notices the pattern."
"But you noticed."
"I notice everything. It's compulsive." I pulled out a fresh sheet of paper, started mapping the full conspiracy. "Here's what I think is actually happening. The Covenant Operating System was installed ten thousand years ago by the Precursors. Complex, sophisticated, beyond anything the current gods could create. But it's degrading. Memory leaks, accumulated errors, architectural decay. The gods don't understand the source code well enough to fix the fundamental problems. So they apply patches. Temporary fixes. Emergency measures."
"The privilege grants."
"Exactly. When infrastructure fails in an area, they grant elevated access to local nobles. The nobles get amplified magic, override authority, enhanced system access. This compensates for the degraded infrastructure—they can work around the failures because they have higher-level permissions." I drew the architecture. "It's like if your computer was crashing constantly, and instead of fixing the operating system, you just gave certain programs admin privileges so they could bypass the broken parts."
"That sounds unstable."
"It is unstable. It's a terrible solution. But it's the only solution they have if they can't actually repair the underlying system." I added more details to my diagram. "And it works, temporarily. Nobles with privileges can function normally despite infrastructure degradation. Everyone else experiences degraded magic, but that's blamed on natural variation or insufficient training or whatever excuse makes sense."
Stolen from Royal Road, this story should be reported if encountered on Amazon.
"Until the system degrades so much that privileges aren't enough."
"Right. Eventually, you can't patch your way around fundamental architecture failures. The whole system crashes. Everything stops working." I looked at the exponential curve I'd drawn. "And based on this acceleration pattern, we're maybe twenty years from total failure. Maybe less."
Pip was quiet for a long moment, processing the implications.
"So the revolution isn't just about corruption," he said finally. "It's about preventing system collapse."
"It's about both. The corruption exists—they're profiting from the failure. But the underlying problem is the failure itself. We need to expose the corruption to discredit their authority. But we also need to fix the actual system before it crashes completely."
"Can you fix it?"
I thought about the Covenant Operating System. Ten thousand years old. Failing infrastructure. Accumulated errors. Memory leaks. A runtime environment managing an entire world's magical physics.
"I don't know," I admitted. "I can see the code. I can identify problems. But fixing a failing OS at this scale? That's a systems architecture challenge beyond anything I've ever attempted. I'd need access to the source code. The original installation documentation. The Root Directory where the core system files are stored."
"Which is in the Palace."
"Which is in the Palace. Defended by gods. Protected by the strongest security in existence." I smiled without humor. "But yes. If we're going to actually save this world—not just expose corruption, but prevent total system collapse—we need to get into the Root Directory. Access the Covenant's source code. Understand what the Precursors built and why it's failing."
"That's a bigger goal than revolution."
"Revolution is just the first step. Discredit the current administrators. Remove them from power. Then we can actually access the system maintenance tools and fix the problems they've been ignoring." I started packing up the evidence. "But first things first. We present this to the resistance at Emberfall. Show them it's not just corruption—it's existential threat. The system is failing and we're running out of time to fix it."
A knock on the door. Corvina entered, took one look at the evidence spread across my room, and sighed.
"You didn't sleep," she said.
"I found the pattern."
"Of course you did." She approached the table, studying the timeline. "Show me."
I walked her through it. System failures correlating with privilege grants. The acceleration pattern. The internal records admitting privileges were emergency measures. The evidence that the Covenant Operating System was fundamentally failing.
Corvina listened in silence, her expression growing darker as the implications became clear.
"Twenty years until total collapse," she said when I finished.
"Maybe less. The acceleration is exponential. Could be faster than my conservative estimate."
"And the gods know."
"The gods know. They've known for years. They're just hoping they can patch their way to a solution before it becomes public." I gestured at the evidence. "This changes the resistance's timeline. We're not just fighting corruption on principle. We're racing against system failure."
"Does Edrin know?"
"Not yet. I wanted to organize the evidence before presenting it." I started gathering documents. "But he needs to see this. Everyone needs to see this. The Emberfall gathering—we're not just voting on revolution. We're deciding whether to sit back and watch the world crash or actually do something about it."
"That's not a choice. That's a fait accompli."
"Exactly." I picked up the timeline, the tax records, the correlation analysis. "Let's go talk to Edrin."
We found Edrin in the inn's common room, studying maps with Thorne. When we spread our evidence across his table, his expression shifted from interested to concerned to alarmed over the course of thirty seconds.
"System collapse," he said. Not a question.
"Within twenty years. Probably less." I showed him the acceleration curve. "The privilege grants aren't just corruption. They're desperate measures to compensate for failing infrastructure. Every time the system experiences a critical failure, nobles in the affected area are granted elevated access so they can work around the degradation."
Edrin studied the timeline, the tax records, the internal documentation. His eyes—sharp despite his age, hardened by twenty years of fighting—tracked across the evidence with systematic precision.
"This is worse than I thought," he said finally.
"You suspected system failure?"
"I suspected something was wrong with the underlying magical infrastructure. Spells that used to work reliably becoming unstable. Wards that required more maintenance. Magic feeling less responsive." He pointed at the acceleration curve. "But I thought it was environmental. Ambient mana degradation. Something natural. Not active system collapse."
"It's both. The Covenant Operating System manages ambient mana distribution. If the system is failing, mana becomes less available, less reliable, less effective. What you've been experiencing as environmental degradation is actually infrastructure failure manifesting in the magical ecosystem."
"Can it be fixed?"
"With access to the source code, maybe. With understanding of the Precursor's original architecture, possibly. But the current gods don't have that access or understanding. They're running inherited code they can't repair." I laid out my diagram of the system architecture. "The only permanent solution is accessing the Root Directory. Understanding how the Covenant was built. Identifying the failure points. Implementing actual fixes instead of temporary patches."
"Which requires removing the current administration."
"Which requires removing the current administration," I confirmed. "Because they'll never voluntarily admit they can't fix it. Never allow access to the core systems. Never step aside for people who might actually understand the technology."
Thorne had been listening quietly. "This is the evidence we're presenting at Emberfall?"
"This is the evidence that changes everything," Corvina said. "We're not just exposing corruption for moral reasons. We're exposing incompetence that threatens everyone's survival. Every person in this world depends on the Covenant Operating System. If it crashes—"
"Everything stops working," I finished. "Magic fails. Wards collapse. Healing spells don't heal. Fire spells don't ignite. The entire magical physics engine grinds to a halt. Millions of deaths. Infrastructure collapse. Civilization ending."
Edrin was quiet for a long moment. Then he started rolling up the maps, making room for my evidence.
"This isn't revolution anymore," he said. "This is survival. We're not fighting for political change—we're fighting to prevent extinction."
"Does that change the plan?" I asked.
"It accelerates it. We can't wait for perfect evidence. Can't spend years building support. If the system has twenty years before total collapse, we need to act within ten. Maybe five. Get into the Root Directory, access the source code, fix the fundamental problems before they cascade into total failure."
"That's ambitious."
"That's necessary." Edrin looked at each of us in turn. "Emberfall is in two weeks. We present this evidence to the resistance. We vote on immediate escalation. And then we stop planning and start executing. Because every month we delay is another month of system degradation. Another month closer to the crash."
"What about the Royal Treasury heist?" Corvina asked. "For the complete financial evidence?"
"Still important. Still necessary. But secondary to the primary objective: Getting into the Root Directory. Accessing the Covenant's source code. Understanding what we're actually fighting." Edrin started organizing my evidence into presentation order. "The financial evidence proves corruption. This system failure evidence proves existential threat. Combined, they'll convince everyone that action isn't just justified—it's mandatory."
I felt the scope shifting again. When I'd first stolen the privilege registry, this had been about exposing nobles buying advantages. Then it became about proving divine corruption. Then about financial conspiracy. Now it was about preventing the literal end of civilization.
Escalation was apparently my specialty.
"Two weeks until Emberfall," Edrin said. "Use that time wisely. Optimize more spells. Train Pip. Prepare your presentation. Because once we present this evidence, there's no going back. We're committing the entire resistance to the most dangerous objective possible: Hacking reality itself to prevent system collapse."
"No pressure," I muttered.
"Maximum pressure," Edrin corrected. "You're the only person who can see the code. The only one who might be able to fix it. The only one who can prevent this world from crashing." He smiled without humor. "How does it feel being the only system administrator in a world of users?"
"Terrifying."
"Good. Terror is appropriate. Means you understand the stakes." He clapped me on the shoulder. "Now go sleep. Actual sleep. Eight hours. Because tomorrow we start preparing for the most important presentation of your life."
I wanted to argue. Wanted to keep working. But Corvina was already herding me toward the stairs, and my body was filing increasingly urgent complaints about resource depletion.
"Fine," I said. "Eight hours. But then I'm optimizing sixty more spells and finishing Pip's Code Vision training."
"Deal," Corvina said.
I climbed the stairs to my room, collapsed on the bed, and let consciousness escape into maintenance mode.
My last thought before sleep: Twenty years until system collapse. Maybe less.
Plenty of time.
Probably.
EXPERIENCE GAINED: SYSTEM FAILURE CORRELATION +600 XP EXPERIENCE GAINED: INFRASTRUCTURE ANALYSIS +500 XP EXPERIENCE GAINED: EXISTENTIAL THREAT IDENTIFICATION +400 XP
LEVEL UP!
ALEXANDRIA "HEX" VOLKOV is now LEVEL 8
Stat Increases:
- Mana: +20 (220 → 240 MP)
- Processing Speed: +15
- Code Vision Range: +2 meters (19 meters)
- System Architecture Understanding: +10
New Skill Unlocked: SYSTEM DIAGNOSTICS
SYSTEM DIAGNOSTICS [ACTIVE - 40 MP]
- Detect health of magical infrastructure
- Identify failure points in Covenant Operating System
- Predict degradation patterns
- Measure system stability metrics
- Locate memory leaks and accumulated errors
- Higher levels allow preventive maintenance
- Critical for eventual system repair
Skills Improved:
- Infrastructure Analysis: Basic → Advanced (NEW SKILL)
- Pattern Correlation: Advanced → Expert
- Threat Assessment: Intermediate → Advanced
STATUS UPDATE — END OF CHAPTER 14
ALEXANDRIA "HEX" VOLKOV
- Level: 8 [+1]
- Class: NULL [UNDEFINED BEHAVIOR ENABLED]
- Location: CROSSROADS - THE WANDERER'S REST INN
- Status: SLEEPING (FINALLY)
Mana: 240/240 MP [+20] XP: 5,650 / 20,000
Trace Risk: 15% [TRACKING FULLY DEGRADED]
New Ability:
- SYSTEM DIAGNOSTICS [ACTIVE - 40 MP] — UNLOCKED
- Detect infrastructure health
- Identify system failure points
- Predict degradation patterns
- Measure stability metrics
- Critical foundation for eventual repair work
Major Discovery:
- Privilege grants correlate 94.7% with system failure events
- Pattern proves privileges are emergency patches, not just corruption
- Covenant Operating System failing: exponential acceleration
- Timeline: ~20 years until total collapse (maybe less)
- Gods incompetent administrators running inherited code
- Can't fix system they don't understand
- Revolution now existential necessity
Evidence Status:
- Financial corruption: DOCUMENTED
- Noble privilege scheme: DOCUMENTED
- System failure pattern: DOCUMENTED
- Correlation between failures and grants: PROVEN
- Existential threat: ESTABLISHED
- Complete evidence package ready for Emberfall
Timeline Shifted:
- Previous goal: Expose corruption, start revolution (decade-long project)
- New goal: Expose corruption, access Root Directory, fix system before collapse (5-10 year window)
- Urgency level: MAXIMUM
- Stakes: Literally preventing end of civilization
SYSTEM NOTE: User discovered system is actively failing.
SYSTEM NOTE: Privileges are desperate patches, not malicious.
SYSTEM NOTE: Timeline compressed: 20 years until collapse.
SYSTEM NOTE: Revolution now survival imperative.
SYSTEM NOTE: User is only potential system administrator.