Chương 60: Forty Minutes

The channel data and the bark-sheet data had been running in parallel for a hundred and twenty days without intersecting meaningfully. He incorporated the information, sure, but back in his base camp, there was very little useable data.

"Please help, I don't know where I am and everything is trying to kill me," which was a large portion of the channel, wasn't all that useful. Useful information, was few and far between. That changed on the morning of Day 120, in a campsite three kilometers south of what he had started calling the "Haven's Reach Approach Corridor," otherwise known as the most accessible, generally well established and safer approach to the southern side of Havens reach. He'd been cross-referencing since 0600.

The channel archive was extensive, six weeks of approach corridor posts, timestamped, filtered for movement references, sorted by account. The bark-sheet's PK movement model sat beside it. Two data sets that had been developed independently for the same problem, and today, finally, they agreed with each other in a way that was useful rather than just consistent. The patrol window was 0900. Forty minutes. Primary cell only. In an area that would take him about a day to reach.

As far out from Haven's reach as he was, he was surprised to see a cohesive group of PKer's in the area. Knowing that soon he'd have to time moving through an area in less than an hour to avoid other players who were trying to kill him and take all his stuff was an odd sort of realization and he wondered how applicable the data would when he finally approached himself. But the confluence of his collected data on their movements and the channel data was good sign. Well, maybe not good, but useable.

He sat with that for a moment. Not celebrating, the secondary cell data was sparse enough that he was holding the full result at arm's length until he'd worked through the uncertainty, but noting that months of documentation had just produced a number, and the number was actionable, which was the only kind of number that mattered. Forty minutes. That's my window. I learned what a PK patrol window was by watching names go quiet in a chat room. Useful skill. Terrible way to learn it.

The secondary cell was the problem. Three accounts in the archive with irregular movement signatures that didn't fit the primary cell's pattern, not contradicting it, just operating on a different rhythm he hadn't fully modeled. Sparse data. Uncertain behavior.

Unknown threat weight, which meant he defaulted to maximum weight by protocol, which meant the corridor had a confirmed window and an unconfirmed variable and he needed to treat those as separate things rather than averaging them together into false confidence. He flagged the secondary cell HIGH on the bark-sheet and updated the model. The secondary cell nagged at him while he ate breakfast. Three accounts. Irregular movement. Different rhythm.

He caught himself doing the thing he always did with incomplete data sets, filling in the behavioral model with extrapolation, building the profile from the negative space around the data points. Three people. At minimum. Probably more, because the accounts he could track were the ones who'd made enough noise to leave a signature, and anyone running a secondary cell who was good at it wouldn't be leaving signatures at all.

These were people who had woken up naked in the same murder forest he had, faced the same hunger bars and threat tiers and thorn-serpent ambushes, and at some point had looked at the situation and decided that the optimal strategy was to kill other players for their stuff. He tried to build the decision tree that led there and found it disturbingly short. You spawn. You almost die. You learn the mechanics. You do die, but then you come back. You realize other players carry loot.

You realize other players are softer targets than a Level 12 boar. You do the math. The math works.

"The math works," he said to his breakfast, which was the last thing he wanted to be true about organized murder and was true anyway. That was the thing about data, it didn't care what you wanted it to mean. Back at the office, he'd built a customer churn model that had accurately predicted which clients would leave, and his manager had said great, now make it predict something useful, and he'd thought that was the most depressing misuse of analytics he'd ever see. He'd been wrong about that.

He'd been wrong about a lot of things. The most depressing misuse of analytics was sitting on a ridge in a blood-red forest building a patrol-window model for people who killed other people on a schedule. He wondered what they'd done before. The primary cell moved with coordination, which meant either military background or, more likely, statistically, gamers who'd played enough squad shooters to understand patrol rotation without formal training.

The secondary cell's irregular pattern could mean independent operators loosely affiliated, or it could mean someone smart enough to deliberately break pattern. He didn't know. He couldn't know. The data gave him movement and timing but not motivation, not capability, not whether the person behind the account had been an accountant or a Marine or a college kid who'd spent three thousand hours in Tarkov. He was profiling them.

The realization landed with the uncomfortable weight of a man who'd built customer segmentation models for a living and was now applying the same methodology to people who would stab him for his rations. Target audience analysis, his brain offered, in Brenda's voice. Who are our key stakeholders in the murder corridor?

"Thanks, Brenda," he muttered.

"Really helpful. Even in another dimension you're assigning me the worst projects." 【 AETHERFORGE NEXUS 】 Route Intelligence — Updated PK patrol window: 0900 daily, 40-minute gap (primary cell only) Secondary cell: status uncertain — flagged HIGH Corridor viability: CONFIRMED with Cautious Movement active The Watchers note the intelligence operation you ran alone for four months and are now summarizing into a single bark-sheet column.

They also note that the data required to produce this summary has been available for approximately six weeks. He read the notification, noted the Watchers' observation, and did not engage with it. They weren't wrong. The full operational picture, six weeks of channel monitoring, cross-referenced against behavioral patterns, distilled into a patrol window and a threat flag, fit in four lines on a bark-sheet. The four months of work that produced it didn't fit anywhere. He had not been looking for a place to put it.

