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

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_information_lineage [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:l:logical_information_lineage [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Logical Information Lineage ======
  
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]]
 +
 +===== Discussion =====
 +
 +Logical Information Lineage describes the relationships among Logical Data Structure Instances as Logical Nodes exchange, transform, validate, interpret, assert, persist, replay, release, or evidence information.
 +
 +Lineage supports review and reconstruction. It allows reviewers to follow information from source values through processing steps, derived assertions, policy decisions, audit records, provenance records, and evidence expectations.
 +
 +Logical Information Lineage remains platform-independent. It does not prescribe a graph database, provenance store, event store, log format, lineage tool, or audit mechanism. Implementation profiles select the realization mechanism.
 +
 +===== Definition =====
 +
 +//Relationship history connecting Logical Data Structure Instances across exchange, transformation, validation, interpretation, assertion, persistence, replay, release, and evidence.//
 +
 +===== Source =====
 +
 +Specialization of Traceability, Evidence, Data Structure Instance, and Audit and Provenance Plane from Part 1, Sections 7.10, 7.9, 7.8, and 8.6; generalised from provenance, audit, replay, and evidence material in the original FX Demo Reference Architecture.
 +
 +===== Note =====
 +
 +Logical Information Lineage supports evidence but does not replace evidence. Evidence supports claims; lineage records relationships among information instances and processing steps.
 +
 +===== Example =====
 +
 +A cash-flow assertion traces to an input transaction record, reference data used during interpretation, an applied model version, the producing Logical Node, and the provenance record created during processing.
 +
 +----
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]]
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>