Logical Node Traceability

Return to L Terms

Discussion

Logical Node Traceability relates a Logical Node to its conceptual source, Logical Node Identity, Logical Node Roles, Logical Node Responsibilities, Logical Communication Endpoints, Runtime Plane participation, interactions, governance relationships, and evidence expectations.

Logical Node Traceability allows reviewers to understand why a Logical Node exists, what responsibilities it performs, which endpoints it uses, which information structures it exchanges, which Runtime Planes it participates in, and which evidence expectations apply to it.

Logical Node Traceability also prepares later profiles to map a Logical Node to implementation and deployment artefacts without redefining the Logical Node.

Definition

Traceability relationship connecting a Logical Node to its identities, roles, responsibilities, endpoints, interactions, Runtime Planes, governance relationships, and evidence expectations.

Source

Specialisation of Node, Node Identity, Node Role, Traceability, and Evidence from Part 1, Sections 7.2, 7.3, 7.4, 7.10, and 7.9; generalised from node, role, identity, and evidence material in the original FX Demo Reference Architecture.

Note

Logical Node Traceability identifies logical responsibility. It does not prescribe process ownership, deployment ownership, operational ownership, or runtime packaging.

Example

A Logical Validation Node traces to the Validation Node Role, the transaction-event endpoint, the validation-result endpoint, Logical Data Plane participation, Logical Audit and Provenance Plane participation, the validation rule version, and evidence expectations for validation outcomes.

Return to Top

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