Chương 87: topography

The watch rotation setup took twelve minutes, which was eleven minutes longer than it needed to be because Marco kept second-guessing his quadrant and Dez had opinions about the overlap coverage that were, objectively, not wrong. Finn let them work it out. He'd found that letting them work things out produced better retention than telling them the answer, which was either good pedagogy or the beginning of something he didn't have a label for yet.

He'd spent the afternoon on route planning while the others broke camp, and the math hadn't cooperated. It never cooperated anymore. In his previous life, topography had been a word that existed somewhere in the vicinity of geography textbooks and hiking blogs he'd never read.

At DataVault, the closest he'd come to elevation data was a 3D bar chart Marcus had built for a client presentation, which had technically represented revenue by region but which Marcus had rotated at seventeen different angles during the meeting because he thought it made the Q2 dip look less catastrophic. It did not. It looked like a bar chart someone had rotated seventeen times.

Now topography was the difference between a four-day transit and a three-week detour, and the Crimson Wilds did not believe in straight lines. The problem was the terrain between here and Haven's Reach. On a flat surface, clean terrain, no obstacles, they were maybe nine days out. Possibly eight if Marco's pace held and nobody got ambushed by anything with more teeth than manners. But the Crimson Wilds was not a flat surface.

The Crimson Wilds was a series of increasingly hostile geological suggestions about where you were and were not allowed to walk, and the penalty for guessing wrong was not a recalculation. It was a canyon. He'd learned this on Day 47. Taken a route that looked efficient on his mental map, followed a ridgeline that curved promisingly northwest, and watched it terminate in a limestone drop-off that went down forty meters into a drainage basin with no exit he could identify from above.

If he'd committed to the descent, if he'd been even slightly less cautious about the angle of that slope, he'd have spent three days climbing back out with no reliable water source and whatever lived at the bottom of limestone drainage basins in a forest designed by entities who thought mortality was entertainment. He'd added "verify descent routes before committing to elevation loss" to the bark-sheet that afternoon.

In retrospect, that entry was doing more work per square centimeter than anything else he'd written. The route to Haven's Reach threaded between two ridge systems that ran roughly parallel for about sixty kilometers before diverging. The northern ridge was compromised by the world boss trajectory, which ruled it out entirely. The southern ridge was navigable but fractured by seasonal drainage cuts that turned into miniature gorges during the wet cycle.

Threading between them meant reading the terrain daily, adjusting for washouts, and accepting that some mornings the route he'd planned the night before would be functionally imaginary because a drainage channel had decided to be four meters wider than it was yesterday. And that was just the geology. Layer the fauna on top. Thorn-stalker territories that had to be routed around because thorn-stalkers did not negotiate. Boar wallows that blocked natural chokepoints.

The raptor corridor they'd skirted on Day 148 that Finn had mapped as a permanent no-go zone because the raptors had not received the memo about it being a shared-use trail. Three weeks, minimum. Probably closer to four if they wanted to arrive alive, which Finn had identified as a priority early in the planning process and had not yet been talked out of.

"You're doing the face again," Dez said, passing him on the way to the fire.

"I don't have a face."

"You have a face that means the route math isn't working. It's the same face you made when the drainage channel was wider than your estimate."

"That face is called 'being correct about a problem,' and I'm not apologizing for it." Dez made a sound that might have been a laugh or might have been judgment. The two were increasingly hard to distinguish, which was either a problem or a feature of having traveled with the same three people for long enough that they'd developed fluency in his operational expressions. Yuki waited until the other two had settled before she asked.

"Why don't you post in the channel?" Not aggressive. Not the setup for something else. She asked things the way she moved through camp: efficiently, without wasted motion, selecting for information she'd identified as missing. He'd learned to take her questions seriously because she didn't ask the ones she already knew the answer to. He had two answers. He gave her the first one.

"Location security. Posting confirms you're alive, which confirms you're worth finding. The PK network runs pattern analysis on active accounts, post frequency, timing, content, and builds movement models. I've been doing it to them for five months. They're doing it to everyone." She nodded. She did not move on, which meant she'd clocked the answer as incomplete. Of course she had.

"That's not all of it," she said.

"No," he said.

"It's not." He looked at the fire for a moment. The fuller answer was older and less clean and he wasn't sure it still fit the shape it had when he'd made it. He'd thought about posting in the early weeks. Drafted things. Deleted them. The channel had felt like standing in a room where people kept disappearing and he hadn't been able to make himself add his voice to a roll call that was, functionally, a countdown. So he hadn't.

And then he hadn't again, and again, and the not-posting had hardened into something that felt like a decision but had really been an absence that went uncorrected long enough to become structural. That was the honest version. It was also the version that required him to explain five months of watching names go quiet without explaining why he'd kept watching anyway, and that explanation had more in it than he was currently prepared to unpack in front of a campfire. Did you know this text is from a different site?

Read the official version to support the creator.

"The threat model is the main reason," he said, which was true and partial, and he noted both as he said it. She accepted this. The accepting had the quality of a provisional filing. She'd taken the answer and put it somewhere accessible rather than somewhere final, which meant she'd return to it when she had more data. He was becoming fluent in how Yuki stored information. He wasn't sure when that had happened. Then she asked the thing he hadn't thought about yet, which was her signature move.

"Haven's Reach will have people who've been posting," she said.

