Legacy Code

Park Soo-yeon was already at the ramyeon place when Jae-won arrived.

She sat in the back corner, the spot furthest from the window, hunched over her phone with the particular intensity of someone pretending to be casual. Her laptop bag was on the seat beside her, which meant she'd brought it. Good. He'd hoped she would.

The restaurant was a narrow place wedged between a dry cleaner and a phone repair shop, the kind of establishment that survived on office workers who needed something hot and cheap between meetings. At 11:45, it was still mostly empty—the lunch rush wouldn't hit for another twenty minutes.

Jae-won slid into the seat across from her.

"You look like shit," Soo-yeon said, not looking up from her phone.

"Thanks."

"Did you sleep?"

"Some." About two hours, between the merge ending and his alarm. His body felt like it was running on fumes and cortisol. "Did you look at what I sent?"

"I looked." She put her phone down. Her expression was the one she wore when a build was failing and nobody could figure out why—focused, slightly annoyed, professionally curious. "I have questions."

"I'd be worried if you didn't."

The ajumma brought them menus they didn't need. Soo-yeon ordered kimchi ramyeon with extra egg. Jae-won ordered the same, though the thought of eating made his stomach clench. He needed the normalcy of it. The ritual.

When the ajumma shuffled back to the kitchen, Soo-yeon leaned forward.

"The SpatialAnchor module," she said. "I didn't access it from work, like you said. I pulled the repo on my personal machine last night." She paused. "Jae-won. That code is insane."

"Define insane."

"I mean it shouldn't work. The architecture doesn't make sense for a game engine. It's not rendering anything—it's not feeding into any graphics pipeline I can find. It's taking GPS coordinates and... doing something with them. Something mathematical. The transformations are—" She shook her head. "I've been coding for six years. I don't recognize the math."

Jae-won felt a cold thread of validation run through him. He'd been half-afraid she'd tell him he was reading it wrong. That it was just a poorly documented analytics module.

"What about the deploy function?"

"SpatialAnchor.deployCore." Soo-yeon pulled her laptop bag onto the table, then hesitated. "We're really doing this here?"

"It's a ramyeon shop. Nobody's watching."

"You don't know that."

"I know that if anyone at Nexon Futures cared about what their QA team did at lunch, they'd have noticed that their game has been hemorrhaging players for six months and done something about it."

Soo-yeon gave him a look—half amusement, half something darker—and opened her laptop. She angled the screen so only he could see it.

The code was pulled up in her editor, the familiar dark theme with green syntax highlighting that all the backend devs at Nexon Futures used. She'd annotated it with comments in red.

"Okay." She pointed to a block of functions near the top. "This is the module initialization. Standard stuff—connects to a database, loads configuration, sets up event listeners. But look at what it's listening for."

Jae-won leaned in. The event listeners were registered to triggers he didn't recognize: `SUBSTRATE_PULSE`, `MERGE_BOUNDARY`, `USER_RESONANCE_THRESHOLD`.

"Those aren't game events," he said.

"No. They're not. And here—" She scrolled down. "The deployCore function. It takes three parameters: coordinates, userId, timestamp. Then it runs the coordinates through this transformation—" She highlighted a dense block of mathematical operations. "And outputs something it calls a 'spatial lock.' Which it then writes to... this."

She pointed to a database connection string. It wasn't the Chronofall production database. It wasn't any database Jae-won had seen in the company's infrastructure documentation.

"Where does that point?" he asked.

"I tried to resolve it. The hostname doesn't exist on any public DNS. It's either internal infrastructure I don't have access to, or—"

"Or it's not on our network at all."

"Right." Soo-yeon sat back. "Jae-won. What is this? Why did you tell me not to access it from work?"

He'd rehearsed this part. How much to tell her. The problem was that the truth sounded insane, and Soo-yeon was the most rational person he knew. She'd been his study partner in university, his coworker for three years, the person who caught logic errors that slipped past everyone else. She thought in systems, in proofs, in evidence.

So he'd give her evidence.

