Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane to dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Audit And Provenance Plane ======
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
 ===== Discussion =====
@@ Line 9: / Line 9: @@
 The Audit and Provenance Plane helps the architecture support review, replay, recovery, evidence, conformance assessment, and long-term governance. It preserves relationships among Data Structure Instances, Nodes, Communication Endpoints, policy decisions, analytical outputs, and evidence.
-A later implementation profile may realise Audit and Provenance Plane interactions through audit topics, provenance records, event stores, immutable logs, evidence packages, lineage graphs, release audit records, or replay records. Those mechanisms do not redefine the Audit and Provenance Plane.
+A later implementation profile may realize Audit and Provenance Plane interactions through audit topics, provenance records, event stores, immutable logs, evidence packages, lineage graphs, release audit records, or replay records. Those mechanisms do not redefine the Audit and Provenance Plane.
 ===== Definition =====