Differences

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

--- fxdemo:01-part:10-conceptual-traceability-model:10-6-deployment-artefact-to-evidence [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:10-6-deployment-artefact-to-evidence to fxdemo:01-part:10-conceptual-traceability-model:10-6-deployment-artefact-to-evidence owen
+++ fxdemo:01-part:10-conceptual-traceability-model:10-6-deployment-artefact-to-evidence [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
-====== 10.6 Deployment Artefact to Evidence ======
+====== 10.6 Deployment Artifact to Evidence ======
 [[fxdemo:01-part:start | Go to Top ]]
-A Deployment Artefact traces to Evidence when recorded information supports a claim about the deployed system.
+A Deployment Artifact traces to [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] when recorded information supports a claim about the deployed system.
-Evidence may support claims about deployment, execution, configuration, communication, health, recovery, policy enforcement, release, audit, provenance, or test results.
+[[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] may support claims about deployment, execution, configuration, communication, health, recovery, policy enforcement, release, audit, provenance, or test results.
-For example, a Kubernetes Deployment may trace to evidence showing that a Node started, reported health, subscribed to the expected endpoint, published a status message, and produced an audit record. A ConfigMap may trace to evidence showing which QoS profile, topic definition, or runtime configuration was active during a test.
+For example, a Kubernetes Deployment may trace to [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] showing that a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] started, reported health, subscribed to the expected [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], published a status message, and produced an audit record. A ConfigMap may trace to [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] showing which QoS profile, topic definition, or runtime configuration was active during a test.
 Examples include:
-Table 10.6-1:	Examples of deployment artefacts traced to evidence
+Table 10.6-1: Examples of deployment artifacts traced to evidence
-^ Deployment Artefact ^ Evidence ^
+^ Deployment Artifact ^ [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] ^
 | Kubernetes Deployment or Pod | Startup logs, status records, health reports, and captured heartbeat messages |
 | ConfigMap or mounted configuration file | Configuration snapshot, checksum, version record, review record |
-| Deployed Node | Node status message, audit record, provenance record, captured output |
+| Deployed [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] | [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] status message, audit record, provenance record, captured output |
 | Runtime topic or endpoint configuration | Captured publication, subscription record, topic discovery output, test result |
 | Policy release service deployment | Release decision record, redaction output, audit entry, policy-version record |
 | Test scenario execution | Test report, captured messages, logs, screenshots, evidence bundle |
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>