robotics-acceptance-harness Quality Declaration

This document follows REP-2004. The package currently claims Quality Level 4.

Version Policy

The package uses Semantic Versioning and is currently pre-1.0.0. It therefore does not claim the stable-version requirement of REP-2004 Quality Level 3. Public interfaces and compatibility rules are listed in Compatibility Policy. The package manifest defines the contracts dependency; the changelog records release changes.

Change Control

Changes are reviewed through pull requests. CI runs tests, coverage, Ruff, mypy, repository hooks, package builds, and installed-wheel checks.

Documentation and License

README documents each CLI mode and pytest integration. The repository is licensed under MIT; copyright and authorship are recorded in LICENSE and package metadata.

Testing

Unit and integration tests cover document validation, graph readiness, timing, authorization, evidence, aggregation, and trace evaluation. CI enforces branch coverage of at least 80 percent. Ruff, mypy strict mode, Semgrep, actionlint, YAML linting, and Markdown linting are required checks.

Dependencies

Runtime dependencies are junitparser, opentelemetry-proto, packaging, and robotics-runtime-contracts. Live ROS observation uses the observer runtime environment instead of declaring ROS packages as Python dependencies. Both packages share the root lockfile for development. Release archive installs use the exact published contracts version outside the workspace; editable source fixtures provide a separate integration check.

Platform Support

CI tests document-only commands on Linux with Python 3.12 through 3.14. A separate Linux job exercises live observation with real ROS 2 Jazzy and an OpenTelemetry Collector, including a lifecycle transition during measurement. These fixtures do not qualify every robot, hardware provider, or REP-2000 Tier 1 platform, which is another reason not to claim Quality Level 3. This declaration keeps package quality separate from execution qualification. Source changes and separately qualified plugin hosts do not expand the quality claim of an immutable package release.

Security

Vulnerability reporting and the observer trust boundary are documented in SECURITY.md.