Differences

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

--- dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-004:start [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-004:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+====== P1-REQ-13-2-004 ======
+[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
+===== Statement =====
+The Conceptual Architecture SHALL NOT allow deployment artifacts to redefine conceptual elements.
+===== Source =====
+Part 1, Section 13.2: Conceptual Separation Requirements.
+===== Rationale =====
+Deployment artifacts describe operational realization. They identify how selected implementation artifacts run, connect, scale, observe, secure, or recover within an operational environment. They do not define the conceptual meaning of the architecture.
+Preventing deployment artifacts from redefining conceptual elements preserves conceptual stability across different deployment environments, including local development, test, regulated production, sovereign infrastructure, and air-gapped or restricted environments.
+===== Applies To =====
+This requirement applies to all deployment-related references within the Conceptual Architecture.
+It applies specifically to artifacts such as:
+  * Runtime configurations
+  * Container descriptors
+  * Orchestration manifests
+  * Deployment scripts
+  * Environment-specific settings
+  * Network topology descriptions
+  * Operational dashboards
+  * Infrastructure profiles
+===== Verification =====
+Verification SHALL confirm that deployment artifacts do not redefine conceptual elements.
+Verification activities include review checks confirming that:
+  * Deployment artifacts appear only as deployment concerns
+  * Deployment profiles map to conceptual elements without changing their meaning
+  * Environment-specific arrangements do not replace conceptual definitions
+  * Operational examples do not become conceptual requirements
+===== Traceability =====
+Related source section:
+  * [[fxdemo:01-part:13-conceptual-requirements:13-2-conceptual-separation-requirements]]
+Related requirement identifiers:
+  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-001:start]]
+  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-002:start]]
+  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-003:start]]
+  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-005:start]]
+===== Status =====
+Draft