| Both sides previous revision Previous revision | |
| fxdemo:01-part:10-conceptual-traceability-model:10-6-deployment-artefact-to-evidence [2026/08/04 07:08] – ↷ Links adapted because of a move operation nick_dido | 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 |
|---|
| [[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. | [[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 [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] showing that a [[dido:99_annexes:annex-b-terms-and-definitions:n: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. | 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: | Examples include: |
| | Kubernetes Deployment or Pod | Startup logs, status records, health reports, and captured heartbeat messages | | | 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 | | | ConfigMap or mounted configuration file | Configuration snapshot, checksum, version record, review record | |
| | Deployed [[dido:99_annexes:annex-b-terms-and-definitions:n:financial_node|Node]] | [[dido:99_annexes:annex-b-terms-and-definitions:n:financial_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 | | | 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 | | | Policy release service deployment | Release decision record, redaction output, audit entry, policy-version record | |