Identity Survives Hardware

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

Eighth in the Federations of Federations series. You are not your box. Everything in this piece follows from that sentence.

Every scheme ever devised for tying software to hardware made the same bet: chain the value to the machine, and the machine becomes the leash.

Dongles. Licenses married to a serial number. Activation servers that outlived the companies that ran them. And every one of those schemes aged the same way — the machine died, and the customer stood holding a corpse with their purchase locked inside it, spending a week on the phone proving they own what they already paid for. If you've ever migrated a point-of-sale system, or begged a vendor to release a license from a dead laptop, you know the feeling exactly: somewhere along the way, you became the accessory, and the box became the customer.

ComOS runs the bet in reverse. You are the identity. The box is an accessory. Three things, deliberately kept separate

In this network, three things that other systems tangle together are kept distinct on purpose.

You — the owner, with a standing earned over time: your history, your reputation, your place in the network. All of it lives in the network's memory, none of it on any machine.

The machine — which has its own identity, its own credentials, created on the machine itself the day it joins and never copied anywhere. Named under you, working for you, but never confused with you.

The business — your world of customers, catalog, and history, which belongs to your ownership, and merely resides on the machine, the way a shop resides in a building without being the building.

Keep those three separate and every hardware disaster becomes survivable, because no disaster can touch more than one of them. The credentials never leave home

When your machine joins the network, it mints its own key, on its own silicon — and that key never travels. Proving itself to the network works like recognizing a voice, never like mailing a copy of one: the network poses a fresh, one-time challenge, and the machine answers in a way only the real keyholder can. The moment of joining is itself written into the network's permanent record — a birth certificate that can't be quietly backdated or forged.

On modern Apple machines the key can live in the hardware vault, where copying it out isn't a matter of skill — the machine simply offers no such operation. Pair that with the encrypted disk the installation insists on, and a stolen machine is a brick that knows nothing and can prove nothing. Killing a machine never touches its owner

Now the part every licensing scheme got backwards.

Report a machine lost or stolen, and the network revokes the machine — its key dies, its calls stop being answered, its listings come out of the shop window. And you, the owner? Untouched. Your standing doesn't dip. Your history doesn't blink. Your world restores onto a new machine, which mints its own new key and takes its place. The network holds two clocks on purpose — a machine's heartbeat ticks in minutes, an owner's reputation moves at the pace of a business — and one never winds the other.

One more decision that tells you where our priorities sit: revoking a stolen machine's key is free. Always. Charging a theft victim for the privilege of protecting themselves would be a toll on doing the right thing, and tolls on doing the right thing teach people to do the wrong one. Machines become tires

Owners here treat machines the way a delivery fleet treats tires. Boxes die, get upgraded, get left behind in office moves, occasionally get stolen — and each of those events is an errand rather than an identity crisis. No license transfers, no week on the phone proving you're you. Replace the box, and continue.

Every hardware-bound scheme made the machine precious and the customer fragile. Binding value to identity makes the customer durable and the machine boring — and boring is exactly what good infrastructure feels like.