Chương 83: It'd be nice if this were readable.

The third world boss notification arrived at 0700, which was approximately the same time the forest started behaving wrong. He'd been tracking the leading-edge disturbance since Day 131, when the fauna displacement first showed up as a pattern he couldn't account for through normal territory-cycling. Each reading had been worse than the prior one. It was getting closer. The third notification confirmed both the getting-closer and the trajectory, which he'd had at confirmed-NNW-to-SSE for three weeks.

It also clarified the distance in a way that was useful without being reassuring, because the distance had been significantly reduced from the prior reading for two consecutive readings now and the rate of reduction was suggesting an arrival window he preferred not to name out loud. The notification's tier classification was still UNREADABLE. He sat with this for a moment and let the frustration have its full shape, because he'd been managing it for three notifications now and it had earned the space.

At DataVault, if a data source returned UNREADABLE, you called IT. Phil answered on the third ring, sighed with the weight of a man who had been doing this for eleven years, asked if you'd tried refreshing, and then eventually fixed the problem while making it clear that the problem was you. It was not a great system. It was a system. There was a Phil.

Here, the help desk was three divine entities who had designed the spreadsheet, were actively trying to kill him with it, and had chosen to render the most important cell in the document in a font only they could read. There was no Phil. There was no third ring.

There was a notification that said UNREADABLE and a forest full of evidence that the thing it was declining to classify was large enough to break canopy lines and real enough to push the wildlife south, and Finn was supposed to route four people around it using the analytical equivalent of a weather forecast that said something is coming, it's big, we've elected not to tell you what.

He'd tried to work around the edges of the unreadable section across all three readings and had gotten exactly nowhere, which told him one of two things: either the classification system was using a category that hadn't appeared in his prior data set, or it was a category the system was actively declining to show him. He'd assigned fifty-fifty probability to each and then moved on, because assigning probability to a thing you couldn't distinguish didn't change either probability. This was the part that sat wrong.

Not the threat. Threats he understood. Threats had shape, trajectory, countermeasures. He'd been managing threats for a hundred and fifty-three days, and while none of them had been enjoyable, they had all been legible. He could read a wolf pack's approach angle. He could model a thorn-stalker's ambush radius. He could assess a PKer's patrol corridor from three data points and route around it before breakfast. The information might be bad, the odds might be terrible, but the information was there.

This thing, whatever it was, had been moving through his operational space for twenty-two days and the best the system would give him was UNREADABLE and a distance metric that kept getting smaller, and he was supposed to make routing decisions for four people based on the analytical equivalent of something's out there and it's probably fine but we're not going to tell you why we think that. He was a data analyst. The absence of data was not data.

It was a gap shaped like a threat that he couldn't model, couldn't classify, and couldn't do anything about except walk away from, which was what he was doing, and the walking-away was sound tactical practice and also deeply, personally irritating in a way that his threat model did not have a column for. He closed the notification and looked at the forest.

The terrain was doing something he'd seen once before, on Day 61, when the first major leading-edge disturbance had pushed the fauna south and left the undergrowth disturbed. That version had been subtle. A few branches snapped high up where the canopy met itself, some churned root earth at the base of the larger trees, birds displaced from a section of the forest they'd been reliably using for two weeks.

You had to know what a normal section of Crimson Wilds canopy looked like to see that something had passed through it. This version was not subtle. The canopy break ran east to west as far as he could see in the morning light, a ragged line where the upper branches had been snapped or bent back by something that had moved through at a height of maybe thirty meters and with enough force that the trees hadn't sprung back.

Below the break, the forest floor was churned in sections, not claw marks, not tracks he recognized, more like the aftermath of something immensely heavy pressing down from above at irregular intervals, leaving craters of compressed earth and splintered root systems where the soil had simply given way under the weight. Between the impact points, the undergrowth was undisturbed, which meant whatever had passed through wasn't dragging itself along the ground. It was stepping. Or landing.

The spacing between the impact points suggested a stride of eight to ten meters, which was a number he ran twice and did not enjoy either time. The fauna displacement was audible before it was visible: the forest to the north was quiet in a way that had nothing to do with the time of day, broadcasting that something that hunted on a scale the local ecosystem couldn't process was in the vicinity or had recently been.

He ran the route diagram in his head and then did it again, because the first version had produced an answer he didn't like and the second version produced the same answer with the same problem, which meant the answer was probably correct. The northern corridor was compromised for at least the next six hours, possibly the next day. The disturbance was too recent and the fauna behavior in the affected section was too suppressed to read as cleared-and-recovering.

