Shared Robotics Project Models
Give robot definitions, programs, and learning workflows a consistent project representation.
Core Technology
Broxme Core
Broxme Core is the software foundation we’re developing around Studio’s internal project models, program execution, and simulation.
Core is in development. The components described here run inside the engineering build, with public interfaces still being defined.
Areas of Development
The pieces that connect a robotics project.
Studio saves robot definitions and programs together. Its runtime executes robot instructions against simulated state, and the debugger can record that state for inspection.
Command and Execution Workflows
Translate Studio’s supported programming workflows into a common intermediate representation for execution.
Simulation Integration
Connect project models to deterministic simulation so behavior can be inspected and reproduced.
Hardware Abstraction
Keep device interfaces separate from project semantics as supported transport and hardware paths are tested.
Extensibility and Compatibility
Develop understandable boundaries for extensions, project interchange, and integration.
Validation and Diagnostics
Make project errors, runtime behavior, and test results easier to inspect.
In Development
What still needs release validation.
Public API contracts and compatibility guidance are in development. Format interchange and hardware adapters need validation for each supported configuration.
Understandable interfaces
Make data contracts and error cases clear so tools can build on the same project model.
Interoperability
Use established formats where they fit, and document what changes when a project moves between tools.
Reliability
Design validation, diagnostics, and recovery into the software.
See what developers can explore.
Read about simulation, interfaces, and evidence for engineering workflows.