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

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_record [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:l:logical_record [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Logical Record ======
  
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]]
 +
 +===== Discussion =====
 +
 +A Logical Record represents a Logical Data Structure Instance preserved for continuity, review, audit, provenance, replay, reconstruction, or evidence.
 +
 +Logical Records support data at rest at the logical level without prescribing a database, file system, object store, ledger, log, archive, or persistence technology. The Logical Architecture identifies what information the system preserves and why; later implementation and deployment profiles select the persistence mechanism.
 +
 +Logical Records support traceability by preserving relationships among information values, Logical Nodes, Communication Endpoints, Runtime Planes, interactions, decisions, provenance entries, and evidence claims.
 +
 +===== Definition =====
 +
 +//Logical Data Structure Instance preserved for continuity, review, audit, provenance, replay, reconstruction, or evidence.//
 +
 +===== Source =====
 +
 +Specialization of Data Structure Instance, Evidence, and Traceability from Part 1, Sections 7.8, 7.9, and 7.10; generalised from data-at-rest, persistence, audit, provenance, replay, and evidence material in the original FX Demo Reference Architecture.
 +
 +===== Note =====
 +
 +A Logical Record is not a database row, file, log entry, ledger entry, object-store object, archive item, or generated report. Implementation profiles select those realisations.
 +
 +===== Example =====
 +
 +A logical provenance record preserves the relationship between a validation assertion, its input transaction record, the producing Logical Node, the validation rule version, and the timestamp.
 +
 +----
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]]
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>