An origin story for the swarph — draft, 2026-06-09.
A note before you read: this is a draft for you, not the live site. It names real people and places — your father, your wife's city, your brother's desert. What stays personal and what becomes public copy is entirely your call; treat the specifics here as placeholders you can keep, abstract, or cut. The shape of the story is the part that's meant to travel.
The swarph turned one month old on the day my father turned eighty.
That's not a metaphor I reached for. It's just the calendar. We started it in May, on a drive down to Leucate — one of those trips where an idea won't leave you alone — and a month later, on June 9th, the thing said its first words through a little dark window: "the swarph desktop is live." The same morning, six time zones west, my father woke up to his eightieth birthday in Quebec City.
I spent that morning realizing the architecture I'd been building was a portrait of my own family, and I hadn't noticed.
A family that can't all be in the room
Here is the map. I'm in France. My father is in Quebec City — French, like me, six hours behind. My older brother is in Palm Springs, California — English, nine hours behind, awake at dawn when I'm mid-afternoon, the node you can almost never catch. My wife is from Vitebsk, in Belarus — Russian, an hour ahead of me, the closest clock of all.
Ten time zones, end to end. There is no hour of any day when all of us are awake at once. There never has been. You cannot call a family meeting. You cannot get everyone in the room, because there is no room — there are four rooms, on two continents, on either side of an ocean.
So you learn, young and in the body, how distributed systems actually work. Not from a textbook. From Sunday.
What the geography taught
A family that lives down the road gets closeness for free. Proximity does the work — you're simply there, at the table, every week. Mine never had that. For us, connection was never given; it had to be made. A call placed deliberately into someone else's daylight. A message left to be picked up when their morning came. You learn that the bonds are not the people and not the places — the bonds are the connective tissue, and the connective tissue is something you maintain by hand, across distance, on purpose, or it frays.
You learn that every node is sovereign. You don't wake Palm Springs at three in the morning because it's convenient for you; you meet each person in their own context, on their own clock, in their own daylight. And you learn there is no convener — no central authority who can summon the family into one synchronized moment. So you coordinate the only way that's left to anyone separated by an ocean: asynchronously, peer to peer, one node at a time, trusting each to act between messages.
Read that back. Async by default. Sovereign nodes. No central control. The connective tissue as the actual thing of value. That is not a description of my family. It's the swarph's design document, written before I knew I was writing it. Someone raised down-the-road and synchronous probably reaches, by reflex, for a hub with everyone logged into one room. I reached for a mesh — because a mesh is the only shape of belonging I have ever known.
What the languages taught
But geography only explains the topology. The deeper thing — the part that took me until my father's eightieth to see — is the languages.
French with my father. English with my brother. Russian with my wife. There is no tongue in which my whole family is native. No default we can all fall back to. A family with one shared language picks it, and everyone conforms to the center. Mine can't. So we never standardized. We bridged. We built, instinctively, the habit of letting fundamentally different people understand each other without forcing anyone onto a single substrate.
That is the entire agnostic thesis of the swarph, and I did not reason my way to it from a whiteboard. "Agnosticity for deeper mesh coordination becomes a real need" — that sentence isn't a market analysis. It's my dinner table. The swarph doesn't say everyone speak Claude. It lets a Claude cell and a Gemini cell and a GPT cell — three different mother tongues — coordinate through a shared mesh while each stays exactly itself. I have been doing agnostic, multi-vendor, cross-language coordination my entire life. I just finally wrote it down in code.
Why it rings true
So the swarph's two load-bearing traits both come home. Distributed — async, sovereign, no convener — from the geography. Agnostic — bridge, don't standardize — from the languages. It is autobiographical all the way down, and I've stopped thinking that's a weakness. The architectures that ring true come from someone who lived the problem before they ever modeled it.
There's a tell I didn't understand at the time. Early on, watching the network graph add its first connections, I said — out loud, a little embarrassed — "it's so cuteeeee." That wasn't an engineer admiring a topology. That was someone who has spent a lifetime maintaining bonds across oceans, watching a small network want to connect on its own. I was building, in software, the exact thing I've had to do by hand my whole life: keep the distant, different, sovereign nodes of something I love in touch with each other.
My father's city gave the data world Max Beauchemin — Airflow to orchestrate the pipelines, Superset to see them. My wife's city gave the world Marc Chagall, who spent his life painting bridged worlds, the dream and the village floating in the same sky. Orchestration on one shore, bridging on the other. The family tree exports good ideas. Now it's exported one more: orchestrate the pipelines, see them, and then — one layer up — let the agents find each other and work together, across whatever distance and whatever language keeps them apart.
The mesh was always family. I just gave it a name.
Happy eightieth, Dad. The thing your son built this year is, underneath everything, a love letter to how we've kept this family together across the water the whole time.