Whatever had moved through had done so within the last twelve hours and might still be in the sector. He had a western alternative. It followed a lower ridgeline where the canopy thickened into old-growth Crimson timber, the kind that was dense enough to block most sightlines from above and tangled enough at root level to slow anything larger than a boar.

Slower going for them, but the resource nodes were better and there was a section around kilometer five where the ridge dropped into a shallow ravine with limited visibility on the western approach. He'd been routing around it because it added half a day and he'd been working with a Haven's Reach timeline that was already revised once. Running the numbers now with the northern corridor unavailable: the western alternative was the correct route.

It was also the longer route, and he was choosing it because of information he couldn't fully read, about a threat he couldn't classify, for reasons the system had decided he didn't need to understand. Full-service murder forest. Not only trying to kill him but improving his routing efficiency while declining to tell him what, exactly, it was routing him around. If this were a customer experience, he'd have left a one-star review. Product actively attempts to consume user. Help documentation deliberately obscured.

No option to speak with a representative. Would not recommend. He turned to the group.

"We're going west," he said.

"Northern section has fresh disturbance. The route's viable again by late afternoon, but we'd lose more time waiting than rerouting." This was technically true. He'd calibrated the sentence to be technically true in a way that communicated everything necessary without requiring him to explain the unreadable notification that had prompted him to look at the northern terrain at all.

The technically-true statement was, he reflected, a professional skill he hadn't expected to need in a survival context, but it turned out that managing information flow for a small team operated on exactly the same principles as managing information flow in a quarterly client briefing: give them what they need, frame it in terms of the action required, and save the part where everything might be catastrophically worse than the framing suggests for a conversation you're not ready to have.

He'd been adequate at this at DataVault. He was apparently adequate at it here. The word adequate was doing a lot of work in both contexts. The story has been stolen; if detected on Amazon, report the violation. Marco processed this in the Marco way, which was immediate and uncomplicated: he reoriented west.

He didn't ask why, which was either trust or Marco's natural disposition toward treating routing calls as settled information once they'd been issued, and Finn had never successfully distinguished these in Marco's case and had stopped trying. Yuki looked north. Then at him.

"Best path?"

"Yes." She accepted it and picked up her pack. Dez was already looking west with the expression of someone recalculating the structural geometry of the new route, which was a face he'd learned to recognize and which was usually productive. Dez's route recalculations had started producing useful secondary data about two weeks ago, the kind that emerged from his engineering brain treating the terrain as a problem to be solved rather than an environment to be navigated.

He'd been adjusting his own route briefings to leave space for Dez's recalculations, which took about four minutes and occasionally produced a suggestion worth integrating.

"The western section has a ridge approach around kilometer three," Dez said, four minutes later.

"If we take the lower line, below the ridge, not along it, we keep better tree cover and lose maybe two hundred meters of elevation gain."

"That's the line I had," Finn said. Dez looked surprised in the way that was becoming routine. He nodded. They moved.

The notification fired two hours into the western route, during a water break at a resource node that was better than anything the northern section would have offered: 【World Event — Approaching】 [Fragment — classification: UNREADABLE — distance: significantly reduced from prior reading] Leading-edge terrain disturbance: CONFIRMED (12hr window, active) Northern corridor: compromised, recommend avoid Route adjustment: +0. 5 days | INT: +0. 1 Route change presented as navigation. Accurate. Also something else.

Both descriptions apply, and the Watchers are entertained by the calibration required to make one true without acknowledging the other. Walking south. Prudent, one of them notes. Boring, says another. They are not wrong on either count. It would kill you. You know this. They know this. The shared understanding does not stop one of them, the one who has been watching since the first terrain disturbance, from asking no one in particular: but doesn't he want to know? You do not hear this. You are walking south.

INT: +0. 1 for the route adjustment. Nothing for the question. The question was not for you. He read the Watcher note with the feeling of someone whose phrasing choices were being evaluated by entities with very long memories and no patience for the technically-true-versus-actually-true distinction. He was not going to apologize for the distinction. The distinction was doing useful work. He noted that the Watchers had called it accurate, which they would not have done if it were dishonest. Just incomplete.

I am routing around an unclassifiable world event by calling it road optimization, he thought, looking at the resource node's water quality, which was excellent and would not have been available on the northern route. This is technically true. And of course I'm curious, but not enough to lose another Echo for it. He filled his canteen. Then Dez's, because Dez had put his pack down in a way that suggested the thought of bending to reach it was more than he currently wanted to budget for.

