Command Router
Route every inbound command to the correct handler.
Design: ApprovedExplore the six runtime layers behind BOS Core, from the first request to a governed action. Follow each module into its responsibilities, components, and design decisions.
The Platform overview describes five business capabilities. This architecture shows the six engineering layers that support them.
Design approval is separate from delivery. Thirty software modules are approved; Robotics/IoT remains draft and deferred. Approval does not mean the runtime is built, deployed, or production-validated.
Public architecture overview
Public overviewArchitecture source review date: 2026-09-07. Technical details require registration.
Where work arrives and gets coordinated: requests come in, and multi-step work is sequenced and timed.
Route every inbound command to the correct handler.
Design: ApprovedCarry commands and events across the runtime on a single bus, under the delivery contract each message class requires.
Design: ApprovedMaintain the lifecycle and context of every active BOS session.
Design: ApprovedDetermine when work runs and release it at the right time.
Design: ApprovedCoordinate multi-step work across the runtime and hold the state of every run.
Design: ApprovedWhere the runtime works out what to do: goals, business rules, context, and the decision itself.
Provide inference, prediction, and language understanding to the runtime, and propose calibrations from evaluated outcomes.
Design: ApprovedAssemble relevant context for requests and decisions, and surface what deserves notice unprompted.
Design: ApprovedSelect the course of action from the available options and evidence.
Design: ApprovedHold the goals of the runtime, rank them against each other, and produce the plans that pursue them.
Design: ApprovedEvaluate the deterministic business rules the business itself sets.
Design: ApprovedWhere decisions become actions in the outside world.
Carry out the individual actions the runtime commits to.
Design: ApprovedConnect the runtime to external systems and services.
Design: ApprovedCommand and monitor physical devices and robotic systems.
Design: DraftExecute scripts and code safely inside the runtime.
Design: ApprovedExecute the steps of a defined workflow.
Design: ApprovedWhat the runtime knows and remembers.
Serve frequently used data quickly and reduce load on the source stores.
Design: ApprovedRepresent the entities of the business and the relationships between them.
Design: ApprovedDescribe what data exists, where it lives, and what it means.
Design: ApprovedPersist the runtime's operational data durably and consistently.
Design: ApprovedStore and retrieve embeddings for similarity search.
Design: ApprovedThe limits on autonomous action, and the record of what was done.
Record an immutable account of what the runtime did.
Design: ApprovedEstablish who is acting and what they are permitted to do.
Design: ApprovedProtect sensitive data at rest, in transit, and in use.
Design: ApprovedEnsure runtime activity conforms to regulatory and organizational obligation.
Design: ApprovedKeep autonomous action within safe and acceptable risk limits.
Design: ApprovedThe platform everything else runs on.
Ensure the runtime and its data can be restored after loss.
Design: ApprovedBuild, test, and deliver runtime changes to their environments.
Design: ApprovedPackage and run every runtime component in an isolated, reproducible container.
Design: ApprovedShow how the runtime is behaving, so engineers can diagnose it.
Design: ApprovedMatch runtime capacity to demand.
Design: ApprovedMove traffic between runtime components and secure it in transit.
Design: Approved