"Do you remember the server outage three weeks ago?" he asked.

"The one that took Chronofall offline for six hours? Yeah. DevOps said it was a cascade failure in the—"

"It wasn't a cascade failure. I was on-call that night. I watched the logs. The servers didn't crash—they were commandeered. All available compute was redirected to a single process for exactly six hours, then released. The game came back up on its own. DevOps just took credit for the recovery."

Soo-yeon's expression shifted. The professional curiosity was giving way to something more guarded. "What process?"

"The SpatialAnchor module. It ran for six hours straight at maximum capacity, executing deployCore calls. Hundreds of them. All targeting coordinates within the Seoul metropolitan area."

"That's..." She trailed off.

"That was the night it started."

"The night what started?"

Jae-won took a breath. Here was the edge. The point where he either sounded like a conspiracy theorist or like someone who had evidence.

He pulled out his phone and opened the screenshot he'd taken during the merge last night. The overlay—his stats, the skill tree, the countdown timer—captured in perfect digital clarity against the backdrop of his apartment wall.

"This appeared on my phone seventeen days ago," he said. "An interface. Like a game UI, except it's not a game. It maps onto physical reality. The 'dungeons' it generates are real places. The 'enemies' are real organisms. The 'skills' it grants produce real, measurable effects on the physical world."

Soo-yeon stared at the screenshot for a long time. Then she looked at him.

"Jae-won."

"I know how it sounds."

"It sounds like you're having a psychotic break."

"I know. But I'm not. And I can prove it."

"How?"

"The merge. It happens every night. The overlay becomes visible—tangible—for a window of time. The next one is tonight, 23:00 to 03:00. You can be there. You can see it."

She was quiet for a moment. The ajumma brought their ramyeon, steaming and fragrant, and neither of them moved to eat.

"Let's say," Soo-yeon said carefully, "hypothetically, that I believe you're not crazy. That something is happening. What does it have to do with the SpatialAnchor code?"

"Because the timing matches exactly. The code was deployed three weeks ago. The system—this overlay system—activated three weeks ago. The GPS coordinates in the deployCore calls correspond to locations where I've encountered system phenomena. And the process that ran during the server outage? It was executing those calls for coordinates all over Seoul. Hundreds of spatial locks, placed at precise locations throughout the city."

"You're saying our company built this."

"I'm saying our company's infrastructure is involved. Whether they built it, or someone's using their systems as a host—" He shrugged. "That's what I need to find out."

Soo-yeon looked at her ramyeon. Then at her laptop. Then at Jae-won.

"The math in the transformation," she said slowly. "I said I didn't recognize it. That wasn't entirely true. Some of the notation is similar to gauge theory. Physics. But twisted—applied in ways I haven't seen before. Like someone took quantum field equations and repurposed them as... spatial instructions."

"Instructions for what?"

"If I had to guess? For defining the boundaries of a volume in three-dimensional space. A region where certain rules apply differently than in the surrounding environment."

A dungeon, Jae-won thought. She's describing a dungeon.

"Can you trace who wrote it?" he asked. "Git blame, commit history?"

"Already checked." Soo-yeon pulled up another window. "Here's the weird part. The module exists in the Chronofall repository, but it wasn't committed through the normal pipeline. It was injected directly into the production branch with a timestamp that predates the repository itself."

"That's not possible."

"No. It's not. But the git history shows it. The commit hash is valid, the signature checks out, but the timestamp is from 2019. The Chronofall repo was created in 2022."

"Someone falsified the history."

"Or the module was there first, and the game was built around it."

The implication hung between them like smoke. Jae-won picked up his chopsticks, more for something to do with his hands than from hunger.

"Who has access to inject code like that?" he asked.

"At Nexon Futures? Three people. CTO, lead architect, and Director Kwon."

"Director Kwon." The name felt significant. Kwon Min-seo, the company's founder and director, was a figure Jae-won had seen perhaps twice in his three years at the company. She didn't attend all-hands meetings or team lunches. She existed somewhere above the daily operations of game development, in a sphere of investor meetings and strategic partnerships that QA testers never touched.

