Global Apocalypse: My System Is Always AFK

Three weeks of peace had done something to Ethan that four months of apocalypse never managed. It had made him soft in the best possible way — the kind of soft where he slept nine hours a night, ate breakfast sitting down, and had genuinely started to believe that ”quiet” was just how life worked now.

So when a section of the Citadel’s courtyard sank six inches overnight, he found out about it the same way he found out about most things: someone else noticed first, and it took a while for the news to reach him, because nobody wanted to be the person who ruined his morning.

”It’s not urgent,” Suresh said carefully, standing at the edge of the depression with a cup of chai in one hand and a clipboard in the other. ”Nobody’s hurt. Nothing’s on fire. I just thought you’d want to know before you walked into it.”

Ethan looked down at the dip in the courtyard — a shallow, almost gentle bowl in the paving stones, roughly ten feet across, centered, with irritating precision, directly beneath where the tea golem usually parked itself to recharge between batches.

”It’s under the golem’s spot,” Ethan said.

”It is.”

”That’s the part that bothers me. Not the ground caving in. The ground caving in exactly where my tea gets made.”

Suresh, who had long since stopped being surprised by which details actually alarmed Ethan, simply nodded and made a note on the clipboard.

The tea golem itself rolled up beside them, took one look at its usual spot now sitting a half-foot lower than the rest of the courtyard, and made a small, offended clicking sound before carefully repositioning itself two feet to the left, as if the ground had personally inconvenienced it.

”Yeah,” Ethan agreed, watching it settle. ”Exactly.”

[NOTICE: Structural anomaly detected beneath courtyard section C-4.]

[The system has been monitoring this depression since it began forming roughly nine hours ago. It did not wake the subject, because the rate of sinking was slow enough not to constitute an emergency, and because the subject had specifically requested, in writing, not to be disturbed for anything below ”immediate threat to life” between the hours of 11 PM and 10 AM.]

Ethan crouched down at the edge of the dip and pressed a hand flat against the sunken stone. It was cool. Ordinary. Nothing about it felt dangerous — no hum, no residual Void energy, none of the telltale signs he’d learned to recognize after months of enforcement droids and admin gates showing up uninvited.

”Feels normal,” he said.

[Composition analysis confirms the stone itself is unremarkable. The anomaly is not in the material. It is in what lies beneath it. The system has attempted to scan the space below courtyard section C-4 and has, for the first time since being assigned to the subject, returned a result it does not know how to interpret.]

Ethan’s hand went still against the stone. ”Define ’doesn’t know how to interpret.’”

[Ordinarily, when the system scans an area, it returns depth, composition, and any relevant threat data — the same way it mapped the Void Cave, the Sunken Vein, every dungeon the subject’s avatar has ever cleared. This scan returned none of that. It returned a single line of data, repeated, regardless of how many times the system requests further detail.]

”And that line says what.”

[UNKNOWN ARCHITECTURE. PRE-DATES CURRENT FRAMEWORK.]

Ethan sat back on his heels, the words settling somewhere in his chest with more weight than he wanted them to have this early in the morning.

”Pre-dates the Framework,” he repeated slowly. ”Like — older than the apocalypse. Older than the whole system.”

[That is the system’s best interpretation, yes. The system would like to note that this is, functionally, the first time it has ever encountered something it cannot classify. Enforcement droids, it understood. The Arbiter, it understood, eventually. This, it does not understand at all, and the system finds that mildly unsettling in a way it does not have prior data to compare against.]

Suresh, listening to one half of the conversation the way he’d learned to over the past several months — patiently, without needing to hear the system’s side directly — set his cup down on the courtyard’s low wall.

”How bad is ’mildly unsettling’ on a scale of droids to Arbiter,” he asked.

”Honestly? I don’t know yet,” Ethan admitted, standing up and brushing dust off his knees. ”The system’s never not known something before. That’s new.”

He looked back down at the sunken stone, at the tea golem now settled a safe distance away, at the small crowd of curious refugees beginning to gather at a respectful distance — word traveled fast in a community of six hundred people with nothing more urgent to do most mornings than notice when something changed.

”Okay,” Ethan said, more to himself than anyone. ”So there’s something under my building that’s older than the thing that tried to erase me for a week straight.”

[Correct.]

”And it’s been sitting there this whole time.”

[Presumably, yes. The courtyard’s foundation would have been laid well before the apocalypse began. If this architecture pre-dates the Framework, it likely pre-dates the building itself — possibly by a significant margin.]

Ethan rubbed the back of his neck, the specific gesture he reserved for problems that were genuinely, personally his to deal with, rather than the Framework’s endless parade of manufactured crises. ”So I’ve basically been living on top of something this whole time and just never noticed.”

[The system would point out that the subject rarely notices anything that doesn’t directly affect his sleep schedule or his tea supply. This is, arguably, consistent behavior.]

”That’s fair,” Ethan admitted, ”but this feels like it should’ve come up sooner. Like — somebody should’ve mentioned there’s a mystery basement under the building I turned into a refugee sanctuary.”

[The system agrees this would have been useful information roughly four months ago. It did not have access to it four months ago. It suspects that whatever is down there only became detectable once the Void Pulse disturbed something in the deeper architecture beneath the Framework itself. The system believes, in short, that the subject’s own actions three weeks ago may be the reason this is surfacing now.]

Ethan groaned, long and put-upon, the exact sound of a man realizing his own competence had once again created a problem he now had to personally solve.

”Great,” he said. ”So I broke something so big it woke up a second, older something.”

[That does appear to be the situation, yes.]

He looked down at the shallow depression one more time, at the quiet, ordinary-looking stone that was apparently sitting directly above a piece of architecture the system — the same system that had confidently narrated its way through Calamities, titans, and literal gods — genuinely could not classify.

Somewhere behind him, one of the younger refugee kids who’d taken to treating the courtyard as a playground tugged at Suresh’s sleeve and asked, in the innocent, unbothered way only kids managed anymore, whether the sunken part was going to turn into a pool.

”Not today,” Suresh told her gently, steering her back toward the others.

Ethan almost smiled at that — almost, except his attention had already shifted somewhere else, down, toward the stone, toward whatever quiet, patient thing was sitting beneath his home, apparently waiting.

”Okay,” he said finally, decision settling over him with the same reluctant, practical weight it always did before he did something he didn’t particularly want to do. ”I guess we’re digging up my own courtyard.”

[The system would like to confirm the subject wishes to investigate personally, rather than requesting a professional excavation team.]

”I’m not letting strangers dig under my building before I know what’s down there,” Ethan said, already walking toward the toolshed Suresh had built for exactly this kind of improvised crisis. ”Last time something new showed up uninvited, it was droids in my kitchen. I’d like to actually be the first one to see whatever this is, for once.”

[The system logs this decision.]

[The system would also like to note, quietly, that it has just accessed a fragment of buried data attached to the unknown architecture — a single phrase, corrupted, barely legible, that surfaced the moment the subject decided to dig. The system does not yet know what it means. It is including it here regardless, because it feels the subject should know it exists.]

[FRAGMENT RECOVERED: ”...the King is still—”]

[The rest of the phrase did not survive.]

Ethan stopped halfway to the toolshed, the words settling into the quiet morning air with a weight that had nothing to do with sleep schedules or tea supplies at all.

”The King is still what,” he said slowly.

The system didn’t answer. For the first time in this entire story, it genuinely couldn’t.