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] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:g:governance_constraint to dido:99_annexes:annex-b-terms-and-definitions:g:governance_constraint 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 1: / Line 1: @@
 ====== Governance Constraint ======
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 ===== 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:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]].
+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]].
 ===== Definition =====
@@ Line 17: / Line 17: @@
 ===== Source =====
-Structured Information Processing [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]]
+Structured Information Processing [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]]
 ===== 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 =====
-A governance constraint requires approved authority review before a [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:semantic_artifact]], [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:structural_artifact]], [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:c:conformance_point]], or [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:a:attachment_point]] changes.
+A governance constraint requires approved authority review before a [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:semantic_artifact]], [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:structural_artifact]], [[dido:99_annexes:annex-b-terms-and-definitions:c:conformance_point]], or [[dido:99_annexes:annex-b-terms-and-definitions:a:attachment_point]] changes.
 ----