dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-005:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-005:start [2026/07/11 12:57] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-01:p1-req-13-10-005:start to dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-005:start nick_didodido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-005:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== P1-REQ-13-10-005 ====== ====== P1-REQ-13-10-005 ======
  
-[[dido:99_annexes:annex-c-requirements:part-01:start|Return to Part 1 Requirements]]+[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
  
 ===== Statement ===== ===== Statement =====
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-Deployment decisions belong to operational realisation. They describe where, how, and under which conditions implementation artefacts execute, connect, scale, observe, secure, or recover. Deployment decisions do not define conceptual architecture meaning.+Deployment decisions belong to operational realization. They describe where, how, and under which conditions implementation artifacts execute, connect, scale, observe, secure, or recover. Deployment decisions do not define conceptual architecture meaning.
  
 This requirement prevents deployment arrangements from altering conceptual elements inherited from Part 1. It preserves conceptual stability across local development, test, regulated production, sovereign infrastructure, and restricted environments. This requirement prevents deployment arrangements from altering conceptual elements inherited from Part 1. It preserves conceptual stability across local development, test, regulated production, sovereign infrastructure, and restricted environments.
Line 40: Line 40:
   * Deployment decisions appear as deployment concerns   * Deployment decisions appear as deployment concerns
   * Conceptual elements retain Part 1 definitions   * Conceptual elements retain Part 1 definitions
-  * Deployment artefacts trace to the implementation artefacts they deploy or configure+  * Deployment artifacts trace to the implementation artifacts they deploy or configure
   * Environment-specific arrangements do not replace conceptual definitions   * Environment-specific arrangements do not replace conceptual definitions
  
Line 51: Line 51:
 Related requirement identifiers: Related requirement identifiers:
  
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-10-003:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-003:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-10-006:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-006:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-10-008:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-008:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-2-004:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-004:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-7-004:start]]+  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-004:start]]
  
 ===== Status ===== ===== Status =====
  • dido/99_annexes/annex-d-requirements/part-01/p1-req-13-10-005/start.1783799866.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido