Crucible SHALL perform Deployment Rollback.
This requirement derives from:
The Original Requirement states:
The system shall support Deployment Rollback.[C1]
FR-DEP-006:
No other substantive normalization is required.
Deployment Rollback provides a controlled response when a deployment must be reversed.
This requirement establishes the ability to perform Deployment Rollback without prescribing:
Separate requirements, workflows, or policies define those subjects and behaviors.
This requirement applies to:
Verification confirms that:
The following pages reference this requirement:
Implemented and Verified
Review and approve FR-DEP-006 as a leaf requirement.
Determine whether separate requirements define the conditions that initiate Deployment Rollback.
Determine whether separate requirements define the required result of Deployment Rollback.
This requirement page retains the stable requirement identifier FR-DEP-006.
This page is a leaf requirement page and omits a trailing :start from its namespace.
The Statement preserves the approved source intent by requiring Crucible to perform Deployment Rollback.
Do not add automatic initiation, predeployment-state restoration, recovery, backup, replacement, validation, or rollback-record obligations unless the controlling requirement changes through an approved requirements process.
To reference this requirement Statement from another wiki page, insert:
{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-006#Statement&noheader&nofooter&noeditbtn}}
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.