====== 18.2 Part 3 FX Logical Element to Part 4 Implementation Artifact ======

[[fxdemo:04-part:18-phase-0-implementation-traceability-model:start | Go To Phase 0 Implementation Traceability Model ]]

Part 3 FX logical element to Part 4 implementation artifact [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] connects an FX logical profile element to the Phase 0 implementation artifact that realizes or supports it.

This relationship supports forward review. A reviewer can start with an FX logical [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], Node Role, Communication Endpoint, information structure, Runtime Plane, interaction pattern, governance relationship, or traceability relationship and identify the Phase 0 implementation artifact or artifacts that realize it.

**Table 18-1: Forward traceability from Part 3 FX logical elements to Part 4 implementation artifacts**

^ Part 3 FX logical element ^ Part 4 implementation artifact ^
| FX logical Node | Implementation node module, process entry point, supporting module, or runtime participant |
| FX logical Node Role | Implementation responsibility, module, function, class, or service behavior |
| FX logical Communication Endpoint | DDS Topic or selected communication artifact |
| FX logical information structure | IDL structure, generated type, implementation data representation, or runtime data instance |
| FX Runtime Plane | DDS Topic naming convention, QoS profile family, logging category, exception-handling convention, repository grouping, or implementation convention |
| FX lifecycle state | Status value, state field, generated type value, command acknowledgement value, log field, or audit/provenance record |
| FX interaction pattern | Implementation processing flow, DDS exchange, command flow, script-supported flow, or demonstration behavior |
| FX governance relationship | Versioning rule, compatibility rule, change-control rule, generated artifact rule, repository rule, or review expectation |
| FX traceability relationship | File-header metadata, generated-file metadata, IDL comments, mapping table, topic mapping record, script header, configuration metadata, or review record |
| FX evidence expectation | Implementation hook, logging convention, status report, audit/provenance record, replay result, configuration snapshot, or Part 5 evidence-planning input |

----

<WRAP centeralign>

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

</WRAP>