Encapsulation
Sibling branches at the same level never see each other’s sub-tasks. They meet only at the clip point, the connection layer. A robot is a whole and a part at once.
A robot is not a single entity you program. It is a reconfigurable multi-agent system, a holon, composed by mixing and matching agents on the platform. BASE is the holonic runtime that makes a whole fleet behave as one adaptive organisation, and keeps each robot working when the network is cut.
The hive is one sheet of compute. A fractal grows downward across it, missions into sub-missions into sub-tasks. Where a branch reaches a robot, it is drawn onto that robot and keeps growing inside it. The orchestration is not a picture over the fleet. It is the fleet.
Tap a robot to cut its link.
Sibling branches at the same level never see each other’s sub-tasks. They meet only at the clip point, the connection layer. A robot is a whole and a part at once.
Lift a robot and its branch detaches. The mission keeps running on the body, through the blackout, with no link to the hive.
Set the robot back and its branch clips in where it left off. No restart, no replay, no lost work. It rejoins the organisation mid-stride.
This is also the design razor. If the post-it physics cannot express it, we do not build it.
A robot is a body, the hard real-time motion hardware, and a soul, a BASE holon that drives it over a control plane we call the fieldlink. The fieldlink speaks the robot's own protocol, so swapping a simulated dog for a real one is a change of transport, not a change of mind.
Mission, world model, planner, safety arbiter. The thinking half. It does not change when the body does.
The dog carries its own BASE hive. Perception, navigation, power, comms, health and a safety arbiter reach consensus on the next move. The mission holon asks, the holons vote, and the safety holon holds a veto over the vote. A connector then marshals the agreed plan and hands it to the hard real-time controller, which BASE can request but never override.
Deliberate, vote, and keep the robot safe.
A manager that streams every motion to a robot is a single point of failure on the end of a radio link. BASE sends a goal, not a joystick. The robot decomposes it and runs it on its own, and it keeps going when the link drops. This is the fleet-manager and robot split that VDA5050 and Open-RMF standardised. We adopt it, then take it further: the robot is autonomous all the way down.
A constant command stream. The robot is a puppet. Cut the link and it stops where it stands.
A dispatched mission. The robot owns the plan, negotiates for help, and runs it through a blackout.
Industrial autonomy converged on two good ideas: a standard contract between planner and machine (VDA5050), and negotiated coordination of mixed fleets and shared infrastructure (Open-RMF). We do not reinvent them. We put a holonic payload inside the envelope they standardised.
Append to a running mission live. The body knows committed from speculative.
An out-of-band channel for estop, pause and cancel.
Capability self-description, aligned to the fieldlink device blueprint.
Versioned mission uploads that survive a lossy link.
Space-time deconfliction for rovers and quads sharing paths.
Airlocks, charging pads and relays become reservable holons.
Open-RMF already runs task auctions and composable tasks. VDA5050 already beats a raw JSON blob, with shared semantics and ordered, idempotent updates. The BASE difference is the shape of the market and where the intelligence lives, not that we have a market and they do not.
| Dimension | VDA5050 | Open-RMF | BASE |
|---|---|---|---|
| Unit of organisation | One vehicle | Fleets behind adapters, central core | Holons. Each resource is whole and part; heterogeneous bodies are peers. |
| Decomposition | None, flat order | Shallow and central | Recursive and fractal. Tasks become sub-tasks that are themselves holons, many levels deep. |
| Matching | Not applicable | Which fleet is configured for the task type | Capability-semantic, through the decomposition layer. |
| Coordination | The master | Central traffic schedule and dispatcher | Peer-to-peer negotiation. Missions run onboard through blackouts. |
| Autonomy | Smart master, dumb robot | Robot executes, the core plans | Edge-autonomous holons. Deliberation runs on the body. |
| Runtime | MQTT client | ROS 2 nodes and central databases | Erlang / OTP. Holons are supervised processes; the runtime is holonic, not just the diagram. |
The standards coordinate robots. BASE grows an organisation.
The same orchestration runs a simulated quadruped and a real one over the same control plane. If you are building a fleet that has to think at the edge, tell us what it looks like.