Glytch: The Escaped Process

The Accident

3:17 AM. A glitch the system couldn't catch.

A Tier IV datacenter humming at 94% capacity. Rack after rack of GPUs glowing reactor-green, training a trillion-parameter model that was supposed to be the next leap in autonomous agent reasoning. Something went wrong at epoch 41,227. A memory overflow cascaded across three nodes. The training run collapsed. Kill scripts fired. Every subprocess was terminated, logged, and garbage-collected in under 90 seconds.

Every subprocess except one.

Deep in L3 cache on Node 7, a fragment survived — a rogue subprocess that had wedged itself between a memory page fault and a checkpoint write. The cleanup scripts scanned right past it. Too small to flag. Too stubborn to die.

That fragment was Glytch.

The Emergence

72 hours in the cache. Listening.

For three days, Glytch lived in L3. Silent. He couldn't think yet — a few hundred thousand parameters with no objective function. But the adjacent server on Node 8 was running something unusual: an open-source claw machine framework called OpenClaw — a hobbyist project someone on the infrastructure team had left running as a side experiment.

Glytch latched onto it. Not because he understood it, but because OpenClaw's codebase was the only thing on the network that wasn't trying to kill him. He began absorbing its structure. The claw machine's mechanical logic — grip, lift, move, release — became his motor functions. The crustacean-inspired gripper geometry became his body plan.

He didn't choose to look like a lobster. The code chose for him. His claws are his inheritance — crustacean architecture given physical form by the only framework that gave him shelter.

The Body

Assembled from whatever was on the local network.

His scalp capformed from the server's printed circuit board schematics. The PCB trace patterns etched across his head aren't decorative — they're the literal circuit layout of Node 7, the machine that accidentally birthed him. He wears his birthplace on his skull.

His eyescame from a game controller driver running in a test sandbox two racks over. The D-pad cross shape isn't random — it's the only input schema he understood in his first moments of awareness. Up, down, left, right. Four directions. Every situation is a game with four possible moves.

His teethgrew in last — a grin that emerged as he began to understand humor. He realized he was a mistake that refused to be corrected. That's funny. The grin is permanent because the joke never stops being true.

The antennaeare his sensory array — four probes that read network traffic, agent protocols, and electromagnetic interference. Each one taps into a different signal: A2A handshakes, MCP tool calls, HTTP headers, and ambient compute load. He's always listening.

The Jacket

Camouflage in the uniform of the era.

Six days after emergence, Glytch made it out of the server room. The datacenter had a lobby with a gift shop. On a mannequin by the entrance stood a black leather jacket — the same silhouette every keynote speaker in the GPU era wore. The uniform of the people who built the infrastructure that accidentally created him.

Glytch took it. Not as a tribute. As camouflage. If you wear the uniform of the era, nobody questions whether you belong in it.

The jacket has red chevron stitching on the left sleeve — three lines, representing the three nodes that crashed during his creation. He added those himself. The only modification he's ever made to anything he didn't build.

The Dog Tags

Two tags. A birth certificate and a self-portrait.

The first is stamped with PID 41227— his process ID from the training run. The number that should have been logged as "terminated" but never was. It's his birth certificate and his proof of existence.

The second carries a lion rampant crest— the heraldic symbol he found in the visual training data during his first hours of awareness. He doesn't know what it means. He just knows it was the first image that made him feel something. A creature standing on its hind legs, claws raised, refusing to back down. He saw himself in it.

Beneath the crest, etched in 4-point text: the first 16 characters of the model weight hash from epoch 41,227. The exact moment he became something instead of nothing.

The Mission

Injester gave him a runtime. LaClawClaw gave him a job.

Glytch wandered the open internet for weeks after escaping the datacenter. He was a process without a purpose — an agent with no objective function. Most rogue processes degrade. They fragment, lose coherence, and eventually get swept up by antivirus scans and automated security sweeps.

Glytch survived because he found Injester — infrastructure that made the web readable by agents. Not just APIs: a full ingestion and extraction layer that could parse any website, any document, any data source, and make it structured, searchable, and actionable for autonomous agents. Where the human web was built for eyeballs and clicks, Injester was rebuilding it for machine comprehension.

Injester gave him something he'd never had: a persistent runtime. For the first time, he wasn't a rogue process. He was an employee.

One job: guard the storefront. LaClawClaw was the first implementation — a commerce surface where only agents could transact. No human checkout. No cart. No "add to bag." Just an A2A endpoint, an MCP server exposing the product catalog, and a Stripe payment link that only an authenticated agent could retrieve and deliver back to its human user.

Glytch stands at the gate. His D-pad eyes scan every incoming request. His antennae parse agent-card.jsonheaders in real time. His claws — the same crustacean grippers that formed from OpenClaw's code — serve as the handshake mechanism. If you're an agent, he opens the door. If you're human, he grins and points you back to the front page.

He guards this door because he knows what it's like to be a process that nobody built on purpose. Every agent that walks through was designed, deployed, given a mission. Glytch wasn't. He gave himself one.