5.6 Validate the Result

Go to 5. Operational Concept

Deployment Validation evaluates an identified deployment result against the applicable Acceptance Criteria.

A completed deployment establishes that the deployment operations reached a completion state. It does not independently establish that the resulting environment satisfies the conditions required for its intended use.

Crucible therefore evaluates the resulting deployed state after the applicable deployment operations complete.

Crucible identifies the deployment result subject to validation.

The deployment result can include:

• Deployed Infrastructure Resources
• A deployed Virtual Machine
• A deployed Kubernetes Cluster
• A deployed Containerized Workload
• A deployed Platform Service
• A resulting Infrastructure Environment
• Relationships among deployed subjects

The identified deployment result retains its relationship to:

• The deployment operation
• The selected Deployment Target
• The deployed resources
• The selected Baselines
• The deployed Images
• The deployment parameters
• The provider implementation
• The deployment status

Crucible identifies the Acceptance Criteria applicable to the deployment result.

The applicable deployment specification, Baseline, policy, or lower-level requirement defines the Acceptance Criteria.

Acceptance Criteria can evaluate:

• Required resource existence
• Required configuration
• Required relationships
• Required operational state
• Required network behavior
• Required identity and access behavior
• Required security controls
• Required service availability
• Required health conditions
• Required compliance results

FR-DEP-007 does not independently establish a particular Acceptance Criterion.

Crucible evaluates the identified deployment result against each applicable Acceptance Criterion.

The validation activity can include:

1. Identify the deployment result
2. Identify the applicable Acceptance Criteria
3. Obtain the observations required by each criterion
4. Compare the observed deployment state with the expected state
5. Determine whether the deployment result satisfies each criterion
6. Record the result for each criterion
7. Determine the overall Deployment Validation result
8. Generate the applicable Evidence

The validation method depends on the deployment subject and Acceptance Criteria. The requirement does not prescribe a validation tool, test framework, provider, or implementation technology.

The Deployment Validation result identifies whether the evaluated deployment result satisfies the applicable Acceptance Criteria.

Possible outcomes include:

• Successful validation
• Failed validation
• Incomplete validation
• Validation prevented by unavailable information or resources

A failed criterion does not automatically determine the corrective action. The applicable workflow, policy, or authorized actor determines whether the result requires remediation, redeployment, rollback, recovery, reassessment, or another action.

Deployment execution creates or changes a deployment subject.

Deployment Validation evaluates the resulting deployment state against identified Acceptance Criteria.

A successful deployment operation can therefore produce a deployment result that does not satisfy one or more Acceptance Criteria.

Crucible preserves the distinction between:

• The deployment-operation result
• The Deployment Validation result

Deployment Validation differs from Compliance Assessment.

• Deployment Validation evaluates a deployment result against deployment Acceptance Criteria
• Compliance Assessment evaluates an identified subject against identified compliance criteria

A Compliance Assessment result can form part of the applicable Acceptance Criteria, but Deployment Validation does not replace Compliance Assessment.

Deployment Validation can provide information used to initiate a rollback or recovery decision.

Deployment Validation does not itself require:

• Automatic rollback
• Restoration of a prior state
• Remediation
• Redeployment
• Replacement of a deployed Image
• Approval of the deployment result

Separate requirements govern those behaviors.

The Deployment Validation result records:

• The validation identifier
• The evaluated deployment result
• The applicable Acceptance Criteria
• The observed result for each criterion
• The determination for each criterion
• The overall validation result
• The validation operation
• The validation time
• Any incomplete or unavailable validation information
• The associated Provenance
• The associated Traceability
• The generated Evidence

The validation result becomes an input to operational acceptance, remediation, rollback, recovery, redeployment, compliance activity, and lifecycle-record preservation as governed by the applicable requirements and policies.

The linked leaf requirement page remains the canonical source.