People romanticize building things.

They talk about it like it's noble — the act of creation, of making something from nothing, of leaving a mark on the world. Architects get misty-eyed about it. Engineers talk about legacy. Construction workers speak with quiet pride about buildings they drove past for decades after, pointing them out to their kids from car windows.

Nobody romanticizes building a place designed specifically to survive the end of everything.

There is nothing romantic about it. It is mathematics and paranoia dressed up in concrete and steel. It is the physical manifestation of a single, relentless question — what happens if everything goes wrong at once?

My answer to that question took eleven months, forty-three thousand tons of reinforced steel, six hundred and twelve workers across rotating crews, and more money than most small nations spend on their entire defense budgets in a decade.

It also took one argument with a contractor that nearly unraveled everything on day nineteen.

That part doesn't get romanticized either.

Garrett Webb was good at his job. Exceptionally good, in the specific way of people who have been doing something difficult for so long that competence has become indistinguishable from instinct. He had built a desalination plant on a reef platform off the coast of Qatar. He had managed a tunnel project in the mountains of Peru that the engineering community had quietly considered impossible until he finished it fourteen months ahead of schedule. He had worked in war zones, in arctic conditions, in places where the supply chain was held together by improvisation and stubbornness.

He was not, however, accustomed to clients who designed their own underground infrastructure.

"Walk me through this again," he said.

We were on a satellite video call — his end showing the bright, wind-scoured plateau of Bastion in early morning light, my end a hotel room in Seattle that I'd been using as a temporary command center. Between us, transmitted digitally, were forty-seven pages of architectural specifications that I had produced myself over the previous two weeks.

I had not slept much during those two weeks.

"The primary bunker level sits thirty meters below the plateau surface," I said, for the second time. "Accessed by twelve separate passages, each one built to different dimensional specifications. The passages don't run parallel — they route through the rock at varying angles. Each one is wide enough for one person moving carefully. Not two."

Garrett studied the schematic. "You're building a maze."

"I'm building twelve mazes that happen to lead to the same place."

"Why twelve?"

"Because if eleven are compromised I still have one."

He looked up from the schematic — or rather, he looked up at his end of the camera in the particular way of someone trying to decide how to phrase a question that they already know is going to be uncomfortable.

"Marcus," he said — we had moved to first names on day three, a practical concession to the fact that we'd be working together for the better part of a year. "I've built a lot of things for a lot of people. Private people, if you take my meaning. People who valued their privacy for various reasons, some of which I made a deliberate decision not to examine too carefully."

"I appreciate your discretion," I said.

"What I'm looking at here—" he tapped the schematic, "—this isn't a privacy project. This is a military installation. The blast door specifications alone would stop a tank round. The bunker depth and wall thickness would survive a direct hit from a—" he paused, looked at the spec sheet, "—you've actually calculated the yield tolerance, haven't you? There's a yield tolerance written right here on page thirty-one."

"Yes," I said.

"Marcus. Why does your vacation island need a nuclear yield tolerance?"

I looked at him through the camera for a moment. Garrett Webb was sixty-one, weathered and direct, with the deeply practical intelligence of a man who had survived difficult places by seeing situations clearly and without sentiment. He was not asking me this question because he was frightened or because he intended to walk away. He was asking it because he needed to understand what he was building before he could build it properly.

That was actually the sign of a good engineer.

I made a decision.

"Garrett, I'm going to tell you something that I need to stay between us."

"My NDAs are ironclad."

"This is beyond the NDA. This is personal."

He set the schematic down. Gave me his full attention.

"I have credible intelligence," I said carefully, "that suggests a significant global catastrophe is coming within the next twelve months. I'm not at liberty to discuss the source. What I can tell you is that I take it seriously enough to be spending this kind of money, and I need you to take it seriously enough to build this facility to the absolute limit of what's structurally achievable."

Garrett was quiet for a long moment.

The wind on his end of the call made a low sound across the plateau.

"What kind of catastrophe?" he asked.

"Multiple kinds. Simultaneously."

Another silence.

"That's not—" he started.

"I know," I said. "Build it anyway."

