====== 20.11 Deployment and Evidence Concerns Remain Outside Part 4 ====== [[fxdemo:04-part:start | Go To Top ]] [[fxdemo:04-part:20-phase-0-implementation-rules-and-constraints:start | Return to Phase 0 Implementation Rules and Constraints ]] Part 4 prepares implementation artefacts for [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]], testability, [[dido:99_annexes:annex-b-terms-and-definitions:o:observation|Observation]], operation, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. It does not define deployment topology, runtime operations, test execution, [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance]] evidence, runtime evidence, dashboards, [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes|Kubernetes]] or [[dido:99_annexes:annex-b-terms-and-definitions:k:k3s|K3s]] deployment, [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] scenarios, or final evidence packages. Part 5 owns those concerns. Part 5 deploys, tests, observes, operates, and evidences the implementation artefacts defined by Part 4. This boundary prevents deployment and evidence choices from redefining the implementation profile or the logical architecture. © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.