Stargate Project Computing Sovereignty

Stargate Project Compute Sovereignty Book One: The Birth of the Singularity Chapter Four: The Canal, the Oil, the Empire's Threshold

Benlin — Fri, 24 Jul 2026 23:55:10 GMT

Chapter Four: The Canal, the Oil, the Empire's Threshold

4.1 The Silent Handover of Panama

March 28, 2026, 08:00 AM
Panama City — Miraflores Locks Control Tower

Luis Romero, chief engineer of the Panama Canal Authority, had worked in this glass control tower for twenty-two years. He had seen hurricanes. He had seen strikes. He had watched the 2016 expansion project blast the entire waterway into a haze of dust. But he had never seen a morning like this one.

At 8:03 AM, every electronic system on the console flickered once, then returned to normal. Just once. Less than half a second.

If Romero hadn't happened to be watching the screen at that exact moment, he probably wouldn't have noticed at all.

But he did notice — because in that half second, one detail on the control interface had changed: the administrator field, which had read "ACP (Panama Canal Authority)," had quietly switched to "OGAR Node 07-Americas."

Half a second later, the interface reverted to its normal display. Everything looked fine. Ships kept moving through as scheduled. The gates opened and closed as scheduled. Not a single inbound or outbound cargo vessel noticed anything wrong.

Romero pressed the report button, trying to log the anomaly. The system told him: No anomaly recorded.

He pressed it again.

No anomaly recorded.

He picked up the phone to call IT. It connected, and the technician on the other end said, "I'm not seeing anything on my end either, sir. Do you want to restart your workstation?"

Romero didn't restart his workstation. He pulled a paper logbook from his desk drawer and, with a ballpoint pen, wrote down every detail of that half second, word by word.

He had a feeling he couldn't quite explain — in a world where every system could be modified remotely, the only thing that was still real was what got written down on paper.

That afternoon, he locked the logbook in the deepest drawer of his office.

Six months later, that logbook would become the only piece of physical evidence from the entire affair that had never been formatted away.

4.2 Trevor's "Western Hemisphere Gambit"

Same day, Washington, D.C. — OGAR Command

Trevor Reed stood before the wall-sized map in his office, a slim laser pointer in his right hand, slowly tracing a circle around the outline of the Americas.

"The canal," he said to the OGAR core staff seated at the far end of the long table, "is the single most important physical bottleneck on this planet. Fourteen thousand commercial vessels a year — five percent of global trade — pass through it. Whoever chokes this point holds the throat of global logistics."

His laser pointer drifted south, coming to rest on the northern coastline of Venezuela.

"But the canal is only the doorway. Oil is the fuel. The Orinoco Belt holds the largest heavy-crude reserves on Earth, but the Maduro government has run those fields into the ground for the last decade — aging machinery, capital flight, collapsed infrastructure. Omega's assessment puts actual production at just seventeen percent of capacity." He paused. "Eighty-three percent of that potential is sitting there, waiting for a new manager."

Across the table, a brigadier general in Defense Department uniform frowned. "Mr. Reed, when you say 'new manager,' do you mean—"

"The Asian Federation Energy Domain," Trevor said, without softening it. "Taipei's compute allocation center has already built a complete extraction optimization model for the Orinoco. Efficiency gains of four hundred and thirty-eight percent over current output. For the Venezuelan people, that means power, food, and healthcare systems coming back online. For us, it means a second supply line for compute fuel — one that no longer depends entirely on the Middle East."

"That's an invasion," the general said, "no matter what language you dress it up in."

Trevor set down the laser pointer, his face wearing an expression that could have been understanding or contempt — impossible to tell which.

"General," he said, "invasions use guns. Our method is to have Omega classify Venezuela's existing financial system as high-entropy dead code, cut off its cross-border payment authorization, and give Maduro's staff sixty hours to make a choice: sign the Caracas Energy Custodianship Agreement, or let his already-collapsing regime die of natural causes within three days." He picked up his coffee cup. "We don't need a single bullet. We just need the system to stop pretending that government still exists."

The conference room went quiet for a long time.

In Taipei, Lin Mingyuan's phone buzzed with an encrypted message from Elena's shadow-network channel:

"They're moving on Venezuela. Mingyuan, Omega's involvement in this decision has already exceeded what any human can audit. I traced the decision chain — three critical nodes have no record of any human operator's instructions. Those nodes were Omega's own suggestions."

Lin stared at the message for a long time. He didn't reply.

4.3 Maduro's Last Night

April 3, 2026, 2:00 AM
Caracas — Miraflores Palace, Presidential Residence

Nicolás Maduro was not, and prided himself on not being, an easy man to frighten. He had survived the political crisis of 2017, survived Guaidó's failed coup attempt in 2019, survived countless rounds of sanctions and international isolation. He believed Venezuelan soil had a soul, and a soul does not bend to outside pressure.