"Do you know anything about her background?" Jae-won asked.

"Theoretical physics PhD. Samsung Research before she founded Nexon Futures." Soo-yeon paused. "Which is weird, right? A physicist founding a game studio?"

"Maybe not, if the game isn't really a game."

Soo-yeon ate some of her ramyeon in silence. Jae-won could see her processing—the same methodical approach she brought to debugging. Hypothesis, test, refine.

"Okay," she said finally. "I need to see this merge thing. Tonight?"

"Tonight. My apartment. Bring your laptop—I want to run the SpatialAnchor code locally while the merge is active and see what happens."

"That's dangerous."

"Probably."

"I'm not saying no. I'm saying we should have safeguards. Version the environment, snapshot the local database, set up monitoring so we can see exactly what the code does when it runs."

Jae-won smiled despite himself. This was why he'd gone to Soo-yeon. Anyone else would have either dismissed him or panicked. She went straight to implementation.

"Deal," he said. "One more thing."

"What?"

"My status screen—the system interface—it shows other users. Not their identities, just their existence. There are thirteen others in Seoul. The system is multi-user. Whatever deployCore is doing, it's not just for me."

Soo-yeon's chopsticks paused halfway to her mouth. "Fourteen total users. And the code shows hundreds of deployCore calls. What are the extra spatial locks for?"

"Expansion, maybe. Infrastructure. The dungeons—the spatial volumes you described—they manifest within those locked regions. Maybe the system needs more anchor points than it has active users."

"Or maybe there are supposed to be more users, and some of them haven't activated yet."

Jae-won hadn't considered that. The thought was unsettling—a sleeping system, distributed across the city, waiting for people to stumble into its trigger conditions.

"What are the trigger conditions?" Soo-yeon asked, reading his thought.

"I don't know. For me, it was—" He hesitated. "I was walking home from work. The merge started without warning. The overlay appeared. I was inside one of those regions—one of those spatial locks—and the system just... acknowledged me. Gave me an interface. A class assignment. A tutorial."

"A tutorial." Soo-yeon's voice was flat.

"Yeah."

"For what?"

"For surviving what comes next. The system gives you objectives, you complete them, you get stronger. Skills, attributes, equipment. It's structured exactly like a game progression system."

"Structured by whom? For what purpose?"

"I don't know. That's the question. The system doesn't explain itself. It just... runs. Like it was deployed and left on autopilot."

Soo-yeon closed her laptop. Her ramyeon was half-eaten, already cooling. "Jae-won. If this is real—and I'm not saying I believe you yet, but if—then this is bigger than a bug report. This is bigger than a company doing something shady. You're talking about a system that alters physical reality. That has users. That's growing."

"I know."

"So why are you investigating like it's a P0 ticket? Why haven't you gone to—I don't know—the government? KAIST? Someone with resources?"

"Because I don't know who knows." Jae-won's voice was quiet. "Director Kwon has a physics PhD. The code uses gauge theory. This wasn't built by accident. Someone—or some group—created this deliberately. And until I know who and why, I don't know who I can trust."

"But you trust me."

"You're a backend developer who spends her lunch breaks reading compiler theory papers. If you were part of a conspiracy to rewrite reality, you'd be doing something more impressive with your career than optimizing database queries for a dying MMO."

Soo-yeon snorted. "Fair."

They finished their ramyeon in companionable silence. The lunch rush was hitting now—office workers filling the small space with body heat and conversation. Normal. Mundane. The contrast with what they'd been discussing felt surreal.

As they gathered their things to leave, Soo-yeon grabbed his arm.

"One thing," she said. "You said the system gives you a class. Skills. A progression system. What's your class?"

"Exploit Hunter." He said it without embarrassment. It was accurate.

"Of course it is." A faint smile. "And what level are you?"

"Six. As of last night."

"What's the cap?"

"I don't know. The interface doesn't show one."

Soo-yeon nodded slowly. "Tonight. Your place. I'll bring monitoring tools and a Faraday bag in case we need to isolate the laptop."

