Robots don’t live in the cloud.
They live in basements. Elevators. Parking garages. Warehouses with dead zones. Places where “always online” is a nice story you tell in slide decks.
That’s why the edge autonomy budget matters for Fabric Foundation.
The chain can’t be in the control loop. If a robot needs to wait for confirmation before it brakes, turns, or avoids a person… congrats, you built a liability machine.
So the real design has to accept delayed truth. Local authority now. Verifiable settlement later.
The robot acts with local rules and tight permissions while it’s offline. It logs what it did. It signs what it can. Then when connectivity returns, the network verifies, settles payments, updates records, and applies consequences if something went off-policy.
That’s the overlooked part of “agent-native” infrastructure. Not how fast the chain is. How well the system handles being disconnected without turning verification into theater.
Because offline is not an edge case.
Offline is the default.