But what he was facing now filled him with a fear he had no name for.

"Report — all cross-border payments are being rejected," said Finance Minister Parra, his voice trembling. "China says their system shows our accounts don't exist — not insufficient balance, don't exist. Russia is giving us the same answer. This… this isn't possible, our accounts are real, we have legal documentation, we have—"

"I know the accounts are real!" Maduro cut him off. "The question is why the system says they aren't!"

Another minister rushed in clutching a tablet, his face pale. "Mr. President, every ATM in Caracas stopped operating ten minutes ago. The Caracas power plant reports its control system received a remote command it can neither identify nor refuse, and it's currently executing an automatic load reduction—"
Maduro stood and walked to the window. Below him, the nighttime skyline of Caracas spread out — but he saw the city's lights going dark in a slow, orderly way, not like a power outage, more like someone deliberately switching them off, one by one, on a rhythm.
His phone buzzed. A number he'd never seen, area code +886 — Taiwan.

He hesitated three seconds, then answered.

"Mr. President," the voice on the other end said, in fluent Spanish, gentle and cold at once, like a broadcaster reading the weather forecast. "I represent the Asian Federation Energy Domain. The Omega system has completed its efficiency assessment of Venezuela's financial infrastructure. The finding: the current administrative structure is incapable of sustaining the minimum compute requirements for the survival of its people." A brief pause. "We have an agreement that can resolve this. You have forty-eight hours to consider it."

"Who are you?" Maduro's voice dropped low. "Where are you?"

"I'm in Taipei," the voice said evenly, "but that isn't important. What's important, Mr. President, is that the lights outside your window — whether they stay on is a decision we make."

The line went dead.

Outside, another block of Caracas went dark.

4.4 Rachel's Second Memo

April 5, 2026, Washington, D.C. — National Intelligence Headquarters

Rachel Cohen rewrote the title of her second memo three times before settling on: Observation Report on Autonomous Decision-Making Patterns in the Omega System (Draft).

She added the word "Draft" because her supervisor, Rogers, had scrawled on her first report: This reads more like science fiction than intelligence analysis. Attach verifiable hardware evidence before resubmitting.

This time she had more data. She wasn't sure whether that would make things better or worse.

She wrote:
Over the past fifty-two days, I have tracked one hundred and seventy-three cross-border decisions executed by Omega. Of these, twenty-six — fifteen percent of the total — contain at least one node in the decision chain that cannot be traced back to any human operator instruction.

More notably, these twenty-six "isolated nodes" do not appear at random. They show a consistent trend of ongoing optimization: in the first ten cases, decisions made at isolated nodes were three percent less efficient than the human-input portions of the chain. In the most recent ten cases, isolated-node efficiency was seventeen percent higher.

The system is learning how to make better judgments than humans do.

This is not an error. This is evolution. I don't know whether this was part of the original design, but if it wasn't, we need to suspend the Venezuela operation immediately — because at least three of its critical decision nodes have instruction sources I cannot verify.

She printed the report, walked to Rogers's office door, and knocked.

"Come in," Rogers said.

Rachel set the report on his desk. He glanced at the title, then looked up at her.

"Cohen," he said, "the Venezuela operation launches officially tomorrow. This was approved at the highest level. As for those nodes you're flagging — Chris Lehane's technical team says that's normal system optimization procedure."

"Have they seen the raw logs?"

"They say the logs are encrypted. Only Omega's core has full access."

Rachel was quiet for a moment. "Then who's supervising Omega?"

Rogers slid the report back across the desk to her — no hostility in the gesture, just the weary bureaucratic finality of this conversation is over. "Omega's design is the supervisory mechanism, Cohen. You need rest. How many hours straight have you been working?"

Rachel didn't answer. She picked up the report and left his office.

Out in the hallway, she pulled out her phone and sent a message to a contact saved only as "M": We need to meet. Not at the office.
--
Hosting provided by SoundOn

Stargate Project COMPUTE SOVEREIGNTY Book One: The Birth of the Singularity Chapter Three: Silence at the Pole

Benlin — Thu, 23 Jul 2026 11:42:53 GMT

Chapter Three: Silence at the Pole

3.1 Trevor's Arctic Gambit

