10.10 Record Audit and Provenance

Go To Top

The Record Audit and Provenance pattern allows a Logical Node to record information needed for reconstruction, accountability, lineage, auditability, replay, recovery, review, and defensibility.

An audit or provenance-producing Logical Node records relationships among Logical Data Structure Instances, Logical Nodes, Logical Communication Endpoints, Runtime Planes, decisions, rule versions, model versions, timestamps, and Evidence expectations.

The interaction belongs primarily to the Logical Audit and Provenance Plane. It also supports other planes by recording what occurred within them and how information moved across them.

Table 10-9: Record Audit and Provenance logical interaction pattern

Element	Logical treatment
Primary Runtime Plane	Logical Audit and Provenance Plane
Producing Logical Node Role	Auditor, Provenance Producer, Validator, Interpreter, Policy Node, or Domain Information Producer
Consuming Logical Node Role	Audit Node, Provenance Node, Evidence Node, Oversight Node, or Replay Node
Primary information	Audit record, provenance record, lineage record, or evidence-supporting record
Supporting information	Input references, output references, producing Logical Node, consuming Logical Node, endpoint, rule version, timestamp
Traceability expectation	Audit and provenance records trace to the related information, Logical Nodes, endpoints, interactions, rules, and decisions.
Evidence expectation	Preserved audit and provenance records support review, reconstruction, replay, and defensibility.

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