The Maintenance Cycle ⁠

Marcus Webb spent ten years finding bugs in other people's code. Now he's a bug in someone else's. The System arrived on a Tuesday. Just a notification that humanity was being integrated, and performance would determine survival. Three weeks in, Marcus gets a deprecation notice. His apartment building has 72 hours before it stops being a valid location. Everyone inside will be "sunset." That's what the System calls it when it garbage-collects human beings. He should run. Find a settlement. Level up like everyone else. Instead, he notices something: the deprecation timestamp is in UTC. Not local time. Someone hardcoded a timezone. That's a developer mistake. And where there's one bug, there's always more. Marcus isn't strong. He's not a fighter. But he's spent his whole career testing systems until they break. Now he's going to QA the apocalypse. The System doesn't have customer support or a bug bounty program. Turns out it really doesn't like users who exploit its edge cases. But Marcus has 72 hours, a ticking deprecation timer, and one question nobody else is asking: If this is software, who wrote it?