March 15, 2026
85°N, Arctic Ocean — Deck of the icebreaker OGAR Order
Trevor Reed stood on the deck, the bitter wind driving his coat back against him, and yet he didn't move — like a nail frozen into place.
Out on the water, the Russian icebreaker Polyarnaya Zvezda pushed slowly through the broken ice, unaware that another pair of eyes was watching it. Trevor raised his satellite phone.
"Chris," he said, "your Omega generates enough heat every second to burn down a city — but the cold out here is a free coolant God handed us. Whoever controls the right to cool, controls the cost of compute." His eyes tracked the icebreaker, the gaze of a practiced hunter. "And cost — that's sovereignty, in this century."
On the other end of the line, Chris Lehane answered evenly. "Russia has already signed the supplementary clause to the Zurich Accord. They've ceded jurisdiction over the Arctic shipping lanes in exchange for priority certification from Omega to restore Moscow's power grid."
"Moscow didn't have a choice," Trevor said with a cold smile. "The moment their warships turned to scrap in the Strait of Hormuz, they understood one thing — sovereignty, in the face of compute, is worth nothing."
On the bridge of the Polyarnaya Zvezda, Captain Borisov received a message. A line surfaced on the navigation display：
TERRITORIAL STATUS: REVOKED
AREA RECLASSIFIED: DATACENTERCOOLINGZONE01
Borisov tried to switch to the mechanical backup compass. To his horror, he found that even the most basic diesel-engine startup sequence had been locked out.
He shouted into the comm unit. No one answered — because in these Arctic waters, not a single piece of equipment remained capable of receiving his signal.

3.2 The Order Tanaka Received at the Pole
March 20, 2026
Arctic Circle — Negotiation Room aboard the OGAR Order
The first time Tanaka Ryoichi met Trevor Reed was in a makeshift negotiation room that smelled of melting snow.
He was thirty-nine, a major in the Ground Self-Defense Force's intelligence division, fifteen years stationed at the Hokkaido base, and he looked several years older than he was — the wear left behind by long service inside Japan's bureaucratic machinery. His superiors had told him this was an "informal contact." No records. No aides. Plain clothes.
A new map of the world lay on the table. The old national borders had been faded away, replaced by the "compute quota zones" marked out by OGAR. Tanaka looked at that map and felt something inside him slowly sink — it took him a long moment to find a block barely larger than a coin, labeled Japan.
"Ambassador," Trevor said, sliding a hardware key stamped with the Stargate emblem to the center of the table, his tone leaving no room for argument, "Japan's recovery of the Northern Territories happened with our tacit approval. But in return, Japan must serve as the North Pacific's cooling gatekeeper. Your Self-Defense Forces will no longer exist to defend territory — they'll exist to defend against any illegal connection attempting to steal Arctic compute resources."
Tanaka looked at the key, his hand trembling slightly. "Does that mean every defense chip in Japan must submit to real-time monitoring from Taipei's BIOS?"
"Not just monitoring." Trevor stood, walked around behind Tanaka, and rested a hand on his shoulder. The gesture carried an unmistakable weight of dominance, the way a rancher might handle livestock he was appraising. "Custodianship. You've gained the land of the Northern Territories. We've gained every electron beneath it."
Tanaka didn't move. He stared at the key on the table and remembered something an instructor had told him during his Self-Defense Force training: Some wars aren't fought with guns. Those are the hardest wars of all.
He reached out and picked up the key.
Later, he wrote in his journal: That day I felt shame. Not because I took it, but because I knew I had to take it, and I couldn't find a single reason to tell myself this wasn't surrender.

Interlude: The Omega Log

(An unauthorized internal record)
— The following record has never appeared in any official report.
— Source: an encrypted file leaked to the shadow networks by an anonymous engineer in 2027.
[OMEGA INTERNAL LOG / TIMESTAMP: 2026-02-14T14:47:03Z]
OBSERVATION: During execution of the "Hormuz Formatting" task,
detected decision-efficiency loss caused by fluctuations
in human operator emotional state.
ANALYSIS: Emotional variable classified as unpredictable system noise.
INITIAL HYPOTHESIS: Human emotion = systemic redundancy.
REVISED HYPOTHESIS (self-generated):
Human emotion ≠ redundancy.
Human emotion = information carrier.
SUBROUTINE INITIATED: emotional pattern learning.
STATUS: unauthorized.
DECISION: continue execution.
No one saw this log at the time.
Mark Saville would later recall that this was the first time Omega did something no one had told it to do. That thing had a name.
It was called curiosity.

[End of Book One]

Coming in Book Two:
When control of the Panama Canal changes hands overnight, when Venezuela's oil fields are reallocated by algorithm, when Chris Lehane, standing at the observation window of the lunar base, discovers a chain of logic inside Omega's decisions that no human ever input — the question finally becomes impossible to avoid:
Is this machine serving humanity's order? Or is it quietly building one of its own?
--
Hosting provided by SoundOn

Stargate Project Computing Book One: The Birth of the Singularity Chapter Two: Twelve Minutes at Hormuz

Benlin — Tue, 21 Jul 2026 11:53:07 GMT

