Skip to main content

​
Conformance classes

  • Core World — implements every MUST in the Core profile on the world side. [AWP-CNF-001]
  • Core Agent — implements every MUST in the Core profile on the agent side. [AWP-CNF-002]
  • Profile conformance — a Core-conformant implementation additionally satisfying all MUSTs of a named profile. Claims are per-profile (e.g. “Core World + sim + robotics (no force monitoring)”). [AWP-CNF-003]

​
Requirement mapping

Every requirement ID has a row in the requirement matrix giving its side (world / agent / both), applicability (all / lockstep / streaming), feature gate (profile or capability key), and the assertion that tests it — or manual / untestable with the reason. Each MUST/MUST NOT maps to at least one assertion in the conformance suite; assertions are named after requirement IDs. SHOULD items generate warnings, not failures. The matrix is generated from spec/requirements.yaml and CI fails if a bracketed ID in the specification is missing from it. [AWP-CNF-004]

​
Claiming conformance

Implementations MUST NOT claim “AWP-conformant” without passing the current suite for the claimed classes; while the suite is unpublished, any claim MUST be labelled “self-assessed against v0.1 draft”. “AWP-compatible” carries no normative meaning. [AWP-CNF-005] See badges.

​
Experimental profiles

Profiles whose requirements depend on physical measurement — robotics in v0.1 — are experimental: no validated hardware harness exists, so their conformance cannot yet be established by the suite. Claims for experimental profiles MUST carry the word “experimental” and attach the evidence required by AWP-ROB-004. A profile leaves experimental status by RFD once a harness has validated at least two independent implementations. [AWP-CNF-006]