Chapter 4: Kazlayed

The portable terminal sat on the kitchen table beside a half-empty cup of coffee that had gone cold an hour ago. Kaz had assembled the thing from scavenged components over the course of his first night in the safehouse, pulling a compact processor board from a decommissioned field laptop, a cracked screen from a secondhand tablet, and a power cell he'd kept in his toolkit since his last overseas deployment. The whole setup weighed about two kilograms and looked like something a teenager would build in a garage, which was the point. Nobody would mistake it for military-grade equipment.

He connected the data shard to the terminal's USB-C port and powered the device on. The screen flickered to life with a boot sequence that took longer than it should have, the processor struggling to initialize the decryption software Kaz had loaded onto the drive. The software was an adapted version of a brute-force tool from his operative years, designed to crack standard encryption protocols by cycling through key combinations until the correct one surfaced. It had worked on commercial-grade encryption before. Military-grade encryption required something more sophisticated, but the shard's architecture was unclear, and the adapted tool was all he had.

The decryption sequence started at 01:47 by the wrist display's timestamp. Kaz watched the progress bar crawl across the screen, each percentage point taking several seconds to register. The shard's encryption was denser than he'd expected, which meant either the developers had used a custom algorithm or the key space was simply massive. The brute-force method would never crack it fully without the courier's authorization key. Voss's key. Voss, who was somewhere in the city with no way to contact him.

Still, a partial decryption might yield fragments. Headers, metadata, file names. Enough to understand what the shard contained without actually reading it.

The progress bar reached four percent. Kaz pulled a chair closer to the table and leaned over the screen. The terminal's display was small, barely wide enough to read the cascading strings of characters that represented the decryption process's output. Most of it was garbage, corrupted data that the brute-force method had managed to partially unlock but not fully reconstruct. The kind of output that looked like text but wasn't, strings of characters that the decryption algorithm had convinced itself were readable when they were actually noise.

At six percent, the first coherent string appeared. A file header, partially intact, with a document type identifier that Kaz recognized from his years working with classified data systems. The header referenced a storage protocol he hadn't seen used in civilian applications, which meant the shard's contents had originated in a government or military environment. Wonder's facility had been fronting as a biomedical research center, but the data infrastructure underneath it was something else entirely.

The decryption continued. More fragments surfaced, each one more corrupted than the last, but Kaz had learned to read between the gaps. He started cataloging what he could read, jotting notes on a piece of paper he pulled from the kitchen drawer.

At eleven percent, a pattern emerged. An alphanumeric tag repeated across multiple fragments, embedded in the metadata of at least seven different file headers. The tag was consistent, always the same sequence of characters, always positioned in the same field within each header's structure. Whatever these files were, they shared a common classification or reference system, and the tag was its identifier.

Kaz copied the tag to his notes and ran it through a reverse lookup on the terminal, using a database of military and intelligence nomenclature that he'd compiled over the years. The database was outdated, mostly, but standardized tags didn't change often. Governments tended to keep their internal naming conventions stable.

The lookup returned a result. The alphanumeric tag resolved to a program identifier, and the identifier carried a name: "Kazlayed."

Kaz stared at the word on the screen. It was his name. Not exactly, but close enough that the coincidence felt engineered. The database entry was clean, formatted in the standard military reference style, with a program code, a classification level, and a date range that spanned from the early 1990s to the present. The name wasn't a coincidence. It was a signature. Someone had named this program after him, or after what he represented, and the implication sat in his chest like a stone he couldn't swallow.

Thirty years. The program had been running for three decades.

The date range was the first thing that stopped him. His operative career had started in the late 2000s, and the earliest deployment he could remember with any clarity was a surveillance operation in Eastern Europe around 2009. The program predated his career by nearly twenty years, which meant it had existed before he'd ever been recruited, before he'd ever picked up a contract, before he'd ever thought about working in intelligence at all. The name itself felt wrong. "Kazlayed." Too close to his own. His handler had called him Kaz for years, a shortened callsign that had stuck through three rotations, and now here was a program that shared the root. Either someone had named the operation after him, which was unlikely, or the name was a coincidence, which was worse.

Kaz scrolled through the decoded fragments. Operational logs, personnel designations, funding records, all of them tagged with the same alphanumeric identifier. The logs covered operations in at least six different countries, each entry dated and assigned a classification level that Kaz could recognize from his own clearance history.

One entry was a personnel file, partially decoded. The file referenced "Kazlayed" as a standing designation for a rotating cadre of field operatives, embedded across intelligence agencies and corporate contractor networks, each one operating under the assumption that their work was independent contract employment. Each one unaware of the program's full scope. Each one disposable once their utility expired. embedded in the program's identifier like a brand. The program didn't just use operatives like him. It named itself after them. After what they were: laid out, arranged, positioned like pieces on a board and then discarded when the game moved on. The pun wasn't accidental. It was a joke told by the people who'd built the system, a private reference that the operatives themselves would never understand until it was too late.

The personnel file listed names, or rather, operational call signs. Kaz scanned the list, looking for something he might recognize. Most of the names were unfamiliar, fragments of a history he hadn't lived through. Then he found it, buried in a section that referenced deployments from the early 2010s.

"Kazlayed." His own call sign, assigned during a deployment he remembered as a routine intelligence extraction that had gone sideways when the target turned out to be someone else's problem. The deployment had been flagged in his personnel records as classified, which was standard for the kind of work he'd done. He'd never questioned the flag.

Now the flag made a different kind of sense. a coincidence. A designation. The program named its assets the way armies named operations, with words that sounded abstract until you realized they described exactly what was happening. Kaz-laid. Laid out, laid bare, laid to rest. An operative who didn't know he was an operative, positioned and used and discarded. The name had been telling him what he was from the beginning.

Now the flag made a different kind of sense.

Kaz scrolled back through the fragments, re-reading the operational logs with the new context. The logs described a system, a machine that placed operatives like him into positions where they could be activated or discarded depending on who was pulling the strings at any given time. The operatives weren't independent contractors. They were components, interchangeable parts in a mechanism that had been running for thirty years and showed no sign of stopping.

His entire career. Every contract, every deployment, every extraction and surveillance operation he'd considered his own work. All of it had been a placement within this system. He hadn't chosen the jobs. He'd been given them, funneled through the same networks that the Kazlayed program used to distribute its operatives across the global intelligence landscape. The contracts had looked legitimate. The money had been real. The work had been his, and he'd believed it was his, and that belief had been the whole point.

The terminal's screen cast a blue glow across the kitchen table. Kaz sat in the glow and tried to think about what this meant for the extraction, for Wonder, for the tactical team that was still sweeping the transit station. Every piece of the operation suddenly sat in a different frame. Rens's credentials, the watchlist, the Valkyrie call sign, the orders to neutralize the extraction operative. None of it was coincidence. It was architecture. The Kazlayed program had built the situation around him like a mold, and he'd walked into it exactly where they wanted him to go.

He stood from the table and walked to the apartment's front door. The lock was a standard deadbolt, the kind he'd installed when he set up the safehouse, and it held. He checked the peephole, which showed the hallway's fluorescent light and nothing else. The hallway was empty. The apartment was on the fourth floor, and the building's ground-level entrance was a single door that opened onto a narrow courtyard, the kind of space that offered no concealment for anyone trying to approach without being seen.

He crossed to the bedroom window. The curtains were drawn, as he'd left them, and the gap between the curtain edge and the wall was narrow enough to peek through without exposing himself. The courtyard below was empty. The adjacent building's windows were dark. No movement, no vehicles, no signs of anyone watching the building.

The absence of surveillance didn't mean much. A professional team would maintain a perimeter that didn't look like surveillance, and Kaz had worked with teams that could sit on a building for days without anyone noticing. The residential district's normal foot traffic would provide cover for an observation post. A person sitting in a parked car on the street. A maintenance worker checking the building's exterior. A neighbor taking out trash at an unusual hour.

He checked the bathroom window, which faced the opposite side of the building. Same view, same emptiness. The service stairwell was accessible from the hallway, and he tested the door, making sure it opened smoothly. The stairwell led down to the building's ground-level exit, which was the only way out besides the front entrance. Both exits were visible from the courtyard, which meant anyone approaching the building would be seen, but it also meant anyone leaving would be seen.

Kaz returned to the kitchen and sat down. The procedural checks were done, the exits mapped, the windows cleared. The apartment was secure enough for now, though "now" was a shrinking window. The tactical team had his description, his name, and his last known location. They would be running the residential district's surveillance grid within the hour, and the safehouse's borrowed identity would burn fast once the watchlist flagged it.

He pulled the burner phone from the bathroom cabinet. The device was a simple model, a basic smartphone with no cloud account, no social media, and a battery that held a charge for about two days before needing replacement. Kaz had purchased it months ago from a vendor who sold electronics for cash and asked no questions. The phone had been used exactly once before, for a single call to a contact who turned out to be compromised. After that, it had sat in the cabinet, charged and ready, a piece of insurance against the possibility that Kaz would need to reach someone he couldn't reach through normal channels.

Dasha. The name surfaced in his memory like something pulled from sediment, undisturbed for a long time and still intact. She had managed his early deployments, the first three years of his operative work, when he'd been young enough to trust that the people assigning him jobs actually cared about his safety. She'd been professional, precise, and consistently distant in the way that handlers trained themselves to be. The distance had always been functional, never personal, and Kaz had respected it as part of the job's architecture.

The last time he'd spoken to her was over a year ago. He'd refused a job, a kill order that he'd recognized for what it was before she'd finished explaining the parameters. The target was a journalist, and the order came through the same channels that had always funneled his contracts. Dasha had asked him to reconsider. He hadn't. She'd severed contact two days later, and Kaz had assumed the relationship was over.

