Differences

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

--- fxdemo:01-part:05-conceptual-architecture-principles:05-3-classification-before-implementation [2026/06/25 14:40] – ↷ Page moved and renamed from fxdemo:01-part:04-3-classification-before-implementation to fxdemo:01-part:05-conceptual-architecture-principles:05-3-classification-before-implementation owen
+++ fxdemo:01-part:05-conceptual-architecture-principles:05-3-classification-before-implementation [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== 4.3 Classification Before Implementation ======
+[[fxdemo:01-part:start | Go to Top ]]
 The architecture classifies the governed financial scope before it defines implementation mechanisms.
-The Ecosphere, Ecosystem, and Domain model identifies the business and semantic scope of an archetype. These classification values do not act as runtime identifiers. They do not define DDS Domain IDs, Kubernetes namespaces, container names, pod names, topic names, Node Identities, or repository paths.
+The [[dido:99_annexes:annex-b-terms-and-definitions:e:ecosphere|Ecosphere]], [[dido:99_annexes:annex-b-terms-and-definitions:e:ecosystem|Ecosystem]], and [[dido:99_annexes:annex-b-terms-and-definitions:d:domain|Domain]] model identifies the business and semantic scope of an archetype. These classification values do not act as runtime identifiers. They do not define DDS Domain IDs, Kubernetes namespaces, container names, pod names, topic names, [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identities]], or repository paths.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>