The first time I saw a “machine identity” system in the wild, it looked clean.
One robot. One ID. One neat record.
Then the robot left the demo.
It moved into the real world, where nothing lives in one place. A vendor cloud for updates. An enterprise stack for operations. A private chain for internal accounting. An L2 for payments. A partner’s system for compliance. Suddenly the robot didn’t have one identity.
It had five.
And the worst part is that all five were “valid.”
That’s the cross-network identity bridge problem that Fabric can’t dodge if its identity layer is going to matter. If machine identity is real, it can’t live in a silo. Robots will operate across environments by default. Not because anyone loves complexity, but because organizations do. Different chains. Different trust models. Different integrations. Different teams.
So the hard question becomes boring and sharp:
How does a robot prove it’s the same entity everywhere without spawning clones of itself?
Because portability without anti-duplication is just identity theater. If an identity can be copied, replayed, or re-minted across systems, then you don’t have a persistent entity. You have a costume.
And costumes don’t earn reputation. They don’t carry liability. They don’t support warranties. They don’t support insurance. They just create confusion when something breaks and everyone tries to map events back to “the real robot.”
This is where people wave their hands and say “bridges.”
But identity bridging isn’t just moving tokens. It’s moving trust. It’s saying: this robot on this chain is the same robot in that vendor cloud. The same robot in that warehouse system. The same robot that signed the maintenance record. The same robot that paid for charging last week.
That requires more than an ID number.
It requires a story that survives conflicting environments. A way to anchor the root identity, prove continuity, and make duplication expensive or impossible. A way to rotate keys without changing the entity. A way to revoke access when a unit is compromised without accidentally revoking the wrong “twin” on a different network. A way to handle resales and repairs without turning the robot into a Ship of Theseus that nobody can identify.
And yes, the alternative is what we already have.
Spreadsheets.
“Here’s the vendor serial.”
“Here’s the internal asset ID.”
“Here’s the blockchain address.”
“Here’s the ops dashboard record.”
“Here’s the insurance file number.”
Five IDs, one machine, and a human in the middle doing reconciliation work forever.
That’s not a machine economy. That’s an admin economy.
So when Fabric talks about identity as a foundation, this is the test I care about. Not whether identity exists on one ledger. Whether it can travel. Whether it can keep its shape across systems without splitting into duplicates. Whether “the robot” stays singular even as it moves through the messy stack of modern organizations.
Because the difference between a universal machine identity and a pile of incompatible identifiers isn’t philosophical.
It’s operational.
One becomes a base layer other people can build around.
The other becomes a spreadsheet you update right before the audit.