Logo
  • Getting started
  • Concepts
  • Architecture
  • Ecosystem components
  • Partition Contract
  • Platforms
  • Backends
  • Validation
    • Validation Methodology
    • Validation: Temporal isolation
    • Validation: Spatial isolation
    • Validation: Interference
    • Validation: Fault injection
    • Validation: Recovery
  • Assurance
  • Research
  • Milestones
  • Compatibility
  • Development
GoMyRobotOS
  • Validation
  • Edit on GitHub

Validation

How the GoMyRobotOS isolation properties are validated: the methodology and the knowledge coverage across temporal isolation, spatial isolation, interference, fault injection, and recovery.

  • Validation Methodology
    • First rule: what validation is and is not
    • The declared validation areas
    • How the results feed the rest of the ecosystem
    • Ladder of where validation runs
  • Validation: Temporal isolation
    • What “temporal isolation” means here
    • What gets measured
    • Experimental plan (research, not implemented)
    • Status
  • Validation: Spatial isolation
    • What “spatial isolation” means here
    • The isolation invariants (per contract field)
    • How the invariants are tested
    • Status
  • Validation: Interference
    • The question
    • The experimental design
    • Measured quantities
    • Status
  • Validation: Fault injection
    • The boundary, stated again
    • The fault classes validated against a contract
    • What each validation run produces
    • Radiation: the honesty rule
    • Space fault responsibility split
    • Status
  • Validation: Recovery
    • The pipeline under test
    • The fault classes exercised
    • What “passing” means
    • Status
Previous Next

© Copyright 2026, The GoMyRobotOS Authors.

Built with Sphinx using a theme provided by Read the Docs.