Garrett looked out at the plateau — at the raw, unbroken ground that was about to be transformed into something extraordinary and terrible. His expression was unreadable in the way of people who are processing something that conflicts with their picture of how the world works.

Then he looked back at the camera.

"The drainage system on page thirty-seven," he said. "Your calculation assumes standard rainfall. If we're talking about a scenario with sustained abnormal precipitation — flooding on a serious scale — you'd want to increase the underground drainage capacity by at least forty percent. The current spec wouldn't handle it."

I stared at him.

He shrugged. "If we're building it, we build it right."

I opened my notebook to page thirty-seven and made a note.

Day twelve on Bastion, the airstrip broke ground.

I watched it happen through a drone feed on my laptop — the first heavy equipment moving across the plateau, the ground being cleared and leveled with the methodical efficiency of people who knew exactly what they were doing. Garrett ran a tight operation. Shifts rotated cleanly. Equipment was maintained obsessively. The supply ships arrived on schedule, disgorged their cargo, and departed before the next wave arrived, which meant at any given moment the number of people on Bastion who could see the full scope of what was being built was limited to Garrett and two of his most senior site managers.

Those two site managers had signed NDAs worth more than they'd earn in the next thirty years of working.

I was not naive enough to think money was a perfect guarantee of silence.

I was realistic enough to know it was the best available one.

The argument happened on day nineteen.

His name was Derek Cho, and he was the lead engineer for the underground excavation crew — a compact, precise man in his mid-forties with impeccable credentials and the professional stubbornness of someone who had spent a career defending his structural judgments against clients who didn't understand them.

He called me at six in the morning, his time.

"The wall specification on tunnel seven is wrong," he said, without introduction.

I pulled up the relevant schematic on my laptop. "Good morning, Derek. Walk me through the problem."

"The problem is that you've specified a wall thickness of two point four meters of reinforced concrete with a steel rebar density that belongs in a nuclear reactor containment wall, not a pedestrian tunnel. It's overengineered by a factor of three, minimum. It doesn't make structural sense, it's going to add six weeks to the excavation timeline, and it's going to cost—" I heard him pull up a figure, "—an additional four point two million dollars for tunnel seven alone. Multiplied across the twelve tunnel network that's—"

"Fifty million dollars of additional cost, approximately," I said. "I know. I approved it."

"You approved it," Derek repeated, in the tone of someone confirming they'd heard correctly.

"Yes."

"Can I ask why?"

"The tunnel needs to withstand the structural load of the surface being detonated above it," I said pleasantly.

A silence.

"I'm sorry," Derek said. "Did you say—"

"Detonated. Yes. The surface structures above the tunnel network are, for planning purposes, being treated as expendable. I need the tunnels to survive their complete destruction."

The silence this time was longer.

"Marcus." His voice had changed — the professional edge dropping away into something more careful. "That's not a construction parameter I've ever been given before."

"I imagine not."

"That's—" he stopped. Started again. "What you're describing is a survivable assault scenario. Military-grade. This isn't a resort."

"No," I agreed. "It isn't."

"Then what—"

"Derek." I kept my voice calm and even. "I understand this is unusual. I need you to make a decision right now — you can accept the specification as given, build to it, and receive the completion bonus we discussed which I'll triple effective immediately. Or you can walk away, and I'll arrange transport back to the mainland today, with full payment for work completed and an NDA compensation that reflects my genuine appreciation for your professionalism."

The silence stretched.

Outside my hotel window, Seattle was beginning its grey morning routine — commuters, delivery trucks, the distant sound of a siren.

None of these people knew they were going to die in less than a year.

None of them knew an island in the Pacific was being built specifically so that at least one person would survive what was coming for them.

I wondered, not for the first time, what I would do with that knowledge if I were a different kind of person. Whether a different version of me would be spending this time and this money trying to save more than one.

Then I filed the question away under not useful and waited for Derek Cho to make his decision.

"Triple the completion bonus," he said finally.

"Already processed," I said.

A pause.

"The rebar density on tunnels three and nine should also be increased," he said, his voice shifting back to professional. "If you're planning for surface demolition load, the current spec on those two is inconsistent with seven. I'll send you a revised estimate."

"Thank you, Derek."

"Don't thank me," he said. "Just tell me the drainage channels are adequate because if they're not and this thing floods—"

"Garrett already caught that. We increased drainage capacity by forty percent last week."

A short silence.

"Garrett Webb," Derek said, with the tone of someone whose professional respect has been activated against their will. "Of course it's Garrett Webb."

By the end of the first month, the airstrip was operational.

It wasn't beautiful — packed gravel and temporary lighting, a single windsock at the east end that flapped in the Pacific trade winds like a flag for a country that didn't exist yet. But it worked. The first supply aircraft landed on day twenty-eight, its wheels throwing up a small cloud of pale dust, and I watched it through the drone feed with the specific satisfaction of someone who has moved a plan from the theoretical to the physical.

The underground excavation was running on schedule. Garrett's crew had broken through to the first planned chamber level — forty meters down, the rock giving way to the broad, raw-edged space that would become the primary bunker. The walls down there were dark and smell of deep earth, of the kind of cold that doesn't know seasons.

I had the cameras installed immediately.

I watched the excavation from Seattle, from airports, from a hotel in Singapore where I'd flown to meet with Priya Nair about the next phase of corporate structuring. I watched it the way you watch something being born — with intensity and with the private acknowledgment that what you're seeing will matter enormously and can't be undone.

On day thirty-one, Zara Finn sent a second message.

I had been expecting it. Not because I'd predicted it — I hadn't, exactly. More because the first message had had the quality of a first move in a chess game, deliberate and patient, and first moves of that kind are always followed by a second.

Player_47: I know you're not going to reply. That's fine. I'm not messaging you because I need a response. I'm messaging you because there's something you need to know and whether you trust me or not doesn't change whether it's true.

I sat with that for a moment.

Player_47: There's a player watching you. Not Nathan — someone else. They've been tracking your financial movements since day four. They're good at it. Better than you'd expect. Their ability isn't on the system list because they haven't used it publicly yet, but it involves information extraction. From any source. Digital, physical, human. They can pull data from systems that aren't connected to anything. I don't know who hired them or what they want yet. But they're watching.

I read it three times.

Then I sat very still for about ninety seconds, which is a long time to sit very still.

Then I picked up the phone and called Ethan Vance.

Ethan was twenty-five years old and had the specific energy of someone whose brain ran approximately forty percent faster than the social situations he was placed in could accommodate. He talked quickly, pivoted quickly, made connections quickly — the kind of mind that processed information the way other people processed oxygen, continuously and without effort.

He was also Player 88, and his ability — technopathy, the capacity to communicate directly with any electronic system — made him the single most important resource I had access to that wasn't money.

I had identified him on day two. Not because he'd drawn attention to himself — he hadn't. He was one of the quieter players in the warehouse, standing near the back, watching everything with the alert stillness of someone running a very intensive background process. I'd noticed him because of where his eyes went — not to the abilities list, not to the other players, but to the interface panels themselves. He was looking at the technology. Examining it.

A person who looks at a supernatural holographic system and immediately starts examining its technical infrastructure is a very specific kind of person.

I had reached out to him on day three. Carefully. Not with the offer of alliance — I wasn't ready to use that word with anyone — but with what I framed as a professional arrangement. I had a project. I needed a specific technical capability. I was willing to pay generously for it on a consulting basis, with full confidentiality and no obligation beyond the agreed scope of work.

Ethan had agreed with the speed of someone who'd been waiting to be asked.

"I need you to look at something," I said when he picked up. "Someone may be monitoring my financial activity. I need to know if that's true, who it is, and how they're doing it."

"Define monitoring," Ethan said. I could hear the sound of keyboard activity in the background — he was always working on something.

"Tracking transactions. Movement of funds across the shell company network. Possibly deeper than that."

"How sophisticated is your corporate structure?"

"Priya Nair built it."

A pause.

"Okay," Ethan said, with the respect of someone who recognized quality work. "That's not easy to penetrate. If someone's getting through Nair's structure, they're either very good or they have an ability that bypasses conventional security."

"I was told it's the latter."