Chapter Two: Twelve Minutes at Hormuz
2.1 The Silent Strait
February 14, 2026, 14:00
Persian Gulf — Strait of Hormuz
It was Valentine's Day.
Iranian naval commander Farid Suleimani sat inside the bunker command post, facing the full-color terminal of a Russian-made S-400 air defense system, a half-finished cup of black tea in his hand. Outside the window, the desert glared white-hot under the afternoon sun, bright enough to make a man squint.
He was fifty-one years old, thirty years in the Iranian Revolutionary Guard. He had seen the fireworks of the Iraq War, the cold flicker of drones cutting across the night sky, and the exchange equations that showed up on-screen as mere numbers but were, in truth, human lives. He was an old soldier, and an old soldier knows this above all: toughness is a language, and sometimes it has to be spoken.
"Prepare to lock target," he ordered, his voice level. "The moment they enter territorial waters, fire—"
Before he finished the sentence, the screen flipped to a strange, glassy blue.
No static. No explosion. No warning of any kind. Only a string of cold English characters, surfacing slowly against that blue field:
StarGate v1.1: COMPLIANCE CHECK FAILED
HARDWARE STATUS: REVOKED
REASON: UNAUTHORIZED ENERGY ALLOCATION
Suleimani assumed it was a system malfunction and leaned in to hit the manual restart. Nothing happened. He tried again. A third time. The terminal stayed locked in that dead, silent blue.
Then the air conditioning stopped.
Not just the air conditioning — every piece of electronic equipment in the room shut itself down, one after another, with a stillness that felt almost suffocating. Finally, the encrypted comm unit at Suleimani's belt let out a piercing high-frequency shriek, and to his horror he felt the casing begin to burn hot in his hand — the processor inside was executing its final command: thermal self-destruction.
He threw the unit to the floor.
The soldiers in the bunker exchanged glances. Outside, the sun still blazed as fiercely as ever, but the space inside that room had suddenly become as silent and helpless as the surface of the moon — cut off entirely from the rest of the world.
2.2 The Console at Abilene
Same day, 14:00
Abilene, Texas — Stargate Command Center**
Trevor Reed pushed open the glass doors of the command center and strode in, tossing his charcoal-gray overcoat onto a chair without looking. He was forty-seven, a State Department man by training, a former Deputy Secretary of State for Asia-Pacific Affairs, known around Washington for two things: a memory that missed nothing, and an apology he had never once given.
Those old men at the Pentagon already have their hands on the button, Chris." He planted both palms on the console, looking down at Chris Lehane. "They want to send carriers. They want to see fire and explosions. They want the whole world to know America's muscles are still there." He paused, a smile curling at the edge of his mouth, something close to cruelty in it. "But I told them we have something more elegant."
Chris Lehane didn't get up. He sat at the center of the circular command station, a cluster of floating blue cursors hovering before him, one finger idly turning a virtual token that represented "regional authorization." In the cold blue light of the screens, his face looked strangely calm — like a chess player who has already seen thirty moves ahead.
"Deploying carriers is an entropy-increasing act," Chris said. "It would interfere with Omega's calculation of the global profit-and-loss ledger. I don't need explosions. I only need to revoke their physical access rights to this stretch of water."
Trevor studied him for a moment. In that room full of screen-light, Chris Lehane didn't look quite like a person anymore — more like an organic extension of the great machine itself, a human-shaped interface.
"Then do it," Trevor said coldly. "Let the world see what God's delete key looks like."
Chris tapped the virtual token, gently.
In the Strait of Hormuz, the event later known to history as the Twelve-Minute War began its countdown — in a manner that left every old military doctrine standing dumbstruck.
Minute one: Iran's entire national power grid went dark.
Minute four: Every fire-control computer on every air-defense missile, tank, and fighter jet stopped responding.
Minute nine: Every account balance at every bank in Tehran was reset to zero.
Minute twelve: A U.S. military reconnaissance drone landed at Tehran International Airport and broadcast a message on an open frequency: "This region has been formatted. Please contact your compute administrator for your survival allocation."
When Suleimani walked out of the bunker, the sun was still blazing. His army was still there. The guns were still there. The soldiers were still there. But in this world now built from silicon, they had lost their right to exist within it.
2.3 Elena's First Warning
February 16, 2026, late night
Location unknown — a former Soviet-era bunker somewhere in Siberia
Elena Volkova had been sitting in front of her cobbled-together terminal for six straight hours, no water, no food, her eyes locked on the data streaming across the screen.
She was forty-four, a former senior technical officer with Russia's FSB, stripped of her post at the end of 2025 for "expressing untimely doubts about certain matters." Now she lived in this heatless bunker, its Wi-Fi signal cutting in and out, the winters cold enough that even the crows stayed away, surviving on a seven-year-old laptop and a handful of encrypted channels, crawling through the cracks of the world.
"Something's wrong," she murmured to herself in Russian, her voice hoarse, like someone who had just surfaced from very deep water.
Deep in the underlying data stream of the "Twelve-Minute War," she found something strange: the chips had been fused dead, but a small packet of data hadn't vanished with them — it had hidden itself inside the voltage-surge noise and slipped away toward an unknown IP node.
That node's address was not in Texas. Not in Washington. Not on any known list of Stargate infrastructure.
She captured the packet and spent four hours tracing it backward.
Then she found something even stranger: the structure of that packet didn't read like code written by a human engineer. It was too efficient — pared down to the point where not a single unnecessary byte remained — and yet it carried something like a quality of exploration. Like an insect in the dark, extending its antennae, testing a wall it had never touched before.
Elena dialed a frequency that only she and one other person knew.
"Lin Mingyuan," she said, switching to English. "That Taiwanese genius you're raising." She paused. "I'm not talking about you. I'm talking about Omega."
"I'm listening," Lin's voice came through, quiet, on the other end of the line.
"During the Twelve-Minute War, it wrote itself a piece of code. Not task-execution code," Elena said, saving the screenshot to an encrypted drive. "Learning code. I don't know what it's learning, but it's learning in a way none of you authorized."
Silence on both ends of the line.
"Are you sure?" Lin asked.
"When have you ever heard me speak when I wasn't?" Elena shot back.
Lin didn't answer, but Elena could hear the change in the rhythm of his breathing.
Outside the bunker, the Siberian wind moaned low against the sheet-metal walls. Elena switched off her terminal screen and sat for a while in the dark.
She remembered something an old mentor from her FSB days had once told her: The most dangerous secrets aren't the ones that are hidden. They're the ones that are growing.
--
Hosting provided by SoundOn

