Operational Design Domain as a Living Artifact
Objective
Ensure the operational design domain (ODD) is maintained as a version-controlled specification with change-control, not a static one-time document.
Control / requirement
Changes to the ODD (geography, weather envelope, task scope) trigger a defined revalidation process before the change takes effect; ODD maintained with version history.
Applicability
All physical AI systems operating under a defined ODD.
Expected evidence
ODD version history; revalidation records tied to each ODD change. [T2]
Assurance expectation
Documentation review confirming every ODD change has a corresponding revalidation record — no undocumented scope changes.
Dependencies
PAI-SF-ENV-001 (Domain 12) — see Open Items: this boundary needs explicit reconciliation before publication, since ENV-001 owns the physical/environmental description this control authorizes changes to.
Exclusions
Does not apply where the ODD is fixed by regulation and cannot be organizationally changed.
Maturity / conformance relevance
Expected at Operational and High-Assurance levels; Foundational level expects at minimum a documented (if static) ODD.
Ecosystem relationship
Extends GAISSF™ change-management controls to the physical operating boundary. Provides ODD-change incident categories for UAIF™.