Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:e:evidence [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:99_annexes:annex-b-terms-and-definitions:e:evidence [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== Evidence ======
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
+===== Discussion =====
+Evidence is recorded information that supports a claim about architecture, implementation, deployment, execution, interpretation, governance, or review. Evidence allows authors, reviewers, testers, operators, and auditors to connect claims to observable or reviewable records.
+Evidence may include captured messages, logs, test results, configuration records, deployment records, version records, runtime observations, audit events, provenance records, release decisions, screenshots, review findings, or scenario results.
+Evidence is broader than logging. Logs may contribute to evidence when an evidence process captures, preserves, interprets, and traces them to a specific claim.
+===== Definition =====
+//recorded information supporting a claim//
+===== Source =====
+Informed by SIP-RA audit, review, traceability, and reproducible processing concerns; aligned with FDIS-RA evidence, provenance, auditability, and defensibility concerns; adapted from FX Demo Reference Architecture persistence, audit, provenance, release-decision, and acceptance-evidence material.
+===== Note =====
+Evidence must remain traceable to the claim, behavior, artifact, configuration, execution condition, or review conclusion it supports.
+===== Example =====
+A captured heartbeat message, deployment record, test result, and provenance entry may together provide evidence that a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] started, reported status, exchanged information, and preserved traceability.