13.5 Data Plane QoS Profile
Go To Phase 0 QoS Profile Model
The Data Plane QoS profile supports FX transaction, validation, semantic, contract state, and cash-flow information exchange.
Data Plane communication must support structured FX information flow among implementation participants. It must provide enough reliability and ordering to demonstrate the Phase 0 happy path and enough Traceability to support audit, provenance, replay, and later Evidence planning.
Table 13-2: Data Plane QoS profile.
| QoS Concern | Phase 0 Treatment |
|---|---|
| Runtime Plane | FX Logical Data Plane |
| Example DDS Topics | Data.FX.TransactionCandidate; Data.FX.ValidationResult; Data.FX.SemanticAssertion; Data.FX.ContractState; Data.FX.CashFlowObligation |
| Communication purpose | Exchange FX transaction, validation, semantic interpretation, contract state, and cash-flow obligation information |
| Reliability expectation | Reliable delivery for information that drives downstream processing in Phase 0 |
| Durability expectation | Sufficient durability to support late-joining subscribers or replay-oriented review where Phase 0 requires it |
| History expectation | Retain enough samples to support expected downstream consumption and Phase 0 demonstration review |
| Ordering expectation | Preserve ordering where transaction lifecycle progression or downstream processing depends on sequence |
| Liveliness expectation | Support detection of unavailable publishers or subscribers where Phase 0 requires it |
| Compatibility expectation | Publishers and subscribers use compatible QoS profiles for each Data Plane Topic |
| Traceability expectation | QoS profile traces to corresponding FX logical Communication Endpoint, FX logical information structure, and FX Logical Data Plane |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.