REBORN BEFORE ZERO: I already know how the world ends

THE SHAPE OF THE TRAP

The document appeared in his inbox at 7:43 on a Tuesday morning, forwarded from a departmental shared folder by a routing algorithm that had no opinion about what it was carrying.

Zayden was eating toast when his laptop chimed. He read the subject line and put the toast down.

The document was an internal planning brief titled Regional Activation Readiness Assessment. It had been generated by the logistics analysis he had been building for Thessaly Morne over the past two months, and it laid out, in the clean functional language of emergency management planning, a deployment framework for emergency distribution centers that would activate in response to what the brief called a Tier Three biological disruption event.

He read it twice. Then he read it a third time, more slowly, looking at it the way you look at a map you have seen before in a different context. Every location. Every timeline. Every resource allocation decision.

He had built most of this. He had built it over fourteen months in his first life, believing he was doing genuine emergency preparedness work. He had been proud of it. He had thought of it as the most useful thing he had ever done.

He was looking at a deployment plan designed to ensure that in the aftermath of a manufactured outbreak, the organizations that manufactured it would be positioned to control the primary resource distribution nodes in twelve metropolitan areas. Which meant controlling who had food, water, medical supplies, and communications access. Which meant controlling everything.

He closed the document.

He sat in the kitchen for about three minutes, doing nothing.

Then he went to his contacts and found Drexen's number.

* * *

He did not tell Drexen everything. Not yet. He was not ready for that conversation and Drexen was not ready to receive it. What he did instead was bring Drexen in on a specific problem framed in a language that Drexen could work with.

"I have a concern about a planning document that's come across my desk," he said, when Drexen picked up. "I'm going to email it to you. I want your read on the security implications of this deployment architecture."

He did not send the actual document. He sent a sanitized version he had reconstructed from memory, with the identifying elements removed and the structural logic intact. It described the same framework using different language. He wanted Drexen's assessment of the framework's vulnerabilities without compromising the information that would tell Drexen more than he needed to know right now.

Drexen called back forty minutes later.

"This is bad planning," he said. The directness was characteristic. "Whoever designed this has these distribution centers in positions that would make them indefensible in any significant breakdown scenario. You've got concentration without redundancy, and the access control model assumes continuous institutional support."

"Right."

"If the institutional support isn't there, whoever is physically in control of these locations controls the resources. There's no distributed fallback."

"That's what I was seeing too," Zayden said.

"Is this from a client?"

"I can't get into the source right now. But I want you to think about what an alternative architecture would look like. One with distributed control, multiple redundancies, community-level access rather than centralized management."

A pause. "That's a lot of work."

"I know. I want to start on it this week."

Another pause, longer. "You're not just doing theoretical planning, are you."

Zayden said, "I want to build something real that can function independently of whatever institutional frameworks are currently in place. I have a property. I have the beginnings of a supply architecture. I need someone who understands operational security and can design a distributed resource management system that doesn't depend on central control."

"Why?" Drexen said. One word.

Zayden thought about the document in his inbox. About twenty-two thousand dollars in a money belt and a storage unit full of supplies and a property in the outer county. About a list on his laptop that kept getting longer.

"Because I think the gap between what emergency planning assumes and what reality might require is larger than most people are accounting for," he said. "And I would rather build the bridge before we need it than during the crossing."

Another pause. "What's your timeline?"

"Aggressive."

"Define aggressive."

"I want operational capacity at the primary location within six weeks."

Drexen was quiet for a moment. "That's very aggressive."

"I know."

A long pause. Then: "Okay. Send me the facility specs. I'll come look at the property this weekend."

Zayden let out a breath he had not been aware of holding. "Saturday morning. I'll send the address."

* * *

The problem with the document was not just what it contained.

It was that it had been routed to him.

In his first life, he had not seen this document until six months into the outbreak. It had appeared in a shared file he stumbled across during a scavenging run through an abandoned office building that had housed one of Thessaly's partner organizations. By then, reading it had been like finding a map of a battle you were already in the middle of.

Now he had it ten weeks before the event it described. And he had not been supposed to get it. The routing algorithm had sent it because his access level had been elevated since Thessaly's decision three weeks ago, and the access level expansion had included a set of shared folders that the algorithm did not realize he had not previously been cleared for. An administrative error. The kind that happened in large organizations where the left hand and the right hand did not communicate.

He needed to decide what to do about this.

Option one: say nothing, wait to see if anyone noticed. This had the advantage of not drawing attention, but the disadvantage of leaving him uncertain about whether the mistake had been logged somewhere. If someone audited the access records and noticed he had downloaded a restricted document, the resulting question would be difficult to answer with anything that sounded reasonable.

Option two: flag it as a mistake proactively. Go to Thessaly, explain that the routing had given him access to something above his clearance level, hand it back. This was the move that an innocent employee would make. It cost him the document but it built trust.

He had already memorized the document. He did not need the file. He needed the trust.

He sent Thessaly an email that afternoon, professionally worded, noting that the automated routing had apparently included a planning brief in his distribution that seemed to be above his standard clearance level, and he wanted to flag it in case it was a permissions error on the system side.

She responded within twenty minutes.

Good catch. I'll have IT look at the access configuration. Thanks for flagging immediately.

He read her response and thought: one point to me.

He went back to work.

* * *

Seraphine came to Myrren on a Saturday morning, exactly as scheduled, and spent three hours walking the property with the systematic attention of a person building a complete picture.

She asked good questions. She identified two things he had missed in his initial assessment: the water table depth in the eastern section of the property made a secondary well feasible for almost nothing, and the old equipment building on the north end of the facility had a foundation structure that would make it the most defensible single structure on the property in the event of needing to hold a position.

He wrote both observations in his notebook while she was still talking.

She noticed him writing. "You write everything down," she said. It was observational rather than critical.

"I lose things I don't write down."

"What kind of things?"

"Useful things that people say. Good ideas that show up at bad times. Plans that make sense when you think of them and stop making sense later unless you have the original version to check against."

She looked at him for a moment with the assessment expression she did not seem to be aware she was doing. "You think ahead," she said.

"I try to."

"Further than most people."

He kept his face neutral. "It's part of the work."

She went back to looking at the equipment building and he closed his notebook and thought about how the thing that was most likely to undo him was also the thing that was most useful about him. The knowing. The way it showed through regardless of how carefully he controlled it, because it was not just information, it was a different relationship with time, and people who were perceptive enough could see the shadow of it even when they couldn't name the source.

Seraphine Kael was perceptive enough.

He was going to have to decide, and soon, how much of the truth to give her.

Not yet. But soon.

Seventy-two days.