The Mothership Never Calls You

Ron Reynolds · 2026-09-05 · 4 min read

Second in the Federations of Federations series. Who calls whom sounds like plumbing. It's actually a statement about who works for whom.

Think about the relationship between a good shop and its wholesaler.

The shop calls in the morning: here's what I sold, here's what I need, anything for me? The wholesaler never phones the shop at 2am. Never sends someone around to check the back room. Never needs a key. The shop reaches out on its own schedule, does its business, hangs up. Everyone understands who owns the shop.

Every answer to "who connects to whom" on a network is a version of that question, and most platforms answer it badly: their machinery reaches into yours whenever it wants, and your IT setup — or your nephew who does your IT — has to hold the door open for it.

A ComOS node answers it the way the shop does. Your machine makes every call. Nothing ever calls in. How the call works

On a schedule you control, your machine calls the network and does four things in one short conversation.

It proves who it is — using a key that was created on your machine and has never left it, the way you'd recognize a voice rather than accept a business card. It mentions what version of the software it's running, so nobody has to come check. It shares its shop window — a compact summary of what your world currently offers, so the network can keep sending you customers. And it leaves a fingerprint of its own history — a tiny seal the network keeps, which later proves your records haven't been quietly rewritten, without the network ever holding the records themselves.

Then it collects whatever was waiting — an order from another business, a question only your world can answer — and hangs up.

No open line, and nothing for a hacker to knock on, because there is no door facing the street. If someone scans your network from outside, your ComOS machine simply isn't there. When a machine goes quiet

Machines lose power. Routers die. Someone unplugs the wrong cable before a long weekend.

A network that pretends this won't happen falls apart the first winter. So quiet has rules. A machine that stops calling in gets marked, then gently taken out of the shop window — the network stops steering new customers toward a store that may not answer — and after a long grace period, its membership lapses. When it comes back, it climbs back the same way it went down.

Two things about that ladder matter to an owner. Nobody gets a 2am phone call — a dark machine is priced in automatically, not paged about. And your own standing doesn't take the walk with your hardware: the machine has a clock that ticks in minutes, you have a reputation that moves on the scale of a business, and the two are kept deliberately separate. A dead box is an errand. It is not a mark against you. The honest cost

Because nothing calls in, work that's waiting for you waits until your next call. If your machine phones home every few minutes, an order from across the network can sit for a few minutes. Your box, your schedule — call more often when speed is worth it, less when it isn't.

Anyone who has run anything from a back room knows what that small delay buys: a machine that handles real money, with no door on the street side at all. A fleet with zero network engineering

A thousand worlds behind a thousand ordinary home routers, and not one port forwarded, not one firewall changed, not one IT consultant billed to "get the system talking." Every machine solved its own connectivity the day it first reached the internet, because reaching out is all it ever does.

Most systems like this die in a hallway conversation — the one where somebody says "I'll need to open up the network for it." This one never has that conversation. Plug it in where there's an outlet and a connection, and it starts calling home.