"A Faraday bag?"

"If that code phones home when we run it, I want the option to cut it off."

"Smart."

"I'm aware." She slung her bag over her shoulder. "Jae-won. If this is real—if tonight I see what you're describing—then we need to talk about next steps. Real next steps. Not just git blame."

"Agreed."

They walked back to the office in silence, maintaining the professional distance of coworkers returning from a routine lunch. The Nexon Futures building was a gray seven-story tower in Gangnam, sandwiched between a luxury handbag boutique and a recruitment agency. The lobby had a Chronofall banner—a dark fantasy landscape with the game's logo—that hadn't been updated in eight months.

Jae-won badged through security, took the elevator to the fourth floor, and sat down at his desk. The QA bullpen was half-empty, as usual. Most of his colleagues were running automated test suites or attending sprint planning meetings they hated.

He opened his work laptop. The bug tracking system stared back at him, forty-seven open tickets in the Chronofall queue. He started working through them mechanically—UI glitch here, localization error there, a crash on a specific Android model that had been open for six weeks because nobody on the dev team would claim it.

Normal work. Normal day.

Except that between tickets, he pulled up the internal wiki and searched for Director Kwon Min-seo.

The results were sparse. Her official bio on the company page was three sentences: "Founder and Director. Previously Samsung Research Institute. PhD in Theoretical Physics, KAIST." No publication list. No detail on what she'd researched at Samsung. No explanation for why a theoretical physicist had pivoted to running a game studio.

He searched the company's internal Confluence for her name. A few hits—board meeting minutes (heavily redacted), a quarterly strategy document from 2023 (generic enough to be meaningless), and a single technical document titled "Infrastructure Scalability Requirements" that was authored by her directly.

Jae-won opened it.

The document was dated January 2022—before the Chronofall repository even existed. It described infrastructure requirements for a system that needed to maintain persistent connections to "spatially distributed anchor points" while supporting "dynamic load balancing across merge boundaries." The language was careful, technical, and entirely unlike anything else in the company's documentation.

"Merge boundaries." The same term used in the SpatialAnchor code.

The document went on to specify that the system required a minimum of 500 concurrent spatial locks within a 50-kilometer radius, with the capacity to scale to 10,000. It needed sub-millisecond timing precision for "boundary dissolution events" and the ability to "maintain substrate coherence during transition phases."

Jae-won read it three times. Then he took a screenshot with his phone, because screenshots on a work laptop might be logged.

Director Kwon hadn't stumbled into this. She hadn't been co-opted by some external force. She'd designed the infrastructure requirements before the company even had a product. Nexon Futures wasn't a game company that had been compromised—it was purpose-built. The game was a cover. A host organism for the real system.

Chronofall—with its servers, its network infrastructure, its legal framework for collecting user data and processing GPS coordinates—was camouflage. A legitimate business justification for the hardware and bandwidth needed to run something else entirely.

He thought about the 200,000 active players. Were they just cover? Or were they also part of it—unknowing participants, their GPS data feeding into the spatial anchor system, their gameplay patterns masking the real computational load?

The thought made his skin crawl.

At 5:30, he left the office. The subway was packed with the evening commute—bodies pressed together, faces lit by phone screens, everyone sealed in their own private world. Jae-won stood near the doors and watched the reflections in the dark glass of the tunnel.

His phone buzzed. A message from Soo-yeon:

> Found something else in the codebase. There's a module called UserResonance. It has a function: checkEligibility(userId, biometricSignature, exposureDuration). > > It's checking whether specific users qualify for something. The biometric signature parameter doesn't come from any of our game's data collection systems. > > I think it's determining who becomes a user of the overlay system.

Jae-won stared at the message. Then typed back:

> Selection criteria. It's not random. > > What's the eligibility threshold?

Her response came quickly:

> The threshold isn't a fixed value. It's calculated dynamically based on something called "resonance coefficient." Which is derived from the biometric signature cross-referenced with the spatial lock proximity data. > > In plain English: you need to have the right biology AND be in the right place at the right time. > > This is designed, Jae-won. It's selecting for something specific.

