Chương 86: Who built the system?
Aetherforge: Defiant Realms · NyxHolloway · 133 chương · ~22 phút đọc · Tạo 11/08/2026
The route north was clean. He knew this because he'd checked it twice before breakfast and once more after, which was once more than he usually checked clean routes, and he was aware of this and filed it under: not relevant to the route assessment. The route was fine. The route was not what he was thinking about. They moved well in the morning, which helped. Marco had gotten quieter since the wolf incursion. Not troubled-quiet.
His arm still pulled wrong on the uphill sections and he had been managing it without complaint. Dez moved better every week, which Finn had stopped finding surprising and started finding satisfying in a way he hadn't budgeted for. Yuki covered the eastern flank without being asked, which she had been doing for three weeks, and he had stopped noting it in the operational column because some things became infrastructure. He ran the threat assessment. He managed the pace. He covered the gaps. Functional was the word.
He was doing everything the day required and doing it correctly and the word for that was functional, which was a good word, a useful word, a word that meant all the systems were running and nothing critical had failed. He had been functional for 159 days. He was good at it. He was thinking about KwanHS. Not constantly. Not in the way that degraded performance. He caught himself when it started pulling his attention and redirected.
But in the background, underneath the route assessment and the threat model and the pace management, there was a question he couldn't stop running. He'd felt responsible for the group before he'd decided to feel responsible for the group. He could pinpoint roughly when it had shifted, somewhere around week two, somewhere between Marco taking the hit in the wolf incursion and Dez going quiet for four minutes during the PK briefing, but he couldn't identify a decision. There hadn't been a decision.
The responsibility had accumulated the way water accumulated in a low point, without asking permission, without announcing itself, until one day he was running threat coverage for four people and calling it route assessment and the self-deception was so thin he could see straight through it. That part he understood. That part had a logic to it. They were here, he was here, he was more capable, the math worked out.
At DataVault, responsibility came with a title change and a modest raise and a line on the org chart that said this person is now accountable for the following deliverables. There was a form. HR sent an email. You signed something. The process was bureaucratic and undignified and it was, at minimum, voluntary. You could decline. You could say no, I don't want the additional scope and someone would be mildly disappointed in you during the next review cycle and life would continue.
Here, the responsibility had no form, no org chart, no HR email, no option to decline. It had arrived the way the weather arrived, as a condition of the environment, and the only acknowledgment had been a pair of broken glasses in a cold fire and a WIL notification that amounted to the system saying we see you carrying this, here's a stat point, keep going. He did not want the additional scope. He was carrying it anyway. What he couldn't account for was KwanHS. KwanHS had never been in his camp.
Had never eaten his food or learned his methodology or moved wrong on the uphill sections in a way that required him to rebuild the travel protocol. KwanHS had been a username in a channel, posting about wind direction and sun glare, and Finn had read those posts with the detached attention of someone collecting data, and somewhere in the reading it had become something else. He'd mapped a route. He'd found a patrol window.
He'd lain awake running the timing and known, with the flat certainty of someone who had been doing threat assessment for five months, that the burst-posting pattern meant something was wrong. He hadn't chosen that. The knowing had arrived the same way the responsibility for the group had arrived, without a decision, without a form to sign, without anyone asking him whether he wanted to be the kind of person who lost sleep over a username he'd never replied to. He was, apparently, that person.
He had apparently been becoming that person for some time without noticing. When, he thought, exactly, did the circle get this big. And then, underneath the question, in the register he used for things that were true and uncomfortable and not going away: who built the system that killed him. Because KwanHS hadn't died of weather. Hadn't died of bad luck or poor planning or any of the things you could attribute to the mechanics of survival if you were being generous about the mechanics.
KwanHS had posted about wind direction. He'd built his fire east-facing. He'd been paying attention, and careful, and methodical, and he'd died anyway because the system that put him in this forest had been calibrated to produce exactly this outcome. Not as a side effect. Not as an unfortunate consequence of an otherwise neutral environment. As the point. Eight hundred and forty-seven accounts at spawn. Fourteen active in the seven-day window. The attrition curve was not an accident.
The threat density was not an accident. The spawn rate, the resource scarcity, the PKer incentive structure that rewarded killing other players with their XP, the notification system that tracked your grief and gave you a WIL point for carrying it correctly. None of it was an accident. Someone had built this. Three someones, if the god-broadcast notifications were to be believed, and Finn had no reason to doubt them because divine entities who wanted credit for their cruelty were generally honest about the cruelty.
Unlawfully taken from Royal Road, this story should be reported if seen on Amazon. He ran the numbers because that was what he did with things that made him angry and the anger needed a shape. Eight hundred and forty-seven minus fourteen. Eight hundred and thirty-three accounts that had posted at least once and then gone quiet over the course of 159 days. Not all dead. Some had stopped posting. Some had found groups and gone silent the way Dez had gone silent.
But probably not most of them, which was what he'd told Dez at the fire three days ago, and the math behind probably not most of them was the math of a system designed to produce a mortality rate that the designers found entertaining. The anger was not hot. He noted this about it. It was not the kind that burned or clouded or pushed him toward something reckless.
It was cold, and it was precise, and it sat in a place he hadn't previously used for anger, a place that was closer to the analytical register than the emotional one. It felt like accounting. Like running a ledger on a company that had been committing fraud and finding that the fraud was not a flaw in the system but the business model. He didn't know what to do with it yet.
He filed it under pending sufficient data because that was the header he used for things he wasn't ready to act on, and because the alternative was a header he didn't have a name for that involved cold accounting against gods and he was not equipped for that column today. But the filing was not the same as dismissal. He was going to come back to this ledger. The ledger was going to get longer. 【WIL — Sustained Carry】 Active: load-bearing under grief-class weight WIL: +0. 1 | CHA: +0.
1 (present engagement maintained) The correct question. Asked in the correct register. Not answered yet, not because the answer is unavailable but because the person asking it is not ready to hear it in full. The Watchers are watching very carefully to see when that changes. They have placed no bets on the timeline. This is unusual for them. Dinner was good, which helped in the way that small concrete things helped when the larger abstractions were unresolvable.
Dez had found something edible that he'd initially misidentified as inedible, realized his error, and then described the process of realizing his error in enough detail that it was genuinely funny. Finn laughed. The laugh arrived without him managing it into existence, which he noted the way he noted the things that surprised him. Briefly, accurately, filed without elaboration.
"See, that's the correct response to my suffering," Dez said.
"Encouragement."
"That was laughing at you, not with you."
"I know. I'm choosing to reframe it." Marco made a sound that was approximately a laugh, which was high praise from Marco. Yuki smiled at the fire, which she did sometimes when she found something amusing and didn't feel the need to perform the amusement. Finn had learned to read the fire-smile. He was building a small catalog of things Yuki did that were only legible if you'd been paying attention for a while. He was paying attention. He had been for weeks. He didn't entirely know when that had happened either.
She glanced at him, once, later in the meal. The glance she used when she'd noticed something and was deciding whether to name it. She didn't name it. He was grateful. The gratitude was genuine and he didn't examine it further because some things didn't benefit from examination and he was getting better, slowly, at knowing which ones. The channel had nothing new. Thirteen active accounts. KwanHS not among them and not going to be.
He closed the tab and sat with the fire for a while before the watch rotation started. The question was still there. When did the circle get this big. He couldn't answer it, which meant either the answer was unavailable or it was available and he was refusing to look at it, and he suspected it was the second one and wasn't ready to look at it yet. What he could say, with the honesty the bark-sheet required even when the bark-sheet wasn't open, was this: it wasn't a decision. The responsibility hadn't been chosen.
It had arrived, and accumulated, and apparently it did not have walls. Did not stop at the edge of the camp or the edge of the group or the edge of the people he'd formally agreed to travel with. It extended, somehow, to people he'd never met, to usernames posting about wind direction, to a one-lensed pair of glasses in a cold fire.
And underneath that, in the register that was newer and colder and was going to require its own column eventually, it extended to a question about the system that had produced the cold fire in the first place. Eight hundred and thirty-three people. Not a weather event. A design choice. 【WIL — Functional Under Load】 Active: question unresolved, performance unaffected WIL: +0. 1 (sustained) | Load: open, unclassified Lying awake wondering where the sense of responsibility ends. The Watchers find this interesting.
They have bad news. It does not end. They have worse news. He already knows this. The question is not where it stops. The question is what he does with the part that doesn't. He did the watch rotation. The camp was sound and the route was clean and the group was breathing in the dark and he had done everything the day required. Being functional was not the same as being fine. He'd known that since Day 3.
The part that was new, the part that the operational column didn't have a header for, was the slowly arriving suspicion that the circle didn't close. That he'd started with himself and expanded to four people and the expansion hadn't stopped and wasn't going to stop and the thing at the end of the expansion, the thing that the Defiant Spark notification from last night was tracking and the Watchers were watching and the system was logging, was not a question about how many people he felt responsible for.
It was a question about the system that kept producing the need for the responsibility in the first place. And the cold anger was not going away. And the ledger was not closing. And somewhere in the space between a pair of broken glasses and eight hundred and thirty-three quiet accounts, the question had changed shape. Not when did the circle get this big. Who built the thing that makes the circle necessary. He didn't have an answer. He had a seed, logged, 1 of 3, accumulating.
He had a ledger with entries he was going to keep adding to. He had cold anger and a clean perimeter and three people breathing in a shelter and a forest that was, structurally and by design, a machine for producing the exact kind of loss that was keeping him awake. The fire was low. The watch was his. He watched.

Giữ khẩu khí thanh khiết — không văn tục, không phá chính trị.
Nhập môn