FR-DEP-006 — Deployment Rollback

Go to Crucible Deployment Orchestration Requirements

Statement

Crucible SHALL perform Deployment Rollback.

Derived From

This requirement derives from:

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-006The Original Requirement states:

The system shall support Deployment Rollback.[C1]

FR-DEP-006:

Replaces The system with the defined system name CrucibleChanges shall to the established uppercase normative form SHALLReplaces the weak verb support with the observable behavior performLinks Deployment Rollback to the controlling definitionNo other substantive normalization is required.

Rationale

Deployment Rollback provides a controlled response when a deployment must be reversed.

This requirement establishes the ability to perform Deployment Rollback without prescribing:

The event that initiates the rollbackAutomatic rollback behaviorThe deployment subjectThe state restored by the rollbackThe rollback mechanismRecovery behaviorBackup or restoration behaviorRollback validationPreservation of rollback recordsSeparate requirements, workflows, or policies define those subjects and behaviors.

Applies To

This requirement applies to:

Deployments

Verification

Verification confirms that:

A tested Deployment is selected for rollbackCrucible performs Deployment Rollback for the tested DeploymentThe result of the tested Deployment Rollback can be determined

Referenced By

The following pages reference this requirement:

Implementation Status

Implemented and Verified

Requirement Status

Issues

Notes for Editors

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.