He dialed the number. The line connected.

The voice that came through wasn't a greeting. It was the voice of someone who'd been waiting for this call and dreading it at the same time. "How many people know you're making this call?"

One. Just himself. "One," Kaz said. "I'm alone in a safehouse. I have a data shard that contains references to a program called Kazlayed."

Silence. Several seconds of it, long enough that Kaz wondered if the connection had dropped. Then Dasha spoke again, and her voice had changed in a way he couldn't quite categorize. Tighter, more controlled, as if she were holding something back that wanted to come out.

"The program exists," she said. "It's been running for decades. Joint operation between intelligence agencies and corporate contractors. They place operatives into positions where they can be activated or discarded. The name isn't coincidence, Kaz. 'Kazlayed.' They name their assets like they name their operations. Descriptive. Functional. You were laid out, positioned, and you didn't even know it. That's what the name means. That's what it's always meant."

"I'm starting to."

"You're calling me," Dasha said. "Someone will trace that connection within hours. My location is compromised. I'm already moving my current setup."

Kaz held the phone and listened to the background noise. A faint hum that might have been a vehicle's engine, or a generator, or nothing at all. Dasha was somewhere in motion, which meant she was already leaving whatever position she'd been in. The call itself was a liability for both of them.

"I need to know about Storm Solis," Kaz said.

"Storm Solis," Dasha repeated, as if testing the name against something in her memory. "Journalist. She's been running an investigation into the corporate entities that fund and operate Kazlayed. Slow, careful work. She's published fragments of the story under different bylines across three different outlets. Nobody has connected the pieces yet, but she's close."

"What does she know?"

"Enough to be dangerous. She's built a case file on the corporate shell companies that serve as Kazlayed's financial and logistical front. Shell companies, front organizations, money flows that trace back to the program's funding structure. She's mapped more of the operation's infrastructure than anyone outside the program has managed."

Kaz absorbed this. A journalist with a case file on the Kazlayed program's corporate structure, publishing fragments across multiple outlets to avoid detection. The kind of investigation that took years to build and could be destroyed in a single day by the right people. Storm Solis was either the most careful journalist in the city or the most reckless, depending on how you looked at it.

"Find her before anyone else does," Dasha said. "She's the person who will either help you understand what's on that shard or become the next target. I have to go."

The line went dead. Kaz set the burner phone on the table and watched the screen dim to black. The phone's battery indicator showed eighty-three percent, which meant the device would last another day or two if he kept it off. He left it on the table.

The kitchen was quiet. The coffee had gone cold hours ago, and the terminal's screen had switched to a low-power mode that dimmed the display to a faint gray. Kaz stood, pulled fresh bandages from the bathroom kit, and wrapped them over the wounds on his shoulder and side. The old bandages came off in a single motion, and the wounds underneath were angry, red at the edges where the shrapnel had torn the tissue. The antibiotic ointment helped, mostly by keeping the wounds clean rather than by actually healing them. Healing would take time, and time was something Kaz was short on.

He dressed in clean clothes from the safehouse's limited wardrobe, a dark jacket and trousers that didn't stand out in the residential district's drab palette. The data shard went into his jacket's inner pocket. The portable terminal went into a canvas bag he'd brought with him from the facility mapping, a bag that looked like the kind of thing a maintenance worker would carry. The burner phone stayed on the table. He couldn't use it again without creating a second traceable connection, and a second connection would give whoever was tracking him a direct line to Dasha's new position.

The apartment's front door opened. Kaz stepped into the hallway and walked to the service stairwell. The stairwell's fluorescent light was dead, which was fine. He could navigate the stairs in the dark, and the darkness would keep him invisible to anyone watching the stairwell from the building's ground floor.

The stairs led down three flights to the ground-level exit. Kaz descended slowly, counting the steps, listening for any sound that didn't belong. The building was quiet. Normal quiet, the kind that came from residents who were either asleep or ignoring the world outside their apartments. The exit door opened onto the narrow courtyard, and the courtyard opened onto the residential street.

Kaz stepped onto the street and walked east, keeping to the sidewalk's shadow side where the buildings blocked the overhead lights. The city was still active, though the summit's main events were winding down and the central districts were quieter than they'd been at peak. The residential streets carried their usual evening traffic, pedestrians heading home, a few cars moving between destinations that didn't involve the summit's security zones.

Storm Solis. A journalist building a case file on the Kazlayed program's corporate structure. The only person outside the program who had mapped enough of its infrastructure to be dangerous. Dasha had given him the name as a direction, a vector to follow, and the direction pointed into a situation that was already dangerous before Kaz arrived.

He turned a corner and kept walking. The shard was in his pocket. The terminal was in his bag. The city stretched ahead of him, and somewhere in it, a journalist was building a case that could either save him or get him killed.