Concepts

The fundamental ideas that the GoMyRobotOS architecture and Partition Contract are built on: partitions, isolation, the execution model, and how assurance is argued.

• Concepts overview
  • The core definition
  • Key terms
  • Architecture in one diagram
  • What GoMyRobotOS is and is not
  • Reading order
• Architecture principles
  • 1. Describe the semantics once; realize them per target
  • 2. The hypervisor is a backend, not the abstraction
  • 3. The contract contains intent and constraints, not backend syntax
  • 4. The product stays a platform, not an “everything safety” monolith
  • 5. The robotics workload stays a workload
  • 6. Recovery must be independent of the domain it recovers
  • 7. Targets are honestly staged
  • 8. Evidence, not assertions
  • 9. The documentation is versioned with the software
• Partitioning
  • What a partition is
  • Why partition, and not process / container / VM
  • A mixed-criticality system is a set of partitions
  • Partition and partition contract: the distinction
• Isolation
  • Isolation dimensions in the contract
  • What GoMyRobotOS specifies vs. what a backend realizes
  • Isolation and assurance
• Execution model
  • The realization pipeline
  • What “execution” means per partition
  • Runtime integration
  • Non-partition execution
• Assurance positioning
  • The boundary
  • What GoMyRobotOS contributes to an assurance argument
  • What GoMyRobotOS explicitly does not claim
  • Why the boundary exists