Differences

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

--- fxdemo:00-part:07-document-responsibilities:start [2026/06/24 15:18] – ↷ Page moved and renamed from fxdemo:00-part:07-document-responsibilities to fxdemo:00-part:07-document-responsibilities:start nick_dido
+++ fxdemo:00-part:07-document-responsibilities:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== 6. Document Responsibilities ======
+[[fxdemo:00-part:start | Go to Top ]]
 Each part has a distinct responsibility.
@@ Line 8: / Line 10: @@
 | Part 1 | Conceptual Architecture | Defines stable concepts, classification model, runtime-plane concepts, traceability, evidence, and separation of concerns. |
 | Part 2 | Logical Architecture / PIM | Defines platform-independent relationships, responsibilities, constraints, and information flows. |
-| Part 3 | FX Demo Logical Profile | Specialises the logical architecture for the Foreign Exchange demonstration. |
+| Part 3 | FX Demo Logical Profile | Specializes the logical architecture for the Foreign Exchange demonstration. |
-| Part 4 | Phase 0 Implementation Profile / PSM | Maps selected logical concepts to Phase 0 technologies and implementation artefacts. |
+| Part 4 | Phase 0 Implementation Profile / PSM | Maps selected logical concepts to Phase 0 technologies and implementation artifacts. |
 | Part 5 | Phase 0 Deployment, Testability, and Evidence Plan | Defines how Phase 0 is deployed, tested, observed, and evidenced. |
-Later phase documents may extend the document set by defining additional implementation or demonstration profiles. A later-phase profile may introduce capabilities not part of the Phase 0 baseline, provided those capabilities preserve the layering rules of the document set. For example, a Phase 2 Policy Plane and Authorised Release profile may define how the logical architecture is extended with policy-governed information sharing, release controls, metadata and aggregate view generation, and evidence requirements. Those capabilities should be introduced first at the conceptual and logical layers before being realised in an implementation profile.
+Later phase documents may extend the document set by defining additional implementation or demonstration profiles. A later-phase profile may introduce capabilities not part of the Phase 0 baseline, provided those capabilities preserve the layering rules of the document set. For example, a Phase 2 Policy Plane and Authorized Release profile may define how the logical architecture is extended with policy-governed information sharing, release controls, metadata and aggregate view generation, and evidence requirements. Those capabilities should be introduced first at the conceptual and logical layers before being realized in an implementation profile.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>