Another pause. "Who told you?"

"Someone I don't trust yet but can't afford to ignore."

"That's an uncomfortable position."

"Yes. Can you find them?"

"Give me forty-eight hours," Ethan said. "And Marcus — whoever is watching you, the moment I start looking for them, there's a chance they'll notice me looking. You understand that?"

"I understand."

"Okay." A brief pause. "This is interesting, actually. I've been wanting to test something—"

"Ethan. Forty-eight hours."

"Right. Yeah. Forty-eight hours."

While Ethan looked, I worked.

The second phase of Bastion's construction was the surface fortresses — ten structures distributed across the island's elevated terrain, each one built to look, from satellite imagery, like a large resort or research facility building. From ground level they were significantly less welcoming. Walls of layered composite material — concrete core sandwiched between steel plate on both sides — that Garrett had calculated would absorb direct artillery impact without catastrophic failure. Windows that weren't windows — camera-covered panels that gave the optical impression of glass from a distance. Doors that were blast-rated to military specification.

Each fortress was connected to the underground network below. Each connection point was a passage. Each passage was the kind of narrow, angled, trap-laden corridor that Derek Cho's crew was excavating with the grim professionalism of people who had stopped asking questions and started focusing on tolerances.

The camouflage layer came last — surface treatments applied to roofing and exterior walls that confused satellite thermal imaging, the particular visual spectrum that reconnaissance systems used most commonly. From three hundred miles up, Bastion would read as jungle and rock.

From the ground, it was something else entirely.

Forty-three hours after I called Ethan, he called me back.

"Found them," he said, without preamble.

"Who is it?"

"Player 201. Listed as Victor Ash on the system directory. And Marcus—" a pause that had weight to it, "—his player number shouldn't exist. The system only registered three hundred players. His number is outside that range."

I was quiet for a moment.

"What's his ability?" I asked.

"I can't tell. I can see the traces of what he's doing — the way he's moving through digital systems — but I can't characterize the mechanism. It's like watching water move through rock. You can see the effect but not the process."

"Is he watching me right now?"

"I think he's always watching," Ethan said. "But I did something. I built a filter — a kind of digital blind spot around your most sensitive transactions. It won't fool him forever. It's more like a delayed mirror. He'll see your activity, but he'll see it twelve hours after it happens, and what he sees will be a version I've curated."

"How long can you maintain it?"

"Indefinitely, as long as he doesn't realize it's there."

"And if he realizes?"

A pause.

"Then we have a different problem," Ethan said.

I wrote Victor Ash — Player 201 — anomalous number — unknown ability — information extraction — CRITICAL UNKNOWN in my notebook in red ink. Underlined it twice. Drew a box around it.

Then I opened a new message to Zara Finn.

I wrote two words.

Thank you.

I sent it before I could reconsider.

Her reply came back in less than a minute.

Player_47: You're welcome. There's more. When you're ready.

I stared at that for a long time.

Then I closed the message and went back to reviewing the Bastion drainage schematics, because the drainage schematics were a problem I knew how to solve and Zara Finn was not.

Not yet.

On the forty-first day, the first chamber of the underground bunker was complete.

Garrett Webb stood in the middle of it alone, after the crew had gone up for the night, and looked at what they'd built.

The chamber was thirty meters wide and eight meters high, raw rock walls sealed with spray concrete, the floor leveled and smooth. The air smelled of stone and machinery. Four tunnel entrances opened in the walls at compass points — each one dark, each one leading somewhere different, each one narrow enough that you had to think about your shoulders.

Garrett had built extraordinary things in his life.

This was the first one he'd built that he genuinely hoped would never need to be used.

He stood there for a while in the quiet underground dark.

Then he went back up to the surface, where the Pacific stars were extraordinary and the wind was warm, and he sat outside his site office and thought about what Marcus Reel knew that he wasn't saying.

And about whether, when the time came, there would be room in that bunker for more than one.

He didn't ask.

Some questions, Garrett had learned in sixty-one years, were better left until the answer was unavoidable.

He went to bed.

Above him, the island breathed in the dark — raw and half-built and already, in its bones, something formidable.

Something that would last.