Architecture

The frozen M0 architecture of GoMyRobotOS: the layered model, the partition contract and its IR, the backend model, the runtime and recovery models, and the frozen baseline.

• Architecture overview
  • The final architecture
  • The surrounding ecosystem
  • Backend matrix (summary)
  • Five core responsibilities
• Layered model
  • The layers
    • 1. Partition Contract
    • 2. IR (GoMyRobotOS Intermediate Representation)
    • 3. Target backend
    • 4. Runtime
    • 5. GoMyRobotRT and the workload
  • Invariant vs. target-specific
• The Partition Contract
  • The central innovation
  • Why this is the center of the architecture
  • Minimum conceptual fields
  • The hard rule: no backend syntax
  • Contract ≠ IR
  • Status
  • Example
• GoMyRobotOS IR (Intermediate Representation)
  • Purpose
  • Naming: contract vs IR
  • Shape
  • Guarantees the IR is responsible for
  • Status
• Backend model
  • The rule
  • A backend is a mapping, not a product
  • Initial backends and their status
  • Backend Capability Manifest
  • Bare-metal backends
  • What backends must never do
• Runtime model
  • Hosting the workload: GoMyRobotRT
  • The runtime responsibilities of GoMyRobotOS
  • Service domains (Linux)
• Recovery model
  • What a partition must do when something goes wrong
  • The detect → contain → recover → resume pipeline
  • The independence boundary (ADR-0011)
  • Recovery as assurance evidence
• Frozen baseline scope notes
  • Naming rule
  • Not in the v1 baseline
  • Platform position
  • Status