P4-REQ-21-8-012
Statement
Implementation flows SHALL NOT redefine FX logical interaction patterns.
Source
Part 4, Section 21.8: Interaction Pattern Realization Requirements.
Rationale
Implementation flows are technical realizations of interaction patterns defined by the FX Demo Logical Profile. They may introduce implementation-specific sequencing, scripts, configuration, communication mechanisms, or runtime packaging, but they do not define the logical meaning of the interaction.
This constraint preserves separation between Part 3 logical behavior and Part 4 implementation realization.
Applies To
This requirement applies to:
-
implementation processing flows;
-
DDS exchange sequences;
-
scripts;
-
configuration artifacts;
-
runtime participants; and
-
demonstration flows.
Verification
Verification SHALL confirm that Phase 0 implementation flows do not redefine FX logical interaction patterns.
Verification activities should include review checks confirming that:
-
logical interaction definitions remain governed by Part 3;
-
implementation-specific sequencing does not silently change logical meaning;
-
implementation participants remain mapped to applicable logical responsibilities;
-
supporting scripts and configuration remain implementation concerns; and
-
changes to logical behavior are governed at the applicable logical layer.
Traceability
This requirement preserves the separation between Part 3 FX logical interaction patterns and their selected Phase 0 implementation realizations.
Related requirement identifiers:
Related source section:
Status
Draft
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.