DIDO Solutions technical documentation and FX Demo knowledge base https://wiki.didosolutions.com/ 2026-08-22T20:30:27+00:00 https://wiki.didosolutions.com/ https://wiki.didosolutions.com/_media/wiki/logo.png text/html 2026-07-07T18:40:01+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/00-part/08-layering-rules/07-1-concepts-precede-logical-models?rev=1783449601&do=diff 7.1 Concepts Precede Logical Models Go to Top Conceptual definitions come before logical relationships. A later logical model must use the conceptual vocabulary consistently. ---------- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. text/html 2026-07-07T18:55:52+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/00-part/08-layering-rules/07-2-logical-models-precede-implementation-mappings?rev=1783450552&do=diff 7.2 Logical Models Precede Implementation Mappings Go to Top The Logical Architecture / PIM defines what the system means and how its parts relate before any implementation technology is selected. ---------- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/00-part/08-layering-rules/07-3-implementation-profiles-realise-logical-models?rev=1784403224&do=diff 7.3 Implementation Profiles: Realize Logical Models Go to Top An Implementation Profile / PSM maps logical elements to selected technologies. For example, the Phase 0 Implementation Profile may map Communication Endpoints to DDS Topics and Data Structure Definitions to IDL structures. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/00-part/08-layering-rules/07-4-deployment-profiles-execute-implementation-profiles?rev=1784403224&do=diff 7.4 Deployment Profiles Execute Implementation Profiles Go to Top A deployment profile defines how implementation artifacts run in a concrete environment. For example, a Kubernetes or K3s profile may deploy containerised Nodes as pods. ---------- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. text/html 2026-07-07T19:22:24+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/00-part/08-layering-rules/07-5-evidence-supports-claims?rev=1783452144&do=diff 7.5 Evidence Supports Claims Go to Top Evidence supports claims about architecture, implementation, deployment, execution, interpretation, or governance. Logs may contribute to evidence, but evidence is broader than logging. ---------- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. text/html 2026-07-07T19:22:39+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/00-part/08-layering-rules/07-6-runtime-identifiers-do-not-replace-architectural-concepts?rev=1783452159&do=diff 7.6 Runtime Identifiers Do Not Replace Architectural Concepts Go to Top Runtime identifiers must not replace architectural concepts. Table 7.6-1: Examples of runtime identifiers that must not replace architectural concepts Do not treat this As this DDS Domain ID text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/00-part/08-layering-rules/07-7-later-parts-must-preserve-traceability?rev=1784403224&do=diff 7.7 Later Parts Must Preserve Traceability Go to Top Each part should preserve traceability to the relevant parent layer. A logical element should trace back to the conceptual element it specializes in or the conceptual element it refines. An implementation artifact should trace back to the logical element it realizes. A deployment artifact should trace to the implementation artifact it deploys. Evidence should trace to the claim it supports. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/00-part/08-layering-rules/start?rev=1784403224&do=diff 7. Layering Rules Go to Top The document set uses the following layering rules. 7. Layering Rules7.1 Concepts Precede Logical Models7.2 Logical Models Precede Implementation Mappings07-3-implementation-profiles-realize-logical-models7.4 Deployment Profiles Execute Implementation Profiles7.5 Evidence Supports Claims7.6 Runtime Identifiers Do Not Replace Architectural Concepts7.7 Later Parts Must Preserve Traceability ---------- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.