Record

Go up to Terms and Definitions

Discussion

A Record represents preserved information that documents an event, state, decision, action, relationship, obligation, condition, or result.

In the FX Demo Reference Architecture, records support traceability, evidence, audit, provenance, review, replay, reconstruction, accountability, and governance.

A Record differs from a general Structure because it preserves information for later reference or review. A Record differs from a Data Structure Definition because it represents preserved information rather than the definition of a structure. A Record differs from a Data Structure Instance because it carries preservation, reference, review, or evidence significance.

Definition

preserved information that documents an event, state, decision, action, relationship, obligation, condition, or result

Source

Generalised from Logical Record from Part 2: Distributed Node-Based Logical Architecture, Section 8.9, Evidence from Part 1: Conceptual Architecture, Section 7.9, and Traceability from Part 1: Conceptual Architecture, Section 7.10; specialised for use in the FX Demo Reference Architecture.

Note

A Record is not necessarily a database record, file, log entry, ledger entry, message, API payload, DDS sample, or persistence artefact. Those artefacts may represent, store, transmit, or preserve a record.

Example

An FX Audit Record documents a release decision, the related FX Policy Decision, the FX Release Package, the recipient context, timestamp, and release obligations.