12.7 Data Plane Non-Goals for Phase 0 [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 12.7 Data Plane Non-Goals for Phase 0 ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:12-data-plane-topics:start | Return to Data Plane Topics ]]

Phase 0 does not need to implement the full [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]] required by the final Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]]. The team should make this limitation explicit so that reviewers understand what the [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] proves and what it leaves for later phases.

Phase 0 Data Plane non-goals include:

  - Full ACTUS processing.
  - Complete FX transaction Lifecycle management.
  - Complete financial-domain semantics.
  - Production-grade validation logic.
  - Full Provenance and lineage implementation.
  - Full audit event model.
  - Full authorized external release packaging.
  - Full IEF policy enforcement.
  - Full cross-jurisdictional visibility control.
  - Performance optimization.
  - Production-scale replay.
  - Enterprise operational monitoring.

The Phase 0 Data Plane should prove implementation discipline, not production completeness. It should show that the team can define typed Topics, generate supporting Artifacts, connect publishers and subscribers, validate message flow, and preserve [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] to the architecture.

Phase 0 Data Plane work should also avoid assuming that all future Nodes may observe all Data Plane Topics. Later phases may introduce sovereignty-aware and residency-aware visibility controls, policy-governed Topic participation, metadata or aggregate views, and recipient-specific release products. Phase 0 does not implement those controls, but its Topic naming, type-generation, catalogue, logging, and validation practices should leave room for them.

Later phases may expand the Data Plane by adding richer structures, more precise semantics, additional Node participation, stronger validation, more advanced QoS policies, replay support, Provenance, policy enforcement, and cross-vendor interoperability testing.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>