The corridor viability confirmed with Cautious Movement active was the important line. Cautious Movement was the passive he'd built through four months of exactly this, moving through threat-adjacent territory without triggering contact through patience and route selection rather than engagement. It cost time and energy and produced the fatigue of sustained low-level alertness rather than the cleaner exhaustion of a fight. But it meant the corridor was passable.

The window, the passive, and the timing were all currently aligned. All three conditions available. Route viable. He updated the departure column. The corridor itself was two kilometers of compressed approach path between the broader Crimson Wilds and Haven's Reach's outer range, a natural chokepoint in the terrain that whoever had set up the patrol operation had identified before he had. He gave them credit for the site selection. Smart.

It meant anyone moving north toward the hub had two options: through the corridor, or a three-day detour around terrain that had its own threat profile. The corridor was the better route. The patrol counted on that. The 0900 window was either a genuine gap in the coverage or a deliberate funnel. He had spent six weeks trying to determine which. His current read: genuine gap, primary cell rotating out for resupply or resource activity, secondary cell either not covering the window or not covering it consistently.

The honest version of that read was that he was 73% confident in the genuine-gap interpretation and 27% aware that 27% was a lot of probability to carry through a chokepoint. He ran the math on the detour for the fourth time in two weeks. Three extra days. Terrain threat profile in the detour route included an unknown-large entry from yesterday's observation, two areas of dense thorn-serpent habitat, and exposure readings that spiked in the open ground east of the thickets.

Against a 73% genuine-window reading through a two-kilometer corridor at 0900 with Cautious Movement active. Unauthorized use: this story is on Amazon without permission from the author. Report any sightings. The corridor was better. Measurably. He updated the bark-sheet. He closed the bark-sheet and sat with the part he hadn't written down. The corridor was better. The math was clear. The window was confirmed.

And if the math was wrong, or the window shifted, or the secondary cell was covering the gap and he'd missed it, then the first human beings he'd interact with in months would be people trying to kill him. He let that sit for a moment. Really sit. Not as a data point. Not as a threat-weight classification. As a thing that might actually happen to a person who, a hundred and twenty days ago, had considered a tense email exchange with the accounts receivable department to be a high-conflict situation.

He had killed boars. He had killed thorn-serpents. He had killed approximately two dozen thorn-rats in the early days with a rock and a level of desperation that he preferred not to revisit. He had built a combat methodology that was functional and efficient and had been validated across four months of threat engagement in the Crimson Wilds. He knew how to fight. He did not know if he could fight a person. The distinction had been abstract until now. Theoretical.

Something that lived in the PK model as a threat category rather than a scenario he might walk into tomorrow morning. But the corridor was tomorrow morning, and the patrol was real, and the people running it had already demonstrated, through the quiet math of names that stopped posting, that they did not have the same hesitation. A boar charged because it was territorial. A thorn-serpent struck because you stepped on its ambush zone. They weren't choosing anything.

They were running code, biological threat response, stimulus and reaction. The PKers were choosing. They'd looked at another human being, scared, alone, trying to reach the same safe zone they presumably knew existed, and decided that person was a resource to be harvested. And if he met them, what was he? A data analyst from Sacramento who'd spent four months learning to kill animals with increasing efficiency and had never once been in a fistfight. His high school had a zero-tolerance policy.

His college roommate had been a pacifist who grew herbs on the windowsill. His most violent pre-AetherForge experience was the time Dave had accidentally hit him in the face with a foam sword at the reenactment society's medieval fair, and Dave had apologized for three weeks afterward and bought him a beer.

"Cool," he said.

"So my combat resume against humans is: got hit with a foam sword by a man who cried about it. Very threatening. The PKers should be terrified." The forest, as usual, did not weigh in. He appreciated the restraint. He was doing enough weighing in for both of them. 【 AETHERFORGE NEXUS 】 Exploration XP: +90 Approach corridor mapped. Route window integrated. The Watchers note you have been building toward this for six weeks. They note the notation took eleven minutes.

They also note you have written "ten to fourteen days" in the column and then looked at it, which they are choosing to interpret as a personality trait rather than a methodology. Eleven minutes. He had no argument with that. Haven's Reach was a couple of weeks north depending on corridor transit time and the terrain above it, which he hadn't fully mapped yet.

The range was real, not a hedge, just an accurate acknowledgment that his post-corridor data was thinner than his pre-corridor data and the uncertainty was honest. He put three weeks in the column because he was being optimistic. Three weeks. He had been alone for a hundred and twenty. The ratio was starting to shift from overwhelmingly solo toward something that didn't have a clean label yet. He ate the rest of his breakfast and broke camp. The day went methodically.

He was three kilometers south of the corridor, which put him outside the patrol range he'd modeled for the primary cell, so the afternoon was standard transit, trail reads at recalibrated confidence, one thorn-serpent sign that was old enough to ignore, one Aethershard resource node he stopped to assess and decided was worth the ten minutes. He took what was worth taking and moved on.

