====== Version-Controlled Condition ====== [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] ===== Discussion ===== A version-controlled condition is one in which artifacts are uniquely identified and managed through explicit version identifiers and change control mechanisms. Version-controlled conditions support traceability, reproducibility, auditability, controlled evolution, and conformance evaluation within the [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]]. A version-controlled condition differs from an informal change state. An informal change state lacks governed identification, versioning, and change control. A version-controlled condition establishes the controlled state of an artifact for review, use, comparison, release, or evaluation. ===== Definition ===== //state in which artifacts are uniquely identified and managed through explicit version identifiers and change control mechanisms// ===== Source ===== Structured Information Processing [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]] ===== Note ===== A version-controlled condition provides a controlled basis for determining which artifact version applies in a governed architectural, semantic, structural, or conformance context. ===== Example ===== A [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic_artefact]], [[dido:99_annexes:annex-b-terms-and-definitions:s:structural_artefact]], [[dido:99_annexes:annex-b-terms-and-definitions:i:interface_contract]], or [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretive_artefact]] is in a version-controlled condition when it has an explicit version identifier, approved change history, and governed release status. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.