Where a decision becomes an action.
All capabilities · Early build
Most coordination software stops at the edge of the screen. The work a community depends on continues past it: things get built, moved, inspected, grown, repaired, and secured. This plane owns the seam where a digital decision becomes a physical action and a physical event becomes a durable record.
A mission is authorized
Move this part to inspection.cell · finishing-3
The record comes back
Placed and measured.event · mission.completed
The seam
A protocol surface, not a driver collection
Machines, robots, cameras, sensors, and gateways are addressed through a stated contract for capability, state, command, and telemetry. Vendor specifics stop at an adapter, which is what keeps the platform from becoming a catalog of one manufacturer's assumptions.
Cells and missions
Work is expressed as a mission given to a cell of cooperating equipment, with preconditions, steps, exceptions, and completion criteria. This is the unit a person authorizes and the unit the record describes.
An edge that keeps working
Local execution continues when the link to the center is gone, and reconciles afterward. Autonomy at the edge is a reliability property, and it is also what stops a network outage from becoming a safety event.
Observation returns as record
What the equipment did, saw, measured, and refused comes back as events on the same backbone as everything else, which is how physical work becomes auditable alongside digital work.
Simulation before deployment
Behavior is exercised against a modeled environment before it reaches hardware. Simulation is not a demonstration tool here, it is the cheap place to be wrong, and it is what makes the expensive place safer.
Safety stays where it belongs
The platform can request, authorize, sequence, and record physical action. It does not become the safety authority for a machine. Interlocks, limits, and emergency behavior remain with the equipment and the domain runtime that owns it, because a coordination layer that could override them would be a coordination layer that must never fail.
Why a community should care
Physical automation is usually sold as a closed system: one vendor's machines, one vendor's controller, one vendor's cloud, and a decade of dependence. Applying the same contracts, identity, policy, and audit rules used everywhere else turns it into a capability the community owns rather than a facility somebody operates on its behalf.