The data analyst in a murder forest approach to resource extraction: spend nine minutes deciding if the resource is worth ten minutes. Efficient. The unknown-large from yesterday's transition zone didn't resurface. He maintained the HIGH flag and kept it in the peripheral assessment rather than retiring it. Absence of contact wasn't the same as absence of threat. He'd learned that one empirically and had not found the experience enjoyable enough to repeat it.

By mid-afternoon he had a cleaner read on the corridor's approach terrain than he'd had at any point in the planning stage. The sightlines from the southern approach were better than he'd estimated from the channel data, whoever had been posting coordinates hadn't been working from the same vantage he was currently using. Small difference. Useful one. He updated the corridor entry plan. The bark-sheet was getting dense.

He flipped through the columns while he walked, threat model, resource inventory, route data, XP projections, the PK operation summary, the channel cross-reference index. Months of a man talking to himself in notation. He'd started it because data without documentation degraded faster than data with it, and the alternative was losing track of things in a situation where losing track of things cost Echoes.

He had kept it because it turned out that writing things down was the closest he'd come to having a conversation for most of those hundred and twenty days. He wasn't examining that too closely. Camp at 1720. Site on a low ridge with the corridor visible in the northern distance, far enough to be outside the patrol range, close enough that the 0900 entry was a forty-minute transit in the morning. He set the perimeter in twenty-eight minutes. Better than yesterday. Trend line positive.

【 AETHERFORGE NEXUS 】 Exploration XP accumulated — Day 120 Total: 2, 890/30, 000 The Watchers observe the bar. They note you have been observing it more frequently since departure. They find the frequency informative. 2, 890 out of 30, 000. The bar moved. Not fast, but it moved.

He had a framework for understanding slow progress that had been built across a hundred days of exactly this, and the framework said: the bar moving was the bar moving, and the alternative was the bar not moving, and he had seen the alternative and had opinions about it. He ate, managed the meters, updated the bark-sheet. Corridor entry: tomorrow, 0845, Cautious Movement active, secondary cell flagged, window confirmed at 0900. He had everything he needed. The plan was good.

He sat with the channel archive for a while after. The approach corridor thread had twelve active posters in the last two weeks. Twelve accounts, some of them posting movement questions that had the texture of people who didn't know about the patrol pattern and were trying to figure out the safest route north. He knew the safest route north. He had the window, the timing, the confidence level, the secondary-cell caveat.

He could post it in three lines and those twelve accounts would have actionable intelligence instead of guesswork. He didn't post it. The calculation was the same as it had always been, unknown accounts, unverifiable intentions, the risk of broadcasting route intelligence in a public channel where the patrol operation might be reading it. The numbers hadn't changed. The parameters hadn't changed. He stared at the twelve active accounts and thought about the people behind them.

Twelve usernames attached to twelve people who were trying to get north, same as him. Some of them were going to hit the corridor without the patrol data. Some of them were going to hit it at the wrong time.

Some of them were going to become the next quiet disappearance in the channel archive, another username that just stopped posting, and the only person who'd notice the pattern was a data analyst on a ridge three kilometers south who had the information that might have prevented it and had chosen not to share it. The logic was sound. He'd run it. The channel was compromised, the PKers might be reading it, broadcasting the window would burn the window. Tactically correct. Operationally responsible.

The kind of decision that looked clean on a bark-sheet and felt like something else entirely when you were the one making it in the dark while twelve people you'd never met were making plans based on information they didn't have. Four months ago, the hardest decision in his professional life had been whether to tell his coworker Marcus that the pivot table in the Q3 report was pulling from the wrong data source. He'd agonized about it for two days.

Two days, over a spreadsheet error that would've cost the company maybe eight thousand dollars and Marcus maybe a mildly awkward conversation with his supervisor. Now he was sitting on intelligence that might keep people alive, running a cost-benefit analysis on sharing it, and the cost-benefit analysis was telling him to keep his mouth shut. And he was going to keep his mouth shut. Because the analysis was right. Sacramento Finn would not recognize this person.

Sacramento Finn meal-prepped on Sundays and worried about his credit score and once spent forty-five minutes on the phone with his internet provider because the upload speed was six megabits below what he was paying for. Sacramento Finn had never considered whether he was capable of killing another human being because Sacramento Finn lived in a world where that question was theoretical for most people and stayed that way. He wasn't in Sacramento.

Tomorrow he was going to walk into a corridor where people killed other people for loot, and his plan was to not be seen, and if that plan failed, the next plan was — what? Run? Fight? The combat methodology worked on boars. Would it work on someone who thought like he did, who'd built their own model, who'd looked at the same mechanics and arrived at a different conclusion about what to do with them? He didn't know.

He added it to the list of things he didn't know, which was getting shorter in some columns and longer in others, and the column it was getting longer in was the one he liked least. He closed the archive and went to sleep.