Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:g:governance_constraint [2026/07/11 11:14] – ↷ Links adapted because of a move operation nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:g:governance_constraint [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 5: / Line 5: @@
 ===== Discussion =====
-A governance constraint identifies a rule or control mechanism governing the definition, modification, versioning, or authority over architectural artefacts.
+A governance constraint identifies a rule or control mechanism governing the definition, modification, versioning, or authority over architectural artifacts.
-Governance constraints support the retention of authority, lifecycle control, semantic and structural consistency, traceability, and the controlled evolution of architectural artefacts.
+Governance constraints support the retention of authority, lifecycle control, semantic and structural consistency, traceability, and the controlled evolution of architectural artifacts.
 A governance constraint differs from an implementation constraint. An implementation constraint is a limit or condition imposed by a selected technology, product, language, runtime, or deployment environment. A governance constraint defines control over architectural meaning, structure, lifecycle, and authority within the [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]].
@@ Line 21: / Line 21: @@
 ===== Note =====
-A governance constraint preserves controlled meaning, structure, lifecycle, and authority for architectural artefacts.
+A governance constraint preserves controlled meaning, structure, lifecycle, and authority for architectural artifacts.
 ===== Example =====