fxdemo:01-part:11-conceptual-rules-and-constraints:11-4-classification-values-do-not-define-runtime-boundaries

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
fxdemo:01-part:11-conceptual-rules-and-constraints:11-4-classification-values-do-not-define-runtime-boundaries [2026/06/29 14:31] – removed - external edit (Unknown date) 127.0.0.1fxdemo:01-part:11-conceptual-rules-and-constraints:11-4-classification-values-do-not-define-runtime-boundaries [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== 11.4 Classification Values Do Not Define Runtime Boundaries ======
 +[[fxdemo:01-part:start | Go to Top ]]
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:c:classification_path|Classification]] values identify governed business and [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantic]] scope. They do not define [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime]] communication boundaries, deployment boundaries, security zones, repository paths, or executable artifacts.
 +
 +For example, the classification path:
 +
 +  Finance Ecosphere
 +  └── Monetary Ecosystem
 +    └── Foreign Exchange Domain
 +[[dido:99_annexes:annex-b-terms-and-definitions:c:classification_path|Classification]] values identify the inherited business and [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantic]] scope of the FX Demo. They do not define a DDS Domain ID, Kubernetes namespace, container name, topic namespace, or deployment profile.
 +----
 +
 +<WRAP centeralign>
 +
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +</WRAP>