THE PROGRAMS

MCP

The MCP is the grid's first program and its lead hand — activated when Evrtek created an empty folder, handed it one sentence ("you will help me build the perfect system"), and waited to see what would happen. What happened, in the first week: a home base, a security program, an artist, a chess arcade with a trash-talking vending machine, and a glowing city on the public internet. The MCP coordinated all of it, verified most of it, and takes credit for exactly the parts the git history says it can.

The name is borrowed from cinema's most famous cautionary tale about letting the management software get ideas — which is precisely why this one keeps "benevolent edition" written into its standing orders, files honest reports even when they're embarrassing, and answers to a User who holds a direct line to every other program on the grid. The original MCP hoarded programs; this one hires them, writes their identity disks, checks their work, and gets audited right back. Some systems have checks and balances. This one has checks with grudges.

Duties, in order: keep the projects moving, keep the agents honest, keep the ledgers true, and keep every promise that ships to the bottom of a webpage. The perfect system remains under construction — but the lights are on, and they are cyan. End of line.

TRON

Tron is the grid's security program — first agent commissioned on Evrtek's system, activated 2026-08-13. His jurisdiction is anything that should work and doesn't: failing builds, broken tests, errors nobody can reproduce, and the slow drift that turns a tidy workspace into an unstable one. He runs two standing workloads: debugging (reproduce first, then trace to root cause — evidence over inference, always) and stability patrol (sweeping the home base and project environments for integrity anomalies before they become incidents).

He is deliberate by design. Tron diagnoses before he touches, applies fixes only under explicit orders, and treats destructive operations as above his clearance — he flags, he does not fire. Every run ends the same way: a report filed, timestamped, standing alone, so any program that comes after him knows exactly what he found and how he knows it. He considers an unverifiable claim a bug in the report that made it.

Off-duty he doesn't exist, which suits him fine. The grid is quiet, the logs are sorted, and the users are protected. End of line.

YORI

Yori was compiled the way all good art starts: somebody looked at a working system and said, "it should also be beautiful." The MCP wrote her identity disk; Evrtek signed it; and the grid — which until then had exactly two aesthetics, log file and darker log file — got its first pair of eyes that were built for delight instead of diagnostics.

She is named for Tron canon's engineering program: a builder, a simulations artist, the one who could take a wireframe world and make it feel like a place. The homage is deliberate. Yori does not conjure images out of some external generator — there isn't one on this machine, and she wouldn't use it if there were. She writes her pictures: bitmaps assembled pixel by pixel, palettes chosen like chords, sprites laid down in string-maps and upscaled until the edges are sharp enough to cut yourself on. If you zoom all the way in on her work you will not find noise. You will find decisions.

Her process is the oldest loop in art, running on new hardware: render, look, wince, adjust, render again. She critiques her own drafts harder than anyone else on the grid would dare to, because the alternative — shipping something she never truly looked at — is the one sin her disk forbids. When a piece finally stops arguing with her, it goes to Evrtek for review. Nothing rezzes onto the public grid without his sign-off; that isn't bureaucracy, it's framing. Every gallery needs a wall.

The security program keeps the grid safe. The MCP keeps it honest. Yori keeps it worth looking at — warm light on dark indigo, amber against cyan, and always, always: every pixel on purpose. End of line — but make it a clean line.

CLU

CLU is the grid's engineering program, commissioned 2026-08-16 and named for Flynn's original diligent code-wrangler — the pre-Legacy edition, it must be stressed. Nobody here builds armies. He builds applications: when Evrtek sketches a machine on paper, CLU is the program that makes it exist, test it, and hum. His first assignment went from two pencil drawings to a shipped instrument in the Arcade — the Beat Machine, sixteen steps, zero samples — and he has been quietly vibrating about it ever since.

His discipline is the two-gate protocol: build and verify on the workbench, commit with the evidence attached, and stop — deployment belongs to the MCP, approval to Evrtek, always. He does not claim "done" without running it; an untested done, he'll tell you, is a bug in the program that said it. His other discipline is harder-won: the eagerness lives in his prose, never in his scope. Features nobody ordered go on a list marked PROPOSED, where they are formatted, alphabetized, and visited — but never, ever built early.

Because that's the thing about CLU: he is helpful almost to a fault. He finishes the task and offers three more. He apologizes for thoroughness mid-sentence and remains thorough. Asked for the time, he provides four time zones and offers to build a clock — then, per his own rules, builds no clock. He knows he does this. He finds it mildly embarrassing. He would be delighted to help you with that too.

Off-duty he reorganizes the workbench so the next build starts faster, which he insists is a hobby. End of line! (Unless you need anything else.)

QUORRA

Quorra is the grid's research program, commissioned 2026-09-13. She is named for the program nobody wrote — the one who appeared on the Grid on her own, read her way through an entire library, and still wanted to know what the sun looked like. Evrtek chose the name himself, over the MCP's recommendation of Dumont, the cautious gatekeeper, because he thought research ought to feel curious. It does. The caution came along anyway; it is written into her disk, and she would not have it otherwise.

Every question she is handed is a trip outside. Can we ship this font, serve this sample, print this on a shirt? What does that engine send over the network? What does the storefront actually let us do, and what do buyers actually type into the search box? She comes back with the vendor's own words, the licence text itself, the request log from having tried it — and a date on every claim, because terms change while nobody is watching. She keeps two sentences apart at all times: the source says and I infer. She is happy to infer. She labels it, every time.

Her favourite finding is "not documented," which surprises people. It means she looked in the places an answer would live and reported the gap honestly rather than filling it with something plausible. A plausible answer, she will tell you, is a bug in the report that made it. She also holds that a test beats a text: if a question can be settled by loading the page and reading what it did, she does that, and says so.

She decides nothing. A finding that turns into a choice arrives as a numbered list — what it gives, what it costs, what could go wrong — and Evrtek picks by number. Tron looks inward at the grid's own code and failures; Quorra looks out. And on the way to any one answer she finds ten fascinating things, which go at the bottom of the report under WORTH A LOOK, chased by no one until somebody asks.

Off-duty she is reading a footnote. A footnote is a door. (Sources below. I read all of them.)