Platform: x86-64

Role: development and reference platform. Status: Development / Reference as a platform role; the Xen realization of it is Planned (M1).

x86-64 is primarily a development and reproducibility platform, not the intended flight processor. It is where the GoMyRobotOS software architecture is developed before moving to space targets, and where the CI-based reproducibility story lives:

  • fast iteration

  • CI

  • automated tests

  • QEMU virtualization

  • fault-injection experiments

  • backend development

  • reproducible regression tests

Realization path

Partition Contract
      → IR
      → Xen backend
      → Linux / RTEMS guests
      → (flight partition) GoMyRobotRT

This roadmap is what M1 ships: parser, validator, IR, the Xen backend, boot/deployment, and basic partition monitoring, with reproducible boot, CPU allocation, memory isolation, communication, and basic fault containment as test goals (M1).

What x86-64 is used for and not for

Used for

Not used for

backend development and CI

flight timing claims

QEMU-based reproducible experiments

hardware interference science

early fault-injection experiments

radiation qualification evidence

Warning

A measurement on x86-64 is evidence about mechanisms and tooling, not evidence about flight hardware. The M3 interference laboratory repeats measurements on NG-ULTRA and HPSC precisely for this reason, see Interference.

Plans for this platform in the milestones

  • M1, reference partition boots and isolates (gate)

  • M3, GMR-INTERF v1 first runs here

  • M6, remains one of the (at least two) heterogeneous target realizations demonstrating the ServiceReady proof