The Reasoning Agent interprets the goal. The World Model supplies shared spatial state and memory. Mission Orchestration coordinates permitted actions across the partner stack.
INTERACTIVE SCENARIO · SIMULATED
Example: P-204 cooling recovery. Simulated process measurements; proposed partner adapters. Run or step through the mission. Approval remains explicit.
Monitoring coolingrev 0World state ready18.0 L/min · 9.4 bar
Mission intake
Translate a business request into a bounded goal.
Domain workflows
Package an outcome, not a collection of devices.
World state, perception & reasoning
Interpret evidence and compare candidate actions.
Mission ownership
POLICY · APPROVAL · RECOVERY
Fleet & autonomy
Translate common skills into supported OEM actions.
Mission requests move down. Measurements and completion evidence return up. Partner boxes are proposed connections, not active vendor APIs.
PROPOSED PARTNERS
Clear roles. Replaceable interfaces.
Open a partner to inspect its role, public capability, proposed adapter and integration checks.
One mission owner. Not two.
Choose whether to own or integrate fleet scheduling. Keep asset identity, permission scope and outcome acceptance consistent across native platforms. A command acknowledgement is never the acceptance test.