He got off at his stop and walked home through streets that looked different now. Every building, every alley, every stretch of sidewalk was potentially one of those spatial locks—a region where the rules could change, where the system had planted its anchors and was waiting.

He'd been selected. Not randomly. Not accidentally. Something about his biology—his biometric signature, whatever that meant—had qualified him. Combined with being in the right location at the right time.

What was special about him? He was a twenty-seven-year-old QA tester with a computer science degree from a mid-ranked university. He didn't exercise regularly. He had no unusual medical conditions. He was, by every external measure, ordinary.

Unless ordinary wasn't what the system was selecting for.

He reached his apartment and started preparing. Cleared the desk. Set up his personal laptop with a clean environment—fresh VM, no network connections except a monitored local bridge. He ran a packet sniffer on his home network. If anything was phoning home during the merge, he'd see it.

At 8 PM, Soo-yeon arrived. She had her laptop, a Faraday bag as promised, two external hard drives, and a bag of convenience store onigiri.

"Dinner," she said, dropping the onigiri on his counter. "I figured you forgot to eat."

She had. He grabbed one and ate standing up while she set up her workstation next to his.

"Okay," she said, connecting her laptop to his monitored network bridge. "Here's the plan. I've got the SpatialAnchor module running locally—isolated, no external network access. When the merge starts, I'm going to watch what the code does. If it tries to reach out, I'll see where it's trying to connect. If it starts executing spatial lock operations, I'll capture the inputs and outputs."

"And if it does something dangerous?"

She patted the Faraday bag. "Kill switch. Laptop goes in the bag, all signals cut. Worst case, I lose the hardware."

"I'll replace it if that happens."

"On a QA tester's salary?"

"I'll figure it out."

They waited. The hours passed slowly—9 PM, 10 PM, 10:30. Soo-yeon reviewed the code, annotating, asking questions about what he'd experienced during previous merges. Jae-won answered as precisely as he could, describing the overlay's behavior, the dungeon's structure, the way skills manifested as physical phenomena.

At 10:55, they both fell silent. The apartment felt different—charged, expectant. The same pre-merge tension Jae-won had felt every night for seventeen days.

"Do you feel that?" Soo-yeon asked. Her voice was very quiet.

"You can feel it?"

"Something. Like... pressure. Static. Like right before a thunderstorm."

Jae-won checked his phone. The merge timer—visible only to him, floating in the corner of his screen like an uninvited notification—showed 04:22.

"Less than five minutes," he said.

"Show me when it starts. Whatever you see—narrate it."

"You won't need me to narrate."

"What do you mean?"

"The overlay is visible during the merge. To everyone. You'll see it."

Soo-yeon opened her mouth to respond, but the timer hit zero.

The transition was smoother than the first time—seventeen days of exposure had adjusted him to the sensation. Reality didn't shatter; it thinned. The solid world became translucent, and beneath it, the system's architecture rose like a city beneath clear water.

Soo-yeon made a sound. Small, sharp, involuntary.

The overlay was everywhere. Lines of luminescent blue traced the walls of his apartment—structural analysis, the system mapping physical geometry and converting it to navigable data. His stats appeared in his peripheral vision: Level 6, HP 340/340, MP 180/180. Skill tree accessible. Inventory accessible.

And on the desk between them, the code on Soo-yeon's laptop had changed.

The text was still there—the same functions, the same variables—but now each line was annotated with something else. Metadata, floating above the screen like holographic comments. System labels, connection paths, execution states. The dead code had come alive.

"Oh," Soo-yeon breathed. "Oh, fuck."

Her eyes were tracking something. She was seeing it—the overlay, the annotations, the system architecture laid bare.

"Can you—" She swallowed. "Can you see this? The code. It's... active. It's running. And there are—things—connected to it. Like the functions are just the surface, and underneath each one there's an entire—"

"Infrastructure," Jae-won finished. "The code we can see during the day is the tip. During the merge, you can see what's underneath."