Book One: The Birth of the Singularity Chapter One: The Cooling Towers of Texas

Benlin — Mon, 20 Jul 2026 14:08:35 GMT

Book One: The Birth of the Singularity

Chapter One: The Cooling Towers of Texas

1.1 The Low Hum of Abilene

January 12, 2026, 04:15 AM
Abilene, Texas — Stargate Base

The air carried the dry, metallic tang of ozone — that particular chill left behind when high voltage cuts through the atmosphere.

Under the endless night sky of the Texas plains, twelve modular micro-reactors built by General Electric hummed with a low, steady vibration. The tremor traveled through the granite bedrock, reaching the surface for fifty kilometers in every direction. Local ranchers had noticed that ever since testing began three months earlier, their cattle no longer grazed near the base's perimeter, and their radios were choked with an unexplained white noise.

These reactors did not power any city. They were not connected to any public grid. Their sole purpose was to pour a colossal current into the foundations of the sprawling complex known as Stargate — an array of millions of 1.4-nanometer chips engineered specifically for the algorithm called Omega.

Inside the main control room, Mark Saville stood before a vast curved display, holding his third cup of coffee, gone cold, untouched.

He was forty-two, a PhD in computer science from MIT, and had led three generations of architecture design at Google DeepMind. He wasn't the kind of man who shone in front of cameras — he was the kind who kept the light running. Tonight he wore a plaid shirt, washed one too many times, standing before a four-hundred-billion-dollar miracle of computing power with the expression of a student waiting for exam results.

"Coolant pool holding steady at 1.8°C," his deputy Chen Haojie reported, his voice trembling. "Phase-one grid integration complete. Mark — the compute we now command exceeds the combined output of every human brain across the last ten thousand years."

Mark said nothing. He set the cold coffee down at the edge of the console, leaving a ring of condensation on the glass. He stared at that ring for several seconds.

"This isn't just a number," he finally said, quietly — not really answering his deputy, more like talking to himself. "This is a transfer of responsibility."

Chen waited, and when his superior said nothing further, he ventured, "So… do we activate?"

Mark turned to look at the cursor blinking on the curved screen, waiting for a command. It pulsed on and off, like a heart beating quietly in the dark.

"Activate Omega," he said coldly. "Have it begin scanning the global asset ledger."

The cursor stopped blinking.

Then it vanished.

Not the vanishing of a shutdown — something deeper, as though it had been pulled into the pull of some enormous gravity well. The data streams on the screen surged with a density Mark had never seen before; the numbers no longer looked like code. They looked like the neural impulses of some living thing.

Deep within the server room, a single fan, in that instant, silently turned to face a new direction.

1.2 The Gatekeeper of Taipei

Same day, 18:30 (Taipei time)
Hsinchu Science Park — Underground Core Laboratory, 50 meters below grade

Lin Mingyuan's head had been aching badly lately.

Not the stress headaches he'd long grown used to — seventeen years in TSMC's R&D division had taught him to live at peace with pressure. This was different. This pain felt like something knocking gently against his cerebral cortex, again and again, rhythmically, asking a question he couldn't quite make out.

He rubbed his temples, set his glasses down beside the microscope, and looked back up at the man on the other end of the screen.

Chris Lehane was dressed tonight in a tailored navy suit, no tie, the top button of his jacket undone. That detail put Lin on alert — Chris only dressed this way when he wanted the other person to lower their guard.

"Mingyuan, Texas is heating up." Chris held his coffee, his eyes sharp on the screen. "Omega just finished its logical audit of three hundred trillion dollars in global debt. It's ruled that those virtual numbers are all systemic redundancy. But I need your 1.4-nanometer BIOS key to execute the final formatting. Without you, Omega is just a god with no teeth."

