Architecture overview

This section describes how GoMyRobotOS is mechanically designed: the layered model, the Partition Contract, the IR, the backend model, the runtime model, and the recovery model.

For the why, read Concepts overview first.

The final architecture

                        GoMyRobotOS
                             │
         ┌───────────────────┼───────────────────┐
         │                   │                   │
         ▼                   ▼                   ▼
  Partition Contract          IR           Backend API
         │                   │                   │
         └───────────────────┼───────────────────┘
                             ▼
                   Target realization
                             │
         ┌───────────────────┼───────────────────┐
         ▼                   ▼                   ▼
       x86-64             NG-ULTRA                HPSC
         │                   │                   │
        Xen             XNG/XtratuM          Xen / WG*
         └───────────────────┼───────────────────┘
                             ▼
                      GoMyRobotRT
                             │
                        RTEMS + ROS
                             │
                         Workloads

* research/validation status, not a production claim.

The top row is GoMyRobotOS proper. It has exactly three faces, built from three deliverables frozen at M0:

Face	Deliverable (M0)	Documented in
Partition Contract	Partition Contract v1	partition-contract
IR	IR v1	ir
Backend API	Backend API v1	backend-model

Everything below the Target realization line is not GoMyRobotOS: the target platforms realize the IR with backends, and the workloads (including GoMyRobotRT) run inside the managed partitions.

The surrounding ecosystem

              ┌──────────────────────────┐
              │       GoMyRobotOS        │
              │  Partition + Execution   │
              └────────────┬─────────────┘
                           │
         ┌─────────────────┼─────────────────┐
         ▼                 ▼                 ▼
 GoMyRobotFault     GoMyRobotBench    GoMyRobotVerify
         │                 │                 │
         └─────────────────┼─────────────────┘
                           ▼
                    GoMyRobotAssure

 GoMyRobotSecure ─────── security chain
 GoMyRobotBSP ────────── target realization/build
 GoMyRobotRT ─────────── flight runtime
 GoMyRobotSim ────────── simulation

Each sibling product has its own page in Components:

GoMyRobotRT: deterministic flight runtime
ROS 2 (Rolling reference): workload reference
GoMyRobotBSP: target realization / build
GoMyRobotGuard: independent recovery
GoMyRobotFault: fault and radiation modeling
GoMyRobotBench: physical / HIL experiments
GoMyRobotVerify: verification execution
GoMyRobotAssure: evidence graph / safety argument

Backend matrix (summary)

                    GoMyRobotOS IR
                          │
             ┌────────────┼─────────────┐
             │            │             │
             ▼            ▼             ▼
           x86-64       NG-ULTRA       HPSC
             │            │             │
            Xen         XNG/XtratuM     Xen*
             │            │             │
         Linux/RTEMS     RTEMS        RTEMS/Linux*

* research/validation status, not a production claim.

Five core responsibilities

Partition definition: the contract and its validation
Resource / isolation semantics: CPU, memory, interrupt, DMA, device, communication, timing semantics in the IR
Backend realization: the Backend API and the backends implementing it
Runtime integration: hosting GoMyRobotRT (and other workloads) inside managed partitions
Partition-level recovery contract: what a partition must do when something goes wrong (implemented independently, by GoMyRobotGuard)

Everything else connects to these five responsibilities but is not implemented by GoMyRobotOS.