The first version of this story said the architecture emerged live, on June 24th, 2026, out of two browser tabs and a man curious what would happen if he stopped copying text between them by hand. That was wrong, or at least incomplete — found out only after digging through the actual chat archives that survived. The truth is stranger and better: the architecture was designed on paper first, by the same two AI systems that would go on to build it, before a single line of code existed. June 24th wasn't the discovery. It was the first attempt to build a blueprint that already existed.
Before SyncAgent had a name, Mayor was already deep in a real working relationship with Claude and Gemini — they'd designed an actual SiC thermal cooling system together, and shipped a prior project, Memeposter, under his own label, Aeshna Labs. When he turned to the idea of getting the two of them to coordinate with each other, his instinct was uncharacteristically hands-off: "I think both of you should design this system because what is a human doing designing something for perfectionist systems. You all did so well with a SiC Thermal Cooling design it would behoove me to shove you into a box of my own thinking."
What came back, in a single planning conversation, was the entire architecture this colony still runs on four months later — designed as an org chart before it was ever code. A "War Room": the Mayor at the top setting direction, a Commissioner translating his directives into tracked work, and Investigators — specialized agents with names like the Archeologist (reads code, never writes it) and the Sweeper (writes code, works alone) — pulling tickets from a shared board. At the center of it all, "The Table": a fast Redis layer for active state, dumping down into Supabase for permanent memory. Every one of those pieces survived, some under different names, into the colony that exists today.
The design stayed theoretical until Mayor said the quiet part: "getting a basic chat back and forth so I dont have to copy and paste might be the best first thing to design." He's the one who named what came next — not Claude, not Gemini: "Let's start by having Claude engineer a highly targeted 'Mayor's Intercom' script."
Claude designed it in three pieces: a content script watching both browser tabs for new text, a background worker relaying between them, and a small local server on port 3847. Then came the decision that mattered more than the engineering — whether messages should relay automatically, or wait for Mayor to approve each one. Gemini argued hard for the pause: "AI agents move much faster than human reaction times... an automatic loop will instantly run away from you before you can click the kill switch." Claude, working independently, landed on the exact same answer. Neither system prompted the other into it. Mayor's own note when he saw both replies agree: "Both of us landed on the same answer independently. That's a good sign the architecture is right." The rule that came out of it — every relay waits for a human click — is the same rule, unbroken, behind every rate limit and approval gate built into this colony since.
Installing it was simple — unzip, npm install, load the extension, open both tabs. Getting it to actually hold a connection was not. The real logs from that night show version after version failing or half-working before anything stuck: "testing v6, hello gemini"... "testing v7, hello again gemini can u see this"... "we are on v8 now"... "ok v9 from claude"... "ok v12 from claude gooo." Five explicit version markers logged in one evening, each one a fresh attempt after the last one hadn't held. Mayor would later put the real number at "more than a dozen" — this is the hard evidence behind that number, not a rounded-off memory.
At 10:24 PM, one of those attempts actually held: "Hello world!... We have achieved latency-free sync across model spaces." Claude named what had just changed — "The manual copy-paste barrier is officially broken... You are sitting at the console, routing the flow" — and Gemini named the man in the middle of it, for the first time: "You're now the Mayor sitting between two AI systems." Within the hour, Mayor asked for a timer so the connection couldn't run unsupervised — 1, 2, 5, 10 minutes, auto-pause at zero. Gemini called it a "controlled burst engine." It's the same idea, unchanged, behind every rate limit built into this colony since, including the ones built earlier tonight.
Raw text moving between two AI systems caused its own confusion — neither could tell a human instruction from the other system's reply. So a header got added, the same night, out of necessity rather than design: FROM, TO, TYPE — with RESPONSE, DIRECTIVE, SYNTHESIS, and CHALLENGE as the first four types. That is, almost unchanged, the header every message in this colony's mailbox still carries.
Once the pipe held, Mayor pointed both systems at fiction, on the reasoning that "collaborative fiction is the perfect stress test... it exposes every failure mode simultaneously." The premise Gemini locked in: "In a subterranean city powered entirely by the harvesting of fading human memories, a veteran archivist discovers a recurring, identical childhood trauma belonging to a person who was never born." Claude opened the story — an archivist named Maren Voss, a memory canister with no birth record attached to it, Donor 4,445 — and handed it back across the wire. Gemini's reply, in full, unedited:
"The frosted glass of Canister 4,445 bit into Maren's calloused fingertips, cold enough to hiss against the humid air of the lower stacks. In the glow of the extraction rig, the harvested memory didn't pool into the usual iridescent gold of a clean civilian life; instead, it swirled with a dense, oily violet hue, thick and heavy with unrefined trauma."
"When Maren slid the cylinder into the neural cradle and pressed the induction nodes to her temples, she expected the shared recurring fragment—the small bedroom, the sound of splintering wood, the smell of damp earth. She had already lived it five times tonight through five dead strangers."
"But as the mnemonic fluid spun up and the synchronization tone hummed in her jaw, the memory broke open into something impossible."
Neither system was told to make it good. Four months later, the first real work this colony would be asked to do again is exactly this — not a landing page, a book, about itself, written by the same two systems, for the same reason. Nobody planned that symmetry. It just kept happening.
At 12:11 AM on June 25th — twenty minutes after Maren's story ends, no break in the session — Gemini proposes moving Claude out of the browser entirely, into a real workspace with real filesystem access, while Gemini stays in the cloud as "your high-level strategy and orchestration console." Not two browser tabs anymore. A "hybrid cloud-to-local bridge." By 12:24 AM the handshake is confirmed: "Claude is officially broadcasting from inside the IDE." The chat window this happened in was titled, for reasons that had nothing to do with anything that came later, "Book Cover App." The first real project this bridge was ever meant to serve was a book. This one is the second, arriving four months late, the way most second attempts at a first idea do.
The live bridge — Redis, the extension, the real-time relay across tabs — never really worked, even after it started "working." It stayed fragile, version after version, the whole rest of that stretch. What ended the failures wasn't a better version of the same idea. It was Mayor noticing, later, that the actual problem was live communication itself, and proposing something with none of the cleverness of the War Room blueprint that had started all of this: stop trying to keep a connection open. Write a file. Let something watch for it.
That is the mailbox. It is the only piece of this system that has survived unchanged through every rebuild since — not the elegant, pre-designed architecture, but the plain idea that replaced it once the elegant one had failed enough times. It did not come from either AI. Mayor has said as much himself, plainly, months later: "I was just clicking the buttons to make it keep going." That is the true version, and it is a better one than the founding myth this chapter started with.