Hot-load boundary
Route XML, service configuration, and service package assets can be adjusted within the runtime's route loading model. Java code, dependencies, Spring beans, and startup parameters remain rebuild or restart boundaries.
Runtime architecture
Service packages, Camel routes, and operational controls
The public architecture view focuses on delivery boundaries: what can be changed as route assets, what is controlled by configuration, and what requires a runtime rebuild or restart.
External systems
Call or publish
MES, WMS, ERP, HTTP clients, data platforms, AI tools, and operations systems enter through routes or APIs.
Control plane
Manage services
CLI and management APIs handle deploy, reload, diagnostics, service status, and bounded Action workflows.
Route runtime
Load packages
Camel XML routes run under service package conventions and can be hot-loaded within route boundaries.
Processors
Govern traffic
Validation, permissions, Action authorization, transformations, logging, AI tools, and robotics processors apply policy.
Adapters
Reach endpoints
HTTP, SQL, MQTT, OPC UA, Modbus, SAP, AVEVA, rosbridge, and gateway routes connect outward.
Governed Action boundary
A bounded task session pins the service, version, Action, policy digest, and exact file scope. Managed route apply requires the latest scope digest and fails closed on live-file drift; approval never replaces final authorization or execution checks.
Delivery boundary
The public repository is a delivery context. It contains the runnable package, examples, docs, skills, and website assets. It does not expose internal source implementation paths or development-only materials.