He didn't announce doing this. He just did it and set it back next to the pack. INT +0. 1. The Nexus was tracking that the world boss had been forcing him to develop a new kind of synthesis, integrating the unreadable notification data with terrain-readable evidence and route-modeling in a loop that produced reliable outputs from unreliable inputs. The system that was trying to eat him was also, apparently, leveling up his analysis skills. He'd have preferred a more conventional professional development program.

One with a manual, possibly. And a Phil. The risk section came at kilometer seven. The old-growth canopy that had been sheltering them since the ridge thinned out here, the trees spacing further apart where the soil transitioned from the deep loam of the ridgeline to a shallower layer of rock-laced clay that couldn't support the root depth the larger trees needed.

The result was a gap, maybe forty meters wide, where the canopy opened up to sky and the western route crossed exposed ground with clear sightlines from the higher terrain to the north. Anything on the ridge above, anything at all, could see four people crossing that gap before those four people had a meaningful read on what was looking.

He'd flagged it in the initial route assessment and built in a timing adjustment to cross when the light was wrong for advantage from above, and a movement protocol that kept Marco in the center and minimized the group's lateral spread. He briefed this one before they reached it. Not all of it.

Not the full threat assessment, because the full threat assessment involved the world boss notification data and that wasn't a conversation he was ready to have at this juncture, where this juncture meant while we are still weeks from Haven's Reach and there is nothing useful any of us can do about an unclassifiable approaching event except walk the other direction, which we are already doing. He briefed: gap, forty meters, keep formation, quick pace, don't stop for anything that isn't an actual threat.

Marco understood this. Dez understood this. Yuki looked at the gap, looked at him, looked at the gap again, and said: "How long has that been on your list?"

"Since this morning," he said, which was accurate.

"What else is on the list?" He looked at her.

"Nothing that changes what we're doing right now." She held his gaze for three seconds with the expression she used when she'd received an answer that was technically complete and practically insufficient. Then she picked up her pack. They cleared the gap in forty-two seconds. He counted without meaning to. By the time they made camp that evening, his mood about the day had turned around considerably.

The western detour had produced two supply nodes better than the northern corridor would have given them, and he knew the northern corridor's resource density well enough to make that comparison with confidence. The first node had Crimson Sap. A meaningful cache of it, more than he'd seen in one location since Day 148 when his stores had dropped to operational minimum and stayed there. He'd been rationing it against the potion supply ever since. Yuki had found it first.

She'd also known a harvesting technique he didn't, slower, more deliberate, the kind of thing that came from a medical background applied sideways to a survival context. It yielded thirty percent more from the same nodes without destabilizing the bark. He noted the technique. He noted that she'd shown him without framing it as instruction, which had made it easier to receive. The second node was Aether Shards.

A cluster, not a scatter, the kind of dense deposit the channel posts had been calling a "merchant stack" for the last two weeks. He'd been reading those posts with the detached interest of someone who had nowhere to spend currency. That was changing. Haven's Reach was still weeks out, but the channel traffic about it had a consistent economic thread running through it: stall prices, merchant inventory rotations, what shards would actually buy.

A warm meal in calm conditions, according to one reliable poster, ran three to five shards. Gear repairs were higher. Information was negotiable. He divided the shard haul evenly at camp. Marco looked at his share with wide eyes. Dez asked how close they were to Haven's Reach again. Yuki said nothing, but she put her portion away with the careful attention she gave things she considered valuable. He updated the inventory and then updated the bark-sheet timeline. The detour had not cost them. It had positioned them.

He filed this in the correct column and closed the bark-sheet. The world boss notification was sitting in his status panel, third instance, unreadable tier. He ran the trajectory math again with the updated distance reading and got a window he didn't like. He updated the model and filed it. The filing was a productive act.

He had a tendency to think of the things he couldn't act on as problems, and the world boss notification kept prompting this tendency, because the unreadable tier was an unsolved problem and unsolved problems accumulated weight in his thinking that resolved problems didn't. But it was also navigation data, and he was using it, and that was the functional relationship to have with a threat you couldn't yet engage.

The fact that it was also the kind of threat that broke canopy lines thirty meters up and left stride craters eight meters apart was information he was going to continue managing in the technically-true register until such time as a more complete register became necessary, or possible, or anything other than terrifying. He'd been a data analyst. Data you couldn't immediately use was still data.

You kept it until the model could use it, and you updated when the model could update, and you did not let the gap between current information and actionable information become a crisis it hadn't earned yet. He closed the panel. The camp perimeter was clean. The resources were better than yesterday. The risk section was behind them. He went on watch. The forest to the north was still quiet.