"People who've helped each other through the channel. That has, I don't know. A social texture. Showing up having never participated might read a certain way." He hadn't thought about this. He thought about it now, and the thinking was uncomfortable in the way of correct observations he'd failed to generate himself.

"Yeah," he said.

"Probably."

"Do you know if everyone starts in the Crimson Wilds?" She was looking at the channel tab, still open on her own display.

"The numbers are so low now. If this is the only starting zone, and attrition has been this bad..."

"I don't know," he said.

"The early posts were dense enough to suggest a mass-spawn event. Could be biome-sorted. Could be there are people who started in a safe zone and we have no way to track them because they never needed to post about water sources."

"So there could be hundreds of people at Haven's Reach who never saw the Crimson Wilds at all."

"Or thousands. The channel's been a survival tool out here. At a hub it becomes something else." Something else. He turned that over. He'd been reading the channel as intelligence: resource locations, PK patterns, threat indicators, the occasional useful observation from someone who was paying the same kind of attention he was. At Haven's Reach it would be social infrastructure. History.

People who'd posted their way through the worst months and built something between them, a shared record of survival that he'd been standing outside of, reading but never adding to, for 161 days. He thought about the route again, the three-to-four weeks of terrain threading that still separated them from that social infrastructure.

Twenty-something days of ridge navigation and drainage-channel gambling, and at the end of it he was going to walk into a settlement full of people who'd been building community while he'd been perfecting the art of not dying alone. Wonderful. Truly the social onboarding experience he'd been hoping for. At DataVault, new employees got a welcome packet and a thirty-minute orientation with HR.

Here, the orientation was going to be "hello, I've been silently reading everything you've posted for five months, I know your water source preferences, and I have opinions about your route planning. Please don't find that unsettling." He thought about LiraT. He'd read her posts the way he read everything: for data, for pattern, for what the content said about the person generating it. He'd drafted responses twice and deleted them.

She'd been posting useful things into a channel he was lurking, and when he arrived at Haven's Reach and she was there, if she was there, he was going to be a stranger who knew her posting cadence and her preferred water source locations and had never once said a useful thing back. He did not find this comfortable. 【 CHA — Honest Engagement 】 Social interaction: question without clean answer, honest partial response CHA: +0. 1 | WIL: +0.

1 Yuki asked one question and he has now been thinking about it for four hours, during dinner, during watch setup, and currently during watch itself. The Watchers find his distress about a chat forum deeply, genuinely entertaining. He has survived wolves and floods and a world event and two deaths, and the thing keeping him awake tonight is his posting history. Or lack thereof. He ran watch and thought about it. He ran the route check in the morning and thought about it.

He pulled the bark-sheet and re-examined the southern approach for the third time, tracing the ridge contour with his thumbnail and trying to estimate where the next drainage fracture would force a lateral correction. The answer was "somewhere between here and there, and you won't know until you're standing at the edge looking down." He found this deeply reassuring in the way that a person finds anything reassuring when the alternative is screaming into the canopy. Three weeks of this.

Three weeks of daily route recalculation, terrain that lied about its own accessibility, and the persistent suspicion that the Crimson Wilds' geological features had been designed by the same entities who thought world bosses were a fun surprise. Every ridgeline that looked passable from a distance had a personal policy about not being passable up close. Every drainage channel that appeared crossable at one point was, at the actual crossing point, a muddy negotiation with gravity that gravity usually won.

He did not resolve the channel question, which the bark-sheet's TBD column was getting increasingly full of. Questions that were real and open and didn't have clean answers yet and weren't going to until he had more data than he currently had. The TBD column had started as a placeholder. It was becoming something else.

He wasn't sure he liked what it was becoming, which was a record of all the things he was carrying without resolution, and the list was getting longer in a way that suggested the Crimson Wilds had been, among other things, too loud with immediate problems to leave much room for the unresolved kind. He had room now. He had people who asked him questions with gaps in them. He had a TBD column that was filling up.

He had a route to Haven's Reach that required him to care about contour lines, which was a sentence that would have meant nothing to him eight months ago and now meant the difference between a productive day and a three-day recovery from a bad elevation commitment. He still did not post in the channel. He told himself he'd think about it more before Haven's Reach. He had time.

Three to four weeks of it, assuming the terrain cooperated, which it would not, so call it four to five weeks of increasingly creative route adjustments and at least two arguments with Dez about whether a given slope was "steep" or "inadvisable." The channel would be there. He would think about it more and then decide, deliberately, what kind of presence he was going to be in a room full of people who'd been building something together while he'd been standing outside reading the blueprints.

The route check came back clean. He put the bark-sheet away. He noted, without attaching anything to it, that the TBD column now had an entry that had nothing to do with threats or resources or operational timelines. He ran the morning count. Fourteen active accounts. LiraT: no new posts. Northern movement confirmed from the last update, four days prior. He closed the tab and started walking.

【 Route Assessment — Filed 】 Southern approach: viable, fracture-dependent Estimated transit to Haven's Reach: 21–28 days (terrain-adjusted) Daily recalculation: mandatory Confidence in estimate: moderate, declining He has added "topography" to the list of things he now cares about that he could not have defined at a dinner party eight months ago. The Watchers would like it noted that the list is long, that it is growing, and that dinner parties are no longer a relevant unit of social measurement.

The forest is the dinner party now. It is not going well.