9.4 Data Plane Type Definitions

Go To Top

Return to DDS / IDL / Type Generation

Data Plane type definitions support the exchange of Data between Nodes. In Phase 0, the Data Plane model may remain limited or partly placeholder, as the initial goal is to demonstrate the Node network and Control Plane behavior rather than full financial processing.

The team should define Data Plane IDL structures only when Phase 0 Nodes need typed Data Plane messages for the demonstration Baseline. If the initial Baseline uses placeholder Data Plane topics, the type definitions should make their placeholder status clear in the Topic Catalogue, Node Catalogue, and relevant tests.

Data Plane structures should trace to the FX Demo Logical Profile. A Data Plane type should represent a meaningful demonstration concept, such as an FX Transaction, validation result, cash-flow request, cash-flow result, Provenance record, or Audit event, only when Phase 0 actually needs that structure.

The team should not encode full financial semantics directly into Phase 0 IDL unless the relevant architecture or profile defines the required meaning. IDL should provide the typed exchange structure. Architecture documents, catalogues, validation rules, and later semantic Artifacts should provide the governed meaning.