Development

How to contribute to the GoMyRobotOS documentation and code: contributing guidelines, testing practice, the Architecture Decision Records, and the change history.

• Contributing to GoMyRobotOS
  • Development flow
  • Non-negotiable documentation rules
  • Status labels: the vocabulary
  • Forbidden conversions (anti-hallucination)
  • ROS 2 rules
  • Architecture decisions (ADRs)
  • Milestones
  • Page discipline
  • Code conventions
  • Reporting problems
  • License
• Testing (project)
  • What is tested today (M0)
  • Declared test areas (from the validation section)
  • Ladder
  • Tooling policy
• Architecture Decisions
  • Index
    • ADR-0001 GoMyRobotOS is a partition and execution platform
    • ADR-0002 Partition Contract is the central abstraction
    • ADR-0003 Hypervisors are target-specific backends
    • ADR-0004 x86-64 is the initial development/reference platform
    • ADR-0005 NG-ULTRA is the primary flight-oriented reference
    • ADR-0006 HPSC is the initial RISC-V research target
    • ADR-0007 GoMyRobotRT is separate from GoMyRobotOS
    • ADR-0008 ROS 2 Rolling is the primary ROS 2 documentation reference
    • ADR-0009 GoMyRobotBSP owns target build and image realization
    • ADR-0010 Fault and radiation modeling belongs outside GoMyRobotOS
    • ADR-0011 GoMyRobotGuard must be independent of the failure domain it recovers
    • ADR-0012 Verification and assurance are external platform services
    • ADR-0013 Documentation is versioned with the software
    • ADR-0014 IPC is described by channel class, not transport mechanism
    • ADR-0015 Backends publish a capability manifest; no silent semantic downgrade
    • ADR-0016 Guard independence is staged (0 / 1 / 2)
    • ADR-0017 WCET claims carry an evidence class
    • ADR-0018 The documentation site is the architecture source of truth
  • Supersession log
• Architecture v2 (working draft), superseded for the M0 baseline
• Changelog
  • [Unreleased]
    • Added
    • Changed
    • Fixed