They sealed the Oversight corridors so smoothly you would think the building had practiced for applause, doors sliding shut with a soft sigh while the intercom informed us that a system integrity audit was underway and that all staff were to remain in designated zones until further notice. I was in the administrative wing, which meant I was technically designated and practically stuck, watching analysts hurry past with tablets clutched to their chests as if they might be frisked for treason.

  “Integrity audit,” someone muttered near the stairwell.

  “That’s what we call it now?” someone else replied.

  The Tower’s voice came through again, calm and level, the tone it uses when it wants cooperation without debate. I leaned against the wall and checked my slate, because when a building locks its doors the interesting thing is rarely the hinges.

  Downstairs, technicians were already performing their ballet of cables and reroutes, speaking in clipped phrases that sounded almost cheerful. The Extractor incident had been framed as a technical irregularity, but the speed of the lockdown suggested a different concern. Mechanical failures get toolkits. Data leaks get doors.

  Back in my cubicle, which now felt like a cell with better lighting, I opened the buffer where I had hidden the partial downloads. They looked harmless enough at first glance, maintenance scraps and predictive modeling residue, but when I layered them together and aligned the timestamps the pattern stood up and waved. Extraction surges matched academy ritual nights to the second. Auxiliary conduit throughput rose whenever the academies staged their most elaborate displays. The emergency spike from the day the Extractor misbehaved aligned neatly with the backfeed that had made the upper district flicker.

  I whistled under my breath.

  “That’s unfortunate,” I told the empty room.

  I ran the comparison again, because I am thorough when I am about to ruin my own life. The allocation ledger showed a clean percentage siphoned into academy reserve grids during peak ritual windows. Not civic lighting. Not hospital stabilizers. Academy reserves. The numbers did not argue. They did not blush either.

  “So we are in the business of turning grief into stage lighting,” I said softly, scrolling. “Efficient.”

  The screen glowed back at me with the steady confidence of arithmetic. Suspicion is foggy and gives you space to wander away. Proof is tidy. Proof lines up its columns and asks what you plan to do with them.

  I considered closing the files and going for coffee. I even stood up halfway, as if caffeine could dilute a ledger. Then the intercom chimed again, this time adding that access privileges might be temporarily adjusted during the audit. Adjusted is a friendly word. It sounds like someone fluffing a cushion.

  My slate chimed.

  Subject: Temporary Suspension of Access Privileges – Administrative Audit Pending.

  “Well,” I said. “There it is.”

  I opened the notice. The language was elegant and courteous. It thanked me for my cooperation while informing me that my write permissions to certain archives had been paused. My audit trail would be reviewed to ensure compliance with data governance protocols. In short, they had noticed me browsing where polite clerks do not browse.

  My badge beeped when I tested it against a restricted console and the console responded with a firm denial. Across the corridor, two analysts pretended to be deeply invested in a spreadsheet. One of them glanced at me.

  “Access glitch?” she asked.

  “Apparently I am too interesting,” I replied.

  She blinked. “You should try being boring.”

  “Working on it.”

  Being flagged does not come with sirens. It comes with subtle inconvenience. Doors that used to open do not. Queries that once returned data now return policy statements. It is all very civilized.

  I checked my logs and saw the elevated scrutiny marker attached to my user ID. A small digital halo of suspicion. Somewhere an automated monitor had decided I required attention.

  “All right,” I told the slate. “Let’s assume I am not the favorite child today.”

  The choices arranged themselves quickly. I could delete the fragments and hope the audit found nothing worth escalating. I could dump everything to an external channel and brace for dramatic consequences. Or I could hide the information in plain sight and make retrieval an exercise in patience.

  I am not dramatic by nature. I am patient when required.

  So I began slicing.

  The archive broke apart into tidy little packets, each no more alarming than a misfiled inventory note. I wrapped them in maintenance metadata, checksum chatter, revision notes about filter replacements and airflow irregularities. I embedded one fragment inside an HVAC calibration log dated three months ago. Another slid neatly into a spare parts inventory for decommissioned regulators. A third nested inside a predictive model cache that no one opens unless they enjoy statistical archaeology. And who does?

  I muttered as I worked, because narration improves craftsmanship.

  “Extraction surge alignment, meet air duct variance report. You two will get along beautifully.”

  I adjusted timestamps by minutes here and hours there, enough to blend but not enough to trigger anomaly detection. I renamed a file to something aggressively dull. I cross-referenced a fragment through a maintenance ticket that had been closed quietly six weeks prior.

  Love this novel? Read it on Royal Road to ensure the author gets credit.

  When I finished the first pass, I leaned back and admired the mess.

  “If they want to find it,” I said to the ceiling, “they’ll need a librarian.”

  Across the aisle, someone coughed. I waved pleasantly.

  I quickly created a breadcrumb under a test environment account that looked like an abandoned training project. The account name suggested an intern had once tried to model energy drift and given up. I left instructions there in oblique form, references that would mean nothing to an auditor and everything to someone who knew where to look.

  I did not transmit anything outside the network. Lockdowns make external traffic glow like a flare, and I prefer my flares metaphorical.

  Footsteps echoed in the corridor. Security had begun its slow walk through the administrative wing, two officers moving in that polite way that says they expect compliance but have practiced otherwise. One stopped near my cubicle.

  “Mirakei,” he said, consulting his tablet, “we’ll need a few minutes of your time.”

  “Only a few?” I asked. “I was hoping for an afternoon excursion.”

  He did not smile, but his eyes flickered. “Clarification regarding your recent access activity.”

  “Ah,” I said. “Clarification. My favorite hobby.”

  He waited.

  I saved my work, closed the visible windows, and pocketed the slate. As I stood, my console chimed with another access denial, as if to underline the point.

  “Rough day?” the analyst across from me whispered.

  “Administrative growth opportunity,” I replied.

  She shook her head and turned back to her screen.

  The officer gestured toward the corridor. I stepped out and fell into pace beside him. The building hummed as it always does, but with more urgency. Doors remained sealed along certain wings, and technicians moved with deliberate focus.

  “Busy afternoon,” I said.

  “Routine review,” he answered.

  “Of course. Nothing says routine like a lockdown.”

  He did not engage with that.

  We passed a cluster of supervisors speaking in low voices. I caught fragments.

  “…containment of internal data exposure…”

  “…ensure narrative consistency…”

  “…academy liaison notified…”

  I filed the phrases away. Narrative consistency is not a phrase you use when you are confident.

  As we walked, my mind ticked through consequences in practical terms. If the audit traced my downloads, they would see the initial copy. They might see fragments, though not easily. If they escalated, I could claim research curiosity tied to optimization modeling. That wasn't even a lie, really.

  The officer glanced at me. “You understand why this is necessary.”

  “Because curiosity is expensive?” I offered.

  “Because system integrity depends on controlled access.”

  “That does sound better in a memo.”

  He almost smiled this time.

  We reached a conference room at the end of the corridor. Frosted glass. Two chairs inside. A recording unit in the corner that looked too bland to be menacing, but as if it would snarl if you got too close.

  Before entering, I asked, “Out of professional interest, how many people get invited to clarifications during audits?”

  “A small number.”

  “I do enjoy exclusivity.”

  He opened the door.

  Inside, another administrator waited, slate already active. She gestured to the chair opposite her.

  “Mirakei,” she said, “thank you for cooperating.”

  “I aim to please.”

  She tapped her screen. “Your access logs show multiple queries into restricted energy allocation archives. These fall outside your standard duties.”

  “I was reviewing predictive throughput models after the Extractor incident,” I said. “Cross-referencing surge patterns to improve stabilization protocols.”

  “Without authorization.”

  “With initiative,” I corrected gently.

  Her mouth thinned. “The audit team flagged your activity because it intersects with academy reserve allocations.”

  “Does it?” I said. “That’s interesting.”

  She studied me, perhaps waiting for a confession or a denial. I gave her neither.

  “Our concern,” she continued, “is that partial datasets, when misinterpreted, can lead to inaccurate conclusions about system priorities.”

  “Misinterpretation is always a risk,” I agreed. “That is why I prefer full datasets.”

  The officer shifted slightly near the door.

  She leaned forward. “Did you extract or replicate any restricted data beyond your authorized purview?”

  There it was. Direct enough.

  “I reviewed what my credentials allowed at the time,” I said. “If those credentials were overly generous, that seems a configuration issue.”

  “You understand that dissemination of incomplete or sensitive information would constitute a breach.”

  “I understand the handbook very well,” I replied. “Section twelve. Data governance. Very stern.”

  Her gaze sharpened. “We are assessing whether any such breach occurred.”

  I folded my hands on the table. “Then I hope your assessment tools are excellent.”

  The officer’s radio crackled softly. Somewhere deeper in the building, another door closed.

  The administrator tapped her slate again. “Your access privileges will remain suspended pending review. You are not to engage in further analysis of allocation archives.”

  “I shall redirect my talents to air filters,” I said.

  “That would be appropriate.”

  She closed the file. “You may return to your station. We will contact you if further clarification is required.”

  “Clarification is my calling,” I replied.

  The officer escorted me back through the corridor. The hum of the Tower resumed its steady rhythm, as if nothing significant had occurred. When we reached my cubicle, he paused.

  “Stay within assigned systems,” he said.

  “I live there,” I answered.

  He walked on.

  I sat down, opened a harmless maintenance dashboard, and let the ordinary data scroll past. Airflow variances. Filter replacement schedules. Comforting, boring things.

  Behind the scenes, fragments of a ledger slept inside duct reports and spare parts inventories. The audit would comb my visible trail. It would find curiosity and perhaps reprimand it. It wouldn't easily find the map.

  Across the aisle, the analyst leaned over again. “Well?”

  “Clarified,” I said.

  “And?”

  “I am to focus on air.”

  She laughed quietly. “Safer element.”

  “Debatable.”

  I returned to the dashboard, fingers moving in the steady rhythm of compliance. The Tower believed it had contained the incident. The academy lights would flicker, then steady. Reports would be drafted.

  Somewhere in the network, the truth now lay, waiting, if still a puzzle.

  When my slate chimed again with a reminder of suspended privileges, I smiled at it.

  “Proof,” I murmured, adjusting a ventilation graph, “is very educational.”