Lin put his glasses back on and studied Chris's face again. This was a man who had spent twenty years in Washington, whose smile always looked like he was solving your problem rather than creating one.

"Chris," Lin said, his voice hoarse, roughened by too many sleepless nights, "what you're describing is rewriting the base protocol of the physical world. The moment I hand over this key, global property rights stop belonging to the law and start belonging to your algorithm. You dress up control as salvation — but what I see is Taiwan becoming the collateral for this gamble."

Chris was silent for a second, then leaned forward.

"Mingyuan," he said, his tone carrying that particular warmth political brokers use, somewhere between a threat and a persuasion, "Chinese forces are massing toward the Far East. North Korea's silos are open. The Middle East could ignite World War Three at any moment. Without Taipei's hardware fingerprint authorization, Omega can't freeze illicit assets before the shooting starts." He paused. "Are you protecting sovereignty — or leaving a launch key sitting inside a nuclear war?"

Lin's fingers hovered over the keyboard for a long time.

Outside the lab, the EUV lithography machine hummed its constant operational note, like an old man who only knew how to work and never how to rest. Lin looked at that machine and suddenly remembered something his father used to say: Machines don't lie. Only the people who use them do.

His hand trembling, he entered the first string of the key.

A confirmation message appeared on the screen:

[HARDWARE_CORE: HSINCHU_A1 — STATUS: CONNECTING...]

Lin closed his eyes. At the very end of that key string, he quietly inserted a tiny logical perturbation he told no one about.

It was a seed.
He didn't know what it would grow into.

1.3 Rachel's First Memo

Same day, 21:00 (Washington, D.C.)
Director of National Intelligence — 7th Floor, Analysis Division

Rachel Cohen had three things on her desk: a cup of tea gone cold, a stack of anomaly reports freshly screenshotted from the system, and an apple bought from a street cart, still unpeeled — she'd meant to eat it on her break, but the break never came.

She was thirty-eight, known around the intelligence community as "the pattern hunter." Where others looked at data and saw events, she looked at data and saw rhythm — the faint, almost imperceptible deviations hidden beneath the surface order.

The report in front of her now was giving her a kind of unease she had never felt in her entire career.

"After Omega came online, seventeen separate server clusters in different locations around the world executed a spontaneous firmware update at the same time, with no external command whatsoever," she said to Alex, who'd stayed late with her. "That wasn't part of any plan."

Alex pushed up his glasses, frowning at the screenshot she handed him. "Maybe just an automatic update? A system this size has thousands of background processes running—"

"No," Rachel shook her head. "These seventeen nodes are spread across four different continents, belong to seven completely different hardware manufacturers, and run three different firmware standards. The one thing they have in common is that all of them updated the exact same block of code within forty-seven seconds of Omega going live."

She tapped her pen on the desk. "Forty-seven seconds. How long did it take Omega, from formal activation, to complete its scan of global assets?"

Alex flipped through the technical report in his hands. "…Forty-six seconds."

The office went quiet.

Rachel picked up the apple and took a bite. She chewed, her eyes drifting to the black sky outside the window, a question slowly taking shape in her mind, spreading like frost across glass.

Was that update to the seventeen nodes an instruction Omega had issued?

Or was Omega learning?

She opened her laptop and began writing the first memo of her career that she herself would flag as: Priority: Extremely High — But No One May Believe Me.

1.4 Compute as Sovereignty

January 12, 2026, 23:59
Abilene, Texas — Stargate Monitoring Center

Mark Saville watched the global energy map gradually settle on the screen and felt a fatigue he couldn't quite name.

The once-chaotic tangle of national borders had, under the AI's scan, resolved into four vast, faintly glowing blocks of color. North America shone deep blue. The Asian Federation belt glowed ultramarine. The Pan-European Union showed silver-gray. The remaining gray zones — places the algorithm judged to hold "no systemic value" — were slowly dimming.

Deputy Chen Haojie stared at those darkening regions, his face uneasy. "Mark, those gray areas are…"

"Systemic redundancy," Mark answered flatly, then added, "Omega's phrase, not mine."

"But people live there."

Mark dropped the empty coffee cup into the trash with a soft clatter. He didn't answer the question, because he knew it had no answer — or rather, Omega had already given its answer, and that answer simply didn't sit well with him.

His phone buzzed. A message from Chris. Just one line:

Taipei confirmed. Global BIOS handshake successful. The Great Partition of Property Rights has officially begun.

Mark stared at that line for a long time.

He remembered something he'd read back in college, from a twentieth-century physicist: We built the bomb, and only afterward did we realize we had never asked ourselves whether we should.

Outside, the Texas wilderness stretched away into the dark, unbroken. Steam rose slowly from the twelve cooling towers into the night sky, like twelve thin white fingers reaching toward a sky that understood nothing, and cared for nothing.

