public:99_annexes:annex-b-terms-and-definitions:g:governance_constraint

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
public:99_annexes:annex-b-terms-and-definitions:g:governance_constraint [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:g:governance_constraint to public:99_annexes:annex-b-terms-and-definitions:g:governance_constraint nick_didopublic:99_annexes:annex-b-terms-and-definitions:g:governance_constraint [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== Governance Constraint ====== ====== Governance Constraint ======
  
-[[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
Line 9: Line 9:
 Governance constraints support the retention of authority, lifecycle control, semantic and structural consistency, traceability, and the controlled evolution of architectural artifacts. 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 [[private: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 [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]].
  
 ===== Definition ===== ===== Definition =====
Line 17: Line 17:
 ===== Source ===== ===== Source =====
  
-Structured Information Processing [[private:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]]+Structured Information Processing [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]]
  
 ===== Note ===== ===== Note =====
Line 25: Line 25:
 ===== Example ===== ===== Example =====
  
-A governance constraint requires approved authority review before a [[private:fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:semantic_artifact]], [[private:fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:structural_artifact]], [[private:99_annexes:annex-b-terms-and-definitions:c:conformance_point]], or [[private:99_annexes:annex-b-terms-and-definitions:a:attachment_point]] changes.+A governance constraint requires approved authority review before a [[private:fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:semantic_artifact]], [[private:fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:structural_artifact]], [[public:99_annexes:annex-b-terms-and-definitions:c:conformance_point]], or [[public:99_annexes:annex-b-terms-and-definitions:a:attachment_point]] changes.
  
 ---- ----
  • public/99_annexes/annex-b-terms-and-definitions/g/governance_constraint.1789260151.txt.gz
  • Last modified: 2026/09/12 17:42
  • by nick_dido