The notification appeared at 5:47 AM, which was somehow the most offensive part.

  

  [NOTICE: Scheduled Deprecation - Structure ID: ATX-E-4471]

  Timestamp: 11:47:23 UTC

  This structure has been flagged for end-of-life processing.

  All users must vacate within 72 hours.

  Failure to comply will result in automatic sunset of remaining processes.

  Thank you for your cooperation.

  Marcus Webb stared at the blue text hovering in his peripheral vision, reading it three times to make sure it was real. His first thought, honed by years of QA work, was: They didn't localize the timestamp. That's UTC, not Central. Six-hour difference. Someone hardcoded a timezone.

  His second thought was: I'm about to be uninstalled.

  He blinked twice, dismissed the notification with a deliberate shift of focus - that gesture still felt unnatural after three weeks - and immediately pulled it back up to confirm he hadn't hallucinated it. The blue text reappeared, exactly the same, down to the passive-aggressive "thank you for your cooperation."

  Automatic sunset of remaining processes. That was what they called it. Not "death." Not "execution." Sunset. Like a scheduled server maintenance window where they'd gracefully terminate your thread and deallocate your memory.

  Marcus had spent ten years as a QA engineer. He knew exactly what "sunset" meant in software development. It meant: this feature is no longer supported. All existing instances will be removed. No migration path. No backwards compatibility.

  It meant: you're garbage now, and we're collecting you.

  He sat up in bed, the movement sending a cascade of empty water bottles rolling across the floor. His apartment was small - had always been small, even before the world ended - but three weeks of self-isolation had transformed it into something that looked like a hoarder's paradise crossed with a conspiracy theorist's cork board.

  Takeout containers from when delivery still worked lined the kitchen counter. His laptop sat open on the desk, screen dim but still logged into the Nexus internal wiki - a page he'd been reading on System behavior patterns before falling asleep sometime around 2 AM. The whiteboard he'd bought during his second week at Nexus, when he'd still believed in collaborative brainstorming sessions, now covered an entire wall with his notes about System bugs.

  Not the aspirational kind of wall that showed you had your life together. The obsessive kind that showed you'd given up pretending.

  Through the window, Austin looked almost normal if you squinted. The skyline was intact - the System hadn't knocked down buildings, which was honestly the weird part. Downtown still rose against the dawn sky, all glass and steel and that one weirdly phallic condo tower everyone made jokes about. Cars still sat in driveways. The sun rose like it always had, indifferent to the fact that humanity was being performance-reviewed by something nobody understood.

  Marcus pulled up his status screen, a habit he'd developed in the first week. It materialized in his vision with a faint shimmer, semi-transparent, positioned just left of center so it didn't block his actual eyeline. The interface had the kind of polish that suggested someone had actually thought about user experience. Which was troubling, because if there was one thing Marcus had learned in ten years of software testing, it was that good UX meant someone had planned this.

  Bad software happened by accident. Good software happened by committee.

  

  USER: Marcus Webb

  Class: Logician (Analyst)

  Level: 2

  Status: Active (DEPRECATED - 71h 58m remaining)

  VIT: 11 | STR: 8 | AGI: 10

  INT: 16 | PER: 14 | RES: 12

  Active Skills: Anomaly Detection v0.8.1-beta

  Passive Buffs: None

  Debuffs: Sleep Deficit (minor), Vitamin D Deficiency (minor), Deprecated (72h)

  Development Credits: 847

  Next Review Cycle: SUSPENDED

  The "Deprecated" status sat there in red text, ticking down like a countdown timer on a bomb.

  Marcus had questions about the debuff system. How did it know about his vitamin D levels? Was it measuring, or inferring from behavioral patterns? He'd been staying indoors for three weeks - maybe it just assumed anyone who wasn't going outside had vitamin D deficiency. But that seemed like lazy implementation. Did it have access to his medical records? Was it running some kind of continuous biometric scan?

  He'd filed a mental bug report, right alongside the others he'd documented since Day One.

  The list was getting long.

  Three weeks earlier.

  The System - capital S, because it had introduced itself that way in the initial notification - had arrived on a Tuesday.

  Marcus had been at work. Nexus headquarters, The Domain, Austin. The office was the kind of place that called itself a "campus" and had kombucha on tap and meeting rooms named after memes nobody found funny anymore. He'd been reviewing test cases for a feature nobody cared about - something to do with optimizing the checkout flow for users who abandoned their carts, as if people needed to be optimized into buying things they didn't want.

  He'd been thinking about lunch when the blue text appeared.

  

  [SYSTEM INITIALIZATION COMPLETE]

  Welcome to the integration program.

  All users will be assessed. Performance determines survival.

  Good luck.

  His first instinct had been to check if it was a prank by the DevOps team. They'd done shit like that before - pushed fake alerts to everyone's monitors as "team building" or whatever they called harassment these days. But the text wasn't on his monitor. It was in his vision. No matter where he looked, it stayed fixed in the same relative position, like a heads-up display.

  He'd looked around the open-plan office. Everyone else was staring at nothing, their faces showing the same confusion he felt.

  It was not a prank by the DevOps team.

  The next notification came sixty seconds later.

  

  [ASSESSMENT PHASE INITIATED]

  Please answer the following questions honestly.

  Your responses will determine your initial classification.

  There are no wrong answers.

  That was a lie. Marcus knew corporate-speak when he heard it. "There are no wrong answers" always meant "some answers will get you fired, good luck guessing which ones."

  The questions had been... weird. Not obviously apocalyptic. More like a personality test designed by someone who'd read exactly one book on psychology and decided they were qualified to categorize human consciousness.

  When faced with an unfamiliar problem, do you: (A) Try different solutions until something works, (B) Analyze the problem to understand its structure, (C) Look for similar problems you've solved before, (D) Ask others for help?

  Marcus had picked B. Because that was what he did. That was what QA was - analyzing problems, finding their structure, documenting their patterns.

  The questions kept coming. Twenty of them. Thirty. Fifty. They covered everything from risk tolerance to social preferences to how you felt about ambiguity. Marcus had answered honestly, because he'd never learned how to game performance reviews. That was one of the many reasons he'd been passed over for promotion at Nexus three times.

  When the assessment finished, the System assigned him a Class.

  

  CLASS ASSIGNED: Logician (Analyst)

  You have been designated as: Cognitive Processing / Pattern Recognition

  Primary attributes: INT, PER

  Role: Analysis, system comprehension, strategic planning

  Note: Low physical optimization. Recommend support-role positioning.

  In other words: squishy nerd. Not great for the apocalypse.

  But Marcus had looked at that designation and thought: okay. Pattern recognition. I can work with that.

  He'd been wrong about the "working with it" part. Mostly what he'd done for three weeks was hide indoors and document bugs.

  This content has been misappropriated from Royal Road; report any instances of this story if found elsewhere.

  He'd spent the first day thinking it would end.

  That was what everyone thought, right? This was a test. A hoax. A mass hallucination caused by 5G towers or chemtrails or whatever conspiracy theory felt most comforting in the moment. Someone would figure it out. The government would fix it. Scientists would explain it. Adults would handle the situation, and Marcus could go back to writing test cases for shopping cart abandonment algorithms.

  But on Day Two, the monsters showed up.

  The System called them "entities," which was the kind of bland corporate language that made Marcus irrationally angry. They weren't entities. They were nightmare fuel rendered at low polygon counts, glitching through reality like corrupted assets in a broken game engine.

  The first one Marcus saw appeared on the I-35 frontage road, outside his apartment window. It looked vaguely humanoid - two arms, two legs, a head-shaped protrusion - but wrong in ways that made his brain hurt to process. The proportions were off. The movement was stuttering, like a video playing at half framerate. Its texture flickered between states, sometimes translucent, sometimes solid, sometimes just an outline traced in static.

  The System classified them as Glitch Horrors, which was both accurate and suggested that whoever named them had a sense of humor.

  Marcus had watched from his window as the thing wandered down the street. It moved randomly, pathing in circles like an NPC whose navigation mesh had broken. Someone's dog barked at it. The Glitch Horror turned toward the sound, jerked forward in a movement that looked like teleportation more than walking, and -

  Marcus had closed the blinds.

  He didn't open them for two hours.

  When he did, the street was empty. The dog was gone. The Glitch Horror was gone. A car alarm was going off somewhere in the distance, and nobody was coming to turn it off.

  That was Day Two.

  By Day Three, infrastructure started failing. The power stayed on - the System apparently needed that - but elevators stopped working. Internet came and went in waves.

  On Day Five, the System started handing out quests.

  

  [QUEST AVAILABLE: Prove Your Worth]

  Demonstrate value to the integration program.

  Kill 5 entities OR gather 100 resources OR establish a settlement.

  Reward: Level advancement, skill unlock

  Failure: Continued low-priority status

  Marcus had looked at his STR 8 and decided that "continued low-priority status" was fine, actually. He didn't accept the quest. Instead, he documented the quest structure in his notes and went back to staying indoors.

  On Day Seven, someone in his building accepted a quest. Marcus heard the screaming from four floors up. Then he heard nothing.

  The next morning, the body was gone. The System notification in his vision said:

  

  [USER: Steven Pak - PROCESS TERMINATED]

  No explanation. No funeral. Just a database entry marking another record as inactive.

  That was when Marcus started his whiteboard.

  The whiteboard covered most of the wall now, every inch filled with his handwriting in blue dry-erase marker.

  SYSTEM BUGS & OBSERVATIONS

  UI/UX Issues:

  - Notifications appear in peripheral vision → collision with driving/combat

  - No volume control on alert sounds

  - Quest text sometimes overlaps status screen

  - Timestamp localization broken (always UTC, never adjusts for user timezone)

  Skill Issues:

  - Tooltip descriptions don't match behavior

  - Example: "Fireball v1.2" - tooltip says "ranged," actual range is ~3m (melee)

  - Version numbers visible on all skills → suggests ongoing development/iteration

  - Skill names use camelCase → developer convention, not user-facing language

  XP/Progression Issues:

  - XP fails to register intermittently (packet loss? server sync issues?)

  - Some users report same actions yielding different XP amounts

  - Level thresholds seem inconsistent across classes

  Entity Behavior:

  - Movement pathing appears buggy (entities loop, get stuck on terrain)

  - Spawn rates vary by time of day (higher at night → intentional or server load?)

  - Entity despawn rules unclear (some disappear after death, some don't)

  Class Assignment:

  - Same assessment answers → different classes (suggests A/B testing)

  - No respec option (bad UX for a system with unclear mechanics)

  World State:

  - Deprecation notices use "sunset" terminology → software development language

  - Building 12 processed in exactly 4m 23s → hard-coded timeout value?

  - Deprecated structures remain physically intact → only flagged as invalid in System database

  Core Question: Is the System software? Evidence suggests YES.

  - Version numbers

  - Developer terminology

  - Bugs consistent with production software

  - Iterative updates (skills have version numbers → implies patching)

  If it's software, who wrote it? And why?

  Marcus had no answers to those questions. He'd filed them in the "P1 - Critical" category of his mental backlog and moved on to documenting things he could test.

  But now, staring at his deprecation notice, the questions felt less academic.

  Someone had written the code that was currently scheduling his death. Someone had set a 72-hour timer and called it "end-of-life processing." Someone had decided that Structure ATX-E-4471 was no longer needed and should be garbage-collected along with everyone inside it.

  Marcus wanted to meet that person.

  He wanted to ask them why the fuck they'd pushed to production without QA approval.

  Building 12 had been deprecated on Day Nineteen.

  Marcus had watched it happen from his window. The building - a four-story apartment complex identical to his own, just two hundred yards down the road - had received the same notification he was reading now. 72-hour warning. Vacate or be sunset.

  Most people left. Marcus watched them stream out over the course of the first day, carrying duffel bags and backpacks, heading toward... somewhere. The highways, probably. People kept saying there were settlements forming, clusters of survivors who'd banded together for defense. Marcus hadn't verified those claims. He'd stayed indoors.

  But some people didn't leave Building 12. Either they didn't believe the warning, or they had nowhere else to go, or they'd decided that dying in their apartment was better than dying on the highway.

  Marcus understood that reasoning. He'd been working through the same logic himself for three weeks.

  When the timer hit zero, Building 12... changed.

  That was the only word Marcus had for it. The structure didn't collapse. There was no explosion, no fire, no dramatic apocalypse movie bullshit. The building just changed.

  The lights went out. That was the first sign. Every window went dark simultaneously, like someone had thrown a breaker. Then the air around the structure took on a quality that Marcus could only describe as wrong. It shimmered. Not like heat haze - more like reality was buffering, struggling to load the next frame.

  The shimmer intensified for exactly four minutes and twenty-three seconds. Marcus timed it on his phone.

  Then the building stopped being a valid location.

  Marcus didn't know how else to explain it. The structure was still there - physically, materially present. But the System no longer recognized it as a place where users could exist. Anyone inside received a status effect:

  

  [ERROR: Invalid Position]

  And then, thirty seconds later:

  

  [CRITICAL ERROR: Process cannot continue]

  And then nothing.

  Marcus had pulled up his binoculars - leftovers from a camping trip he'd taken three years ago and hated - and looked at Building 12's windows.

  He'd seen shapes. Human-shaped. Pressed against the glass.

  They weren't moving.

  The System had simply decided that structure was no longer supported, and everything in it was cleaned up. Garbage collection. Memory deallocation. Process termination.

  The bodies were still there. Marcus knew that. The building was still there, physically. But the System had marked that space as invalid, and so it was. You could probably walk into Building 12 right now, if you wanted to test it. You could probably climb the stairs, open an apartment door, see what was left.

  Marcus hadn't tested it.

  He'd written it down on his whiteboard instead: Deprecation = permanent. No reversal. Hard-coded timeout: 4m 23s.

  And now his building was next.

  The dread didn't hit all at once.

  It came in waves, each one slightly worse than the last, like the System was stress-testing his psychological resilience to see when he'd break.

  Wave one: This isn't real. You're misreading the notification. Check again.

  Marcus checked again. The notification was still there. Structure ATX-E-4471. 72 hours. Automatic sunset.

  Wave two: Okay, it's real, but maybe there's a way to cancel it. Maybe you can petition the System, file a complaint, find an admin console somewhere.

  Marcus pulled up his System interface, navigating through every menu option he'd mapped over the past three weeks. Status. Skills. Quests. Inventory. Settings. There was no "cancel deprecation" button. There was no "contact support" option. The System didn't have a helpdesk.

  Wave three: Fine, you can't cancel it, but you have 72 hours. That's time to make a plan. Figure out where to go. Pack efficiently. Leave safely.

  Marcus looked at his STR 8. He looked at his Anomaly Detection skill, which was great for spotting problems but did exactly nothing to solve them. He looked at his 847 Development Credits, which he'd been hoarding like they'd matter, and realized he had no idea what to spend them on because he'd been too afraid to experiment.

  Wave four: You're going to die.

  That one hit harder than the others.

  Not because it was new information. Marcus had been operating under the assumption that he'd probably die since Day One. The apocalypse wasn't kind to squishy nerds with poor upper body strength. But there was a difference between "probably die eventually" and "definitely die in 72 hours if you don't get your shit together."

  The first was abstract. The second was a countdown timer in red text at the top of his vision.

  Marcus stood up, legs shaky, and walked to the window.

  Austin was waking up. The sun was higher now, painting the sky in shades of orange and pink that would've been pretty if he'd had the mental capacity to appreciate beauty. Somewhere down the street, a car alarm was going off. Nobody would turn it off. Car alarms didn't matter anymore.

  He could see Building 12 from here. Still standing. Still physically present. Still full of bodies that nobody had collected because there was no "nobody" left to do that kind of work.

  In 72 hours, his building would look exactly the same.

  He thought about the people in Building 12 who'd stayed. Had they been afraid? Resigned? Too tired to run? Marcus understood all of those options. He'd been too tired to run for three weeks.

  But standing here, staring at his future, he realized something:

  I don't want to die like that.

  Not pressed against a window, waiting for a hard-coded timeout to expire. Not garbage-collected like a deprecated variable in a codebase nobody was maintaining.

  If he was going to die - and he probably was, statistically speaking - he wanted it to be somewhere other than his shitty apartment in a building the System had marked for deletion.

  That wasn't courage. It wasn't heroism. It was just... a preference. And preferences were something he could act on.

  Marcus turned away from the window and started packing.