FR-DEP-006 — Deployment Rollback

Go to Crucible Deployment Orchestration Requirements

Statement

Crucible SHALL reverse a deployment by restoring the affected deployment subject to its identified predeployment state.

Source Statement

The system shall support deployment rollback.

Source

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-006.

Assessment

The source statement expresses the approved intent but does not provide a fully testable formulation.

The following Specification, Discipline, and Authoring findings apply:

The system does not use the defined system nameshall does not follow the established uppercase normative conventionSupport is a weak verb that does not identify the required behaviorDeployment rollback names an operation but does not identify its required resultThe source statement does not identify the deployment subject affected by rollbackThe source statement does not identify the state to which the deployment subject returnsThe source statement does not require automatic rollback, rollback after every failure, or rollback of external stateThe source statement does not prescribe a rollback mechanism, checkpoint format, transaction model, provider, or implementation methodThe normalized Statement:

Replaces The system with CrucibleReplaces support with the direct behavior reverseIdentifies the affected deployment subjectIdentifies the predeployment state as the required rollback resultRetains one primary required behaviorPreserves implementation independenceThe normalized Statement does not require an automatic rollback. Separate requirements or workflow rules determine when an actor or process initiates rollback.

Deployment Rollback should receive a glossary definition because this requirement depends on a precise distinction among rollback, recovery, redeployment, and replacement.

Rationale

A deployment may fail or produce an unacceptable result after changing an Infrastructure Environment, Infrastructure Resource, Virtual Machine, Kubernetes Cluster, Containerized Workload, or Platform Service.

Deployment Rollback reverses the deployment effects required to restore the affected subject to an identified predeployment state.

The predeployment state may be identified through:

A prior BaselineA prior RevisionA prior Infrastructure ConfigurationA prior ImageA recorded resource stateA deployment checkpointAnother identified valid stateDeployment Rollback differs from recovery:

Deployment Rollback reverses the effects of a deploymentRecovery restores operation after a failure and may use rollback, repair, replacement, or another mechanismDeployment Rollback differs from redeployment:

Deployment Rollback restores an identified prior stateRedeployment applies a deployment again and may produce the same or a different resulting stateDeployment Rollback contributes to:

Controlled response to unsuccessful deploymentRestoration of a known stateReduced duration of deployment disruptionConsistent environment stateProvenanceAuditabilityTraceability

Applies To

This requirement applies to:

DeploymentsDeployment subjectsPredeployment statesDeployment resultsRollback operationsInfrastructure EnvironmentsInfrastructure ResourcesVirtual MachinesKubernetes ClustersContainerized WorkloadsPlatform ServicesBaselinesRevisionsCI/CD Pipelines

Verification

Verification SHALL confirm that the tested deployment has an identified predeployment stateVerification SHALL confirm that Crucible executes a rollback operation for the affected deployment subjectVerification SHALL confirm that the rollback operation reverses the tested deploymentVerification SHALL confirm that the affected deployment subject matches the identified predeployment state after successful rollbackVerification may include:

Infrastructure Resource rollback testingVirtual Machine rollback testingKubernetes Cluster rollback testingContainerized Workload rollback testingPlatform Service rollback testingPredeployment-state comparisonPostrollback-state comparisonDeployment-log inspectionRollback-log inspectionAutomated CI/CD Pipeline testingThe verification record SHALL identify:

The affected deployment subjectThe deployment operationThe identified predeployment stateThe deployment resultThe rollback operationThe rollback resultThe observed postrollback stateThe generated Evidence

Outgoing Traceability

This requirement realizes:

This requirement relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference FR-DEP-006.

Incoming Traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list.

Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship.

ConOps Relationship

The Crucible Concept of Operations describes automated deployment through a Phase 1 CI/CD Pipeline.

FR-DEP-006 establishes the behavior required to reverse a deployment and restore the affected subject to its identified predeployment state.

Requirements governing deployment initiation, deployment validation, recovery, backup, restoration, and immutable replacement define separate behavior.

Delivery Phase

Phase 1

Implementation Status

Not Assessed

Implementation status requires verification that Crucible reverses a deployment by restoring the affected deployment subject to its identified predeployment state.

Requirement Status

Draft

The source System Requirements Specification identifies Version 1.1 as a draft.

Notes for Editors

This requirements page should retain the stable requirement identifier 'FR-DEP-006'.

Changes to the Statement SHALL preserve the approved intent of the source requirement.

The Source Statement should preserve the original wording from the controlling System Requirements Specification.

The Statement should remain limited to the reversal of a deployment and the restoration of the affected subject to its identified pre-deployment state.

Requirements for automatic rollback initiation, recovery, backup, restoration, replacement, validation, and retention of rollback records should remain in their applicable requirement pages.

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

Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.

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}}

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

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.