FR-DEP-007 — Deployment Validation

Go to Crucible Deployment Orchestration Requirements

Statement

Crucible SHALL perform Deployment Validation.

Derived From

This requirement derives from:

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

The system shall support Deployment Validation.[C1]

FR-DEP-007:

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 Validation to the controlling definitionNo other substantive normalization is required.

Rationale

Deployment Validation determines whether a deployment result satisfies the conditions governing acceptance of that deployment.

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

The deployment subjectThe validation methodThe applicable Acceptance CriteriaCompliance-assessment behaviorRollback behaviorRecovery behaviorPreservation of validation resultsValidation tools or implementation technologySeparate requirements, specifications, 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 validationCrucible performs Deployment Validation for the tested DeploymentThe result of the tested Deployment Validation 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-007.

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 Validation.

Do not add a specific deployment subject, Acceptance Criteria, validation method, compliance-assessment, rollback, recovery, logging, or validation-record obligation 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-007#Statement&noheader&nofooter&noeditbtn}}

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