FR-DEP-007 — Deployment Validation

Go to Crucible Deployment Orchestration Requirements

Statement

Crucible SHALL perform Deployment Validation by evaluating an identified deployment result against the applicable Acceptance Criteria.

Source Statement

The system shall support Deployment Validation.

Source

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

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 Validation names an activity but does not identify the evaluated subjectThe source statement does not identify the criteria used for validationThe source statement does not identify an observable validation resultThe source statement does not prescribe a validation tool, test framework, provider, validation method, or implementation technologyThe normalized Statement:

Replaces The system with CrucibleReplaces support with the direct behavior performUses the defined Deployment Validation conceptIdentifies an identified deployment result as the evaluated subjectIdentifies applicable Acceptance Criteria as the evaluation basisRetains one primary required behaviorPreserves implementation independenceThe normalized Statement does not define the Acceptance Criteria. The applicable deployment specification, Baseline, policy, or lower-level requirement defines those criteria.

Rationale

A completed deployment does not by itself establish that the resulting subject satisfies the conditions required for its intended use.

Deployment Validation evaluates the deployment result against identified Acceptance Criteria.

The evaluated deployment result may include:

Deployed Infrastructure ResourcesA deployed Virtual MachineA deployed Kubernetes ClusterA deployed Containerized WorkloadA deployed Platform ServiceA resulting Infrastructure EnvironmentRelationships among deployed subjectsAcceptance Criteria may evaluate:

Resource existenceRequired configurationRequired relationshipsRequired operational stateRequired network behaviorRequired identity and access behaviorRequired security controlsRequired service availabilityRequired health conditionsRequired compliance resultsFR-DEP-007 does not independently establish any particular Acceptance Criterion.

Deployment Validation differs from deployment execution:

Deployment execution creates or changes a deployment subjectDeployment Validation evaluates the resulting state against Acceptance CriteriaDeployment Validation differs from compliance assessment:

Deployment Validation evaluates a deployment result against deployment Acceptance CriteriaCompliance assessment evaluates a subject against identified compliance criteriaCompliance results may form part of the applicable Deployment Validation criteria.

Deployment Validation contributes to:

Detection of incomplete deploymentsDetection of incorrect deployment stateControlled acceptance of deployment resultsRollback or recovery decisionsEvidenceAuditabilityTraceability

Applies To

This requirement applies to:

Deployment resultsAcceptance CriteriaInfrastructure ResourcesVirtual MachinesKubernetes ClustersContainerized WorkloadsPlatform ServicesInfrastructure EnvironmentsDeployment workflowsValidation operationsValidation resultsCI/CD Pipelines

Verification

Verification SHALL confirm that the tested deployment result is identifiedVerification SHALL confirm that the applicable Acceptance Criteria are identifiedVerification SHALL confirm that Crucible evaluates the identified deployment result against the applicable Acceptance CriteriaVerification SHALL confirm that Crucible determines whether the deployment result satisfies each applicable Acceptance CriterionVerification SHALL confirm that Crucible records the Deployment Validation resultVerification may include:

Infrastructure Resource validation testingVirtual Machine validation testingKubernetes Cluster validation testingContainerized Workload validation testingPlatform Service validation testingSuccessful-validation testingFailed-validation testingAcceptance Criteria inspectionDeployment-result inspectionValidation-output inspectionValidation-log inspectionAutomated CI/CD Pipeline testingThe verification record SHALL identify:

The evaluated deployment resultThe applicable Acceptance CriteriaThe observed result for each Acceptance CriterionThe Deployment Validation operationThe Deployment Validation resultThe 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-007.

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 predeployment and postdeployment activities within an automated Phase 1 CI/CD Pipeline.

FR-DEP-007 establishes the behavior required to evaluate an identified deployment result against the applicable Acceptance Criteria.

Requirements governing deployment execution, compliance assessment, rollback, recovery, logging, and Evidence retention define separate behavior.

Delivery Phase

Phase 1

Implementation Status

Not Assessed

Implementation status requires verification that Crucible performs Deployment Validation by evaluating an identified deployment result against the applicable Acceptance Criteria.

Requirement Status

Draft

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

Notes for Editors

This requirement page should retain the stable requirement identifier FR-DEP-007.

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 evaluating an identified deployment result against the applicable Acceptance Criteria.

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

Requirements for deployment execution, compliance assessment, rollback, recovery, logging, and Evidence retention 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-007#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.