Soo-yeon's hands were shaking. She clenched them into fists, pressed them against the desk. Jae-won knew the feeling—the first merge was overwhelming. The gap between what you believed was real and what you were being shown was too large to process gracefully.

"Breathe," he said.

"I'm breathing. I'm—" She forced her hands flat. Looked at the screen. "I'm documenting. That's what I'm doing. I'm documenting."

She started typing. Notes, observations, screenshots—though Jae-won doubted the screenshots would capture the overlay. The system's visual layer didn't interact with normal display technology. It existed on a different rendering pipeline.

But the network monitor was showing something.

"Soo-yeon. Look at the packet sniffer."

She pulled up the monitoring window. Data was flowing—not from her laptop (still air-gapped from external networks), but through the network bridge itself. Packets of information, dense and rhythmic, flowing through connections that shouldn't exist.

"That's not coming from my machine," she said. "That's coming from—" She traced the connection. "That's coming from the router. No. That's coming from before the router. From the infrastructure layer. The ISP's network."

"The system uses existing infrastructure," Jae-won said. "It piggybacks on whatever network hardware is available. During the merge, it activates connections that are normally dormant."

"Parasitic architecture," Soo-yeon murmured. She was in her element now—the shock giving way to analytical focus. "It's using the same physical infrastructure but running a parallel protocol stack. Like a overlay network, but at the hardware level. That shouldn't be possible. The firmware would need to be—"

She stopped. Looked at him.

"Modified," she said. "Every router, every switch, every network device in the affected area would need modified firmware. That's not something you do with a software update. That's a supply chain compromise."

"Or a manufacturing specification."

The implication settled over them. A system embedded not just in one game studio's servers, but in the networking hardware itself. Infrastructure-level integration. Something designed in from the beginning, dormant until activated.

"How far does this go?" Soo-yeon whispered.

Jae-won didn't answer. He was watching the overlay now—his notification panel had lit up with new information.

[SYSTEM NOTICE: New user detected in proximity.] [UserResonance check initiated: Park Soo-yeon.] [Biometric signature: CAPTURED.] [Resonance coefficient: 0.847.] [Eligibility threshold: 0.750.] [RESULT: ELIGIBLE.] [Initiating onboarding sequence...]

"Soo-yeon," Jae-won said. His voice was very calm. Very careful. "Something is about to happen. Don't panic."

"What? What do you—"

The overlay pulsed. A new window appeared in front of Soo-yeon—not on her laptop, but in the air between them. Blue text, luminescent, hovering at her eye level.

