Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| fxdemo:01-part:11-conceptual-rules-and-constraints:11-2-conceptual-elements-remain-distinct [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:11-2-conceptual-elements-remain-distinct to fxdemo:01-part:11-conceptual-rules-and-constraints:11-2-conceptual-elements-remain-distinct owen | fxdemo:01-part:11-conceptual-rules-and-constraints:11-2-conceptual-elements-remain-distinct [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| The Financial Systems Archetype keeps core conceptual elements distinct. | The Financial Systems Archetype keeps core conceptual elements distinct. | ||
| - | A Node is not a Node Role. A Node Identity is not a container name. A Communication Endpoint is not the Data Structure Instance it carries. A Data Structure Definition is not a Data Structure Instance. A Runtime Plane is not a DDS Domain, DDS partition, Kubernetes namespace, or network segment. | + | A [[dido: |
| Maintaining these distinctions allows later parts to map concepts to technologies without losing the conceptual meaning. | Maintaining these distinctions allows later parts to map concepts to technologies without losing the conceptual meaning. | ||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | |||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | </ | ||