====== C.3.3 Deployment Orchestration ======

[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:start|Go to Crucible Functional Requirements]]

The Deployment [[dido:99_annexes:annex-b-terms-and-definitions:o:orchestration]] [[dido:99_annexes:annex-b-terms-and-definitions:f:functional_requirement|requirements]] define how [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] deploys infrastructure resources, virtual machines, dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes Clusters]], [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workloads]], and [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]] and performs [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_rollback|Deployment Rollback]] and [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]].

Together, these requirements establish coordinated [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] and [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] behavior that contributes to repeatable deployment results, operational recovery, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]].

===== Contents =====

{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration#1|js navbar nocookie maxjs#1 id#crucible_deployment_orchestration_requirements_nav}}

===== Notes for Editors =====

The individual requirement pages should retain the stable identifiers ''FR-DEP-001'' through ''FR-DEP-007''.

Individual requirement pages are leaf nodes and should not include a trailing '':start'' in their namespaces.

The Source Statement on each requirement page should preserve the original wording from the controlling System Requirements Specification.

Normalized Statements should use direct, testable behavior and should identify the applicable deployment subject, [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]], operation, and required result.

Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.

Incoming [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] should use the wiki Backlinks function rather than a manually maintained list.

To reference a requirement Statement from another wiki page, insert:

<code dokuwiki>
{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}
</code>

Replace ''<namespace>'' with the namespace of the requirement leaf page.

The section name following ''#'' SHALL match the section heading verbatim on the requirement page.

Do not rename a requirement page after an external citation unless a redirect or move plan is in place.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>