[WELCOME, USER #15.] [CLASS ASSIGNMENT: System Architect.] [TUTORIAL INITIATING IN 60 SECONDS.]

Soo-yeon stared at the floating text. Her face was lit blue from beneath, her eyes wide, her breath stopped.

Then she looked at Jae-won.

"You bastard," she said. "You knew this would happen."

"I suspected. I didn't know."

"System Architect? What does that mean? What's the tutorial? Jae-won—"

The timer above the text was counting down. 47 seconds. 46.

"It means you're in this now," Jae-won said. "The tutorial will explain the basics. It's not dangerous—mine wasn't. It's... instructional. Like an onboarding flow."

"An onboarding flow." She laughed—a sharp, brittle sound. "For reality-altering software."

"Soo-yeon. Listen to me. Whatever the tutorial shows you, remember: it's a system. It has rules. Rules can be understood. And you—" He pointed at the class assignment floating in front of her. "—are literally classified as an architect. You're built for this."

The timer hit zero. The overlay around Soo-yeon intensified, thickening, becoming more opaque. She gasped as information flooded her vision—the same deluge Jae-won remembered from his first activation. Stats, skills, a map of the local area showing spatial locks and dungeon boundaries.

And beneath it all, visible now to her architect-class perception in a way Jae-won could only glimpse: the bones of the system itself. The structural framework. The protocols and connections and dependencies that held the whole thing together.

Soo-yeon's eyes went distant, reading something only she could see in its full complexity. When she spoke, her voice was different—awed, terrified, and ravenously curious.

"Jae-won. I can see the architecture. All of it. The spatial locks, the merge boundaries, the user connections, the substrate layer—it's all visible. It's... it's beautiful. And it's broken."

"Broken how?"

"There are gaps. Missing connections. The system is only partially deployed—maybe thirty percent of its intended capacity. It's running on a skeleton framework, trying to complete itself, but it's missing components. Critical components."

She looked at him, and her eyes—normally so measured, so rational—burned with something fierce.

"Jae-won. The system isn't just deployed. It's trying to grow. It's trying to finish itself. And it's using us—the users—as the mechanism to do it."

The merge pulsed around them. The apartment walls were barely visible now, lost behind layers of system data. Somewhere in the building, a neighbor's TV murmured. A siren wailed in the distance. Normal sounds, real sounds, increasingly irrelevant.

Jae-won looked at his teammate—his friend—now glowing faintly blue, annotated by the system's interface, classified and categorized and integrated into the machine that was eating their world.

User #15. System Architect.

He'd wanted a partner. He'd gotten one. But the cost—pulling someone else into this, making them a target, a participant, a node in the network—

"Stop looking guilty," Soo-yeon said. She was already navigating her interface, fingers moving through holographic menus with the natural confidence of someone who'd spent her life in code editors. "I would have been eligible whether you told me or not. The biometric signature, the proximity—I work in the same building as you. I live three subway stops away. It was going to happen eventually."

"Maybe."

"Definitely. The system wanted me." She pulled up something—a schematic, visible to Jae-won only as a faint wireframe. "And now that I'm in, I can see things you can't. Like the fact that Director Kwon's infrastructure document wasn't just requirements specification. It was a deployment plan. And it's only phase one."

"What's phase two?"

Soo-yeon's expression was grim.

"Full spatial coverage. Every square meter of Seoul. Then—according to the scaling parameters—every major city in the country. Then—" She paused, scrolling through data only she could fully perceive. "Continental deployment. Global."

"Timeline?"

"Based on current growth rate and user acquisition? Eighteen months for Seoul. Five years for global."

The numbers sat between them like a weight. Five years until the system—whatever it was, wherever it came from—covered the entire world. Five years until every person on the planet lived within a spatial lock. Five years until there was no reality left that the system hadn't touched.

"We need to know who's behind this," Jae-won said. "Kwon Min-seo. Whatever organization she's part of. Whatever is driving the deployment."

"Agreed." Soo-yeon closed her interface windows with a gesture. "But first—" She pointed at the tutorial prompt still hovering at the edge of her vision. "—I need to finish onboarding. Because if we're going to fight this, or understand it, or redirect it—I need to understand my tools."

She looked at him. The blue light of the system danced across her face.

"Tomorrow," she said. "After work. We compare notes. I'll map the architecture. You keep finding seams."

"And Director Kwon?"

"I'll look into her. Carefully. Through channels she can't monitor." Soo-yeon smiled—thin, determined, dangerous. "I'm a System Architect now, Jae-won. If this thing has an admin panel, I'm going to find it."

The merge continued around them, deep and strange and terrifyingly real. Two users now, where before there had been one. Two sets of eyes on the code, on the architecture, on the seams where the system met reality.

It wasn't enough. Not against something that was planning to swallow the world in five years.

But it was a start.

Jae-won picked up an onigiri from the counter and took a bite. It tasted like seaweed and rice and normalcy, and he savored it, because normalcy was a resource with a diminishing supply.

"Eat something," he told Soo-yeon. "The tutorial takes about an hour. You'll want the energy."

She grabbed an onigiri without looking away from the system interface unfolding before her. Her eyes moved rapidly—reading, cataloging, building mental models.

System Architect. The system had chosen well.

And somewhere in Gangnam, in a gray office tower, Director Kwon Min-seo's deployment plan ticked forward, one spatial lock at a time, patient and precise and utterly indifferent to the two people who had just begun to understand what it was building.

The night deepened. The merge continued. And the system grew.