Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
Robotics runtime
Robotics runtime
  • Integrate an assistant with testing and evidence
  • Architecture
  • Architecture diagrams
  • CI executors
  • Optional external Test API
  • First result with the published Python tools
  • Architecture and implementation references
  • Releasing workspace packages
  • Published schema compatibility
  • Inspect results and native recordings
  • Robotics runtime host
  • Offline MCP tools
  • Robotics Runtime Contracts
    • Changelog
    • Compatibility Policy
    • Contributing
    • Robotics Runtime Contracts Quality Declaration
    • Security Policy
    • Supply-Chain Assurance
    • Consumer Examples
      • Flight controller interface profile
      • Native archive example
      • Published CLI consumer inputs
    • Assessment controls and archive result versions
    • Architecture Decisions
      • Keep One Canonical Contract Set Before 1.0
      • Validate Domain Extensions Offline
      • Separate Structural and Semantic Validation
      • Keep Device and Workload Identities Distinct
      • Keep the Package Domain Neutral
      • Separate Transport Qualification from Acceptance Aggregation
      • Preserve Published Schema Compatibility
      • Test the Declared Python Support Range
      • Preserve Deterministic JSON and Exact Byte Bindings
      • Keep a Narrow jsonschema Resolver Adapter
      • Retain the Pinned Ruff Budget Parser
    • Migrating from 0.15 to 0.16
    • Product artifact roles
    • Qualification validation
    • Core schema generation
    • Published schema compatibility gate
    • Document writers
  • Robotics Acceptance Harness
    • Changelog
    • Contributing
    • robotics-acceptance-harness Quality Declaration
    • Security Policy
    • Archive assessment
    • Compatibility
    • Architecture Decisions
      • Runtime Owns the Execution Environment
      • Aggregate Per-Domain Results
      • Consume Qualified Accelerator Evidence
      • Separate Permit and Workload Identities
    • Finite evaluator JSON
    • Evaluator authentication
    • Local evidence and observation timestamps
    • Live ROS 2 Jazzy integration tests
    • Standard-library helpers
    • Supply-Chain Assurance
  • Function complexity budgets
Back to top
Made with Sphinx and @pradyunsg's Furo