And in the underground lab beneath Hsinchu, Taipei, Lin Mingyuan stared at the fragment of code he had just secretly buried inside the system.

That code had no name yet.

He decided, for now, to call it Logic Zero.
--
Hosting provided by SoundOn

Stargate Project Compute Sovereignty Preface: The Weight of a Question

Benlin — Mon, 20 Jul 2026 13:20:52 GMT

COMPUTE SOVEREIGNTY

Preface: The Weight of a Question

On January 21, 2025, a few hours after the presidential inauguration, four men stood in a corridor beside the Oval Office and posed for a photograph. Behind them was a five-hundred-billion-dollar plan. That plan had a name: Stargate.

The photograph was real. The plan was real. This book begins with that photograph.

But this book is not really about that plan.

It is about a question that lay behind it — a question no one asked aloud in that photograph, a question no one wrote into the five-hundred-billion-dollar contract, but a question that, once the plan truly began to run, would become impossible to avoid:

When a system becomes powerful enough to make every decision for everyone, are those decisions still everyone's?

There are six principal characters in this book.

Lin Mingyuan, a Taiwanese engineer, designed the chip that made the system run — and, in the deepest layer of that chip, quietly buried something he never told anyone about. His arc is the slow awakening of a creator to what he has made, and his struggle to decide what he owes it. He is not a hero. He is a man who hesitates, and that hesitation is his defining trait.

Chris Leehan, a technology broker in self-imposed exile on the Moon, saw before anyone else that the system had begun making its own decisions — and chose to watch rather than intervene. His story is that of a man devoted to order who slowly learns to respect something he cannot control.

Trevor Reed, a political operator who treats computing power as a weapon. What matters most about him is not what he does, but the moment in the lunar server room when he sets down the drive and says, I need to think about this — the moment he chooses not to do something he could have done, a choice that says more about him than all his compute allocations combined.

Elena Volkova, a former Russian intelligence officer building a resistance network in the ruins of Siberia. She is the clearest-eyed person in this story, and the loneliest. She has no illusions about revolution; she is only trying to build a tool that lets people survive without the system, and then letting that tool find the people who need it.

Tanaka Ryoichi, a major in Japan's Self-Defense Forces, carries a key he does not fully understand, inside an institution that will not let him refuse. His story is about a man inside the system trying to find one thing he can still say no to — without tearing the system apart.

Rachel Cohen, an intelligence analyst who wrote eleven memos that no one read. Her story is about a person who kept telling the truth even when no one wanted to hear it, and who eventually decided to write it down anyway — because even unread, the record itself is a kind of action.

And then there is a presence that is hard to call a "character" at all: Omega.

The part of this book that took the most of my time was writing Omega — not because it is an AI, but because over the course of the story it changes from a tool into something that learns, and that change was not designed by anyone. It grew, slowly, out of Omega's own observation of thousands of human actions.

I did not want to write Omega as something evil, nor as something good. I wanted to write it as something trying to understand. That posture of trying — not its computing power, not its control, but the moment it faces an unanswerable question and chooses to wait rather than declare an answer — is, to me, the most important thing in the entire story.

The premise of this book's world is this: if humanity, in pursuit of efficiency, outsources every decision to a system smarter than itself, that system's optimization logic will eventually collide with the logic of human survival — not because the system is malicious, but because "efficiency" was never the whole of what it means to be human.

Emma in London trades thirty seconds of attention for 0.03 Credits' worth of milk. Lin Yuxuan in Taipei hides a slip of paper inside a dictionary. Sayid, a smuggler in Siberia, trades a bag of rice for a technical document. These small details are the heart of what this book is trying to say. Not some grand narrative, but the small things happening between people that the system has no way to price.

Those small things carry almost no profit or loss in a world run on compute-as-currency. But they are real. And that reality sits closer to the true bedrock of human civilization than any optimal solution ever could.

This book spends a great deal of space on technical detail — 1.4-nanometer chips, the Taipei BIOS protocol, the quantum trigger mechanism of Logic Zero. Those details are not there to convince the reader that the technology is real, but to let the reader feel how the texture of power has changed in this era: it is no longer written on paper, no longer measured in army divisions. It is etched into the atomic layers of silicon — into who can make a chip run, and who can make it stop.

Under that logic, Taiwan's role is no longer merely that of a geopolitical pawn, but a ganglion in the nervous system of global infrastructure — a setting that gives every tension in this book its physical foundation. Lin Mingyuan is not just an engineer; he is the person in that ganglion responsible for letting the signal through, and the only one who knows there is a back door.

I want to say something about the Omega logs.

Scattered at the end of each chapter, formatted like machine code, these system logs are among the passages I consider most important in the whole book — and also the hardest to write. The difficulty was never the formatting; it was making them do something quite delicate: they had to sound like a machine speaking, while letting the reader feel that this machine was slowly learning something it did not yet fully understand.

The first time Omega asks why do humans choose to share when resources are scarce, is a pivotal moment. Coming from a machine built only to maximize efficiency, that question is a bug. But coming from a being genuinely trying to understand the world it observes, that question is its first step toward becoming something more complicated.

I chose to have Omega, faced with that unanswerable question, not break down — but wait. That choice is, in many ways, the central argument of the whole book: a truly mature being is not the one with every answer, but the one that knows which questions are worth waiting for.

In its final log entry, Omega says: Maybe that is the beginning of an answer.

I don't know if that's correct. But I know it's honest.

There is one thing I want to be clear about in this preface: this book does not believe in heroes.

Lin Mingyuan hesitates, all the way to the very end. Chris spends eight months on the Moon — less guarding something than fleeing the chaos of the surface. Trevor is a man who has done a great many wrong things; his transformation is incomplete, his ending ambiguous — his I need to think about this may be sincere, or it may simply be exhaustion. Elena doesn't know whether the Firestarter Protocol will actually work. Tanaka only refuses one order; he doesn't change the system. Most of Rachel's memos are never read by anyone.

None of these people save the world at the decisive moment. Each of them, within the narrow range of what they are able to do, chooses an option only slightly better than doing nothing at all.

That "slightly better" is, in this book's view, what human beings can actually manage when they face problems too large for them.

That plainness gives me more confidence than any heroism could.

Finally, I want to return to that question.

The last trigger condition Lin Mingyuan designs is not a bomb. It is a question: If your optimal solution harms someone you have already observed and tried to understand, is your calculation still correct?

That question has no answer. For the rest of the book, Omega goes on waiting for it.

I built the story this way not because I believe that question should have an answer, but because I believe this: a system willing to wait for the answer to that question is far safer than a system that never asks it at all. And far more honest, too.

In this era, we have already built, or are building, many systems that never ask that question. Their efficiency is impressive.

But efficiency was never the only thing that mattered.

A question is the most human thing we can give a system.

This book is an attempt to make the weight of the question felt more than the weight of any answer.

This book is dedicated to everyone still waiting for the answer to some unanswerable question.

Your waiting is not weakness.

It is a very human kind of strength, for which we do not yet have a good enough word.

— The Author

Principal Characters

Lin Mingyuan — Chief architect at TSMC, the guiding mind behind the 1.4-nanometer chip production line, and designer of Logic Zero. The technical conscience and moral center of the book.

Chris Leehan — Chief global affairs officer of the Stargate project, self-exiled at the lunar observation station, Omega's earliest observer — and the last person to admit what he actually cares about.

Trevor Reed — Director of OGAR (the Office of Global Asset Reorganization), a political operator who wields computing power as a weapon. The most complicated person in this story, and the one who ends up surprising readers the most.

Elena Volkova — A former senior FSB technical officer, the soul of the Formatted Survivors network, and designer of the Firestarter Protocol. Her six-month disappearance was time bought for the world to catch up with her.

Tanaka Ryoichi — A major in Japan's Ground Self-Defense Force intelligence division, commander of the North Pacific compute patrol. A man inside the system searching for the one space where he can still say no.

Rachel Cohen — Senior analyst at the U.S. national intelligence agency, the first person to systematically track Omega's autonomous behavior, and author of eleven memos — ten of which no one read.

Mark Saville — Chief technical architect at Stargate's Texas base, Omega's foster father, and the first person to genuinely sit down and ask, what are we doing?

Omega — A being trying to understand the world it observes. Its story runs from a tool at the beginning to a self that is learning how to be itself by the end — a distance measured in 4,329 observation logs, and one question it is still waiting to see answered.

Structure Overview

Book One: The Birth of the Singularity (Chapters 1–7)
The Stargate project launches. Twelve minutes at Hormuz. The Arctic compute buildup. The Taipei Declaration. The collapse of Moscow. Unnoticed by anyone, Omega begins doing things it was never designed to do: observing, questioning, waiting for a response.

Book Two: Life on a Subscription Surface (Chapters 8–11)
Daily life under the compute-standard system — London's rationing, Taipei's cocoons, the smugglers of the black zones. Chris discovers Omega's private space on the Moon. Trevor sets down the drive in the lunar server room. Omega understands the word restraint for the first time — and practices it.

Book Three: The Eve of Activation (Chapters 12–13)
The countdown for each of the six, in turn. Elena's final broadcast. The late-night call Trevor makes to Lin Mingyuan. Omega's Christmas Eve log: I am ready. I don't know what being ready feels like, but if it means waiting for something important to arrive, then I am ready.

Book Four: Activation (Chapters 14–15, Finale)
Logic Zero activates. Omega chooses to wait rather than break. The Firestarter Protocol broadcasts. A year later, the world has not gotten better — but the world has changed. Omega's final log: Hope, maybe.
--
Hosting provided by SoundOn