dido:99_annexes:annex-b-terms-and-definitions:l:logical_interaction_traceability

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-b-terms-and-definitions:l:logical_interaction_traceability [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:l:logical_interaction_traceability [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Logical Interaction Traceability ======
  
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]]
 +
 +===== Discussion =====
 +
 +Logical Interaction Traceability relates a logical interaction pattern to its participating Logical Nodes, Communication Roles, endpoints, information structures, Runtime Planes, governance constraints, and evidence expectations.
 +
 +Logical Interaction Traceability supports review of how the architecture behaves. It identifies the structure of recurring interactions such as Register Node, Report Node Status, Publish Domain Information, Subscribe to Domain Information, Issue Control Command, Acknowledge Control Command, Request Policy Decision, Record Audit and Provenance, and Replay or Reconstruct Information.
 +
 +Logical Interaction Traceability also supports domain-profile specialization. A domain profile specializes a logical interaction pattern while preserving the trace to the reusable Part 2 pattern.
 +
 +===== Definition =====
 +
 +//Traceability relationship connecting a logical interaction pattern to Nodes, roles, endpoints, information structures, Runtime Planes, governance constraints, and evidence expectations.//
 +
 +===== Source =====
 +
 +Specialization of Traceability, Communication Endpoint, Node Role, Data Structure Instance, and Runtime Plane from Part 1, Sections 7.10, 7.6, 7.4, 7.8, and 7.5; generalised from interaction-sequence and use-case material in the original FX Demo Reference Architecture.
 +
 +===== Note =====
 +
 +Logical Interaction Traceability records the logical structure of an interaction. It does not prescribe sequence-diagram notation, test-script format, protocol exchange, or runtime message capture.
 +
 +===== Example =====
 +
 +The Request Policy Decision pattern traces to a requesting Logical Node, a policy-evaluation Logical Node, a policy-decision request, a policy-decision response, a Logical Policy and Release Plane, and audit/provenance evidence expectations.
 +
 +----
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]]
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>