Differences

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

--- fxdemo:01-part:11-conceptual-rules-and-constraints:11-11-conceptual-constraints-summary [2026/06/29 14:31] – removed - external edit (Unknown date) 127.0.0.1
+++ fxdemo:01-part:11-conceptual-rules-and-constraints:11-11-conceptual-constraints-summary [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+====== 11.11 Conceptual Constraints Summary ======
+[[fxdemo:01-part:start | Go to Top ]]
+The Conceptual Architecture applies the following constraints:
+  - Conceptual elements remain distinct from one another.
+  - Conceptual architecture does not prescribe execution granularity, deployment granularity, communication technology, interface style, [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]] serialisation format, or runtime packaging.
+  - [[dido:99_annexes:annex-b-terms-and-definitions:c:classification_path|Classification]] values identify business and [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantic]] scope, not [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime]] boundaries.
+  - [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]] classify architectural purpose, not implementation mechanisms.
+  - Implementation mappings realize concepts; they do not redefine them.
+  - Deployment artifacts execute implementations; they do not redefine concepts or logical elements.
+  - [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] supports claims; it does not replace claims.
+  - [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] preserves relationships across layers.
+  - Local profiles preserve parent meaning unless they explicitly define a controlled extension.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>