MO-006

Go to Mission Objectives

Statement

Crucible SHALL perform the applicable Operational Lifecycle activities for each Infrastructure Environment from initial Infrastructure Deployment through Retirement while preserving the applicable environment state, history, Provenance, Evidence, and Traceability.

Source Statement

The system SHALL support infrastructure lifecycle management from initial deployment through retirement.

Source

Crucible System Requirements Specification, Version 1.1 Draft, Mission Objectives, MO-006.

Assessment

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

The following Specification Discipline and Authoring findings apply:

The system does not use the defined system nameSupport is a weak verb that does not identify the behavior Crucible performsInfrastructure lifecycle management does not identify the lifecycle activities, managed information, responsible components, or required outcomesInitial deployment does not identify the event that begins the managed lifecycleRetirement does not identify the required termination, archival, preservation, or resource disposition activitiesThe source statement does not identify which environment records must remain available throughout and after the lifecycleThe source statement does not define the acceptance criteria for lifecycle transitionsThe source statement does not distinguish the lifecycle of an Infrastructure Environment from the lifecycle of a Baseline, Machine Image, or other ArtifactThe normalized Statement replaces the weak verb with perform, identifies the managed Infrastructure Environment, bounds the lifecycle from initial deployment through retirement, and identifies the information that must remain preserved.

Rationale

An Infrastructure Environment changes throughout its Operational Lifecycle.

After initial Infrastructure Deployment, an organization may need to:

Validate the deployed environmentApply configuration changesUpdate Machine ImagesApply security updatesReassess complianceReconcile environment stateRecover failed operationsRestore an environment from a backupRoll back an unsuccessful changeReplace or upgrade componentsPreserve operational and compliance recordsRetire the environment and dispose of its resourcesWithout controlled lifecycle management, an environment may diverge from its approved Baselines, lose Traceability, accumulate configuration drift, or retain resources after the environment is no longer authorized.

Crucible coordinates lifecycle activities through controlled Crucible Descriptions, versioned Baselines, recorded lifecycle transitions, validation activities, and preserved Evidence.

Each lifecycle transition should preserve the relationship among:

The affected Infrastructure EnvironmentThe applicable Crucible DescriptionThe selected Baseline revisionsThe prior environment stateThe resulting environment stateThe authorized lifecycle actionThe actor or automated process that initiated the actionThe resulting Evidence

Applies To

This requirement applies to:

Environment validationEnvironment stateLifecycle transitionsConfiguration changesState reconciliationBackup and restorationRecoveryUpgradesRollbackCompliance reassessmentRetirementResource dispositionProvenanceEvidenceTraceabilityConnected EnvironmentsDisconnected EnvironmentsAir-Gapped EnvironmentsCI/CD Pipelines

Verification

Verification SHALL confirm that each tested Infrastructure Environment has a unique identifierVerification SHALL confirm that the lifecycle record identifies the initial Infrastructure DeploymentVerification SHALL confirm that each tested lifecycle transition has a unique identifierVerification SHALL confirm that each tested lifecycle transition identifies the applicable lifecycle activityVerification SHALL confirm that each tested lifecycle transition identifies the prior environment stateVerification SHALL confirm that each tested lifecycle transition identifies the resulting environment stateVerification SHALL confirm that each tested lifecycle transition identifies the applicable Crucible DescriptionVerification SHALL confirm that each tested lifecycle transition identifies the applicable Baseline revisionsVerification SHALL confirm that each tested lifecycle transition records the actor or automated process that initiated the actionVerification SHALL confirm that each tested lifecycle transition records the execution resultVerification SHALL confirm that each successful lifecycle transition satisfies the applicable acceptance criteriaVerification SHALL confirm that each failed lifecycle transition preserves the last valid environment state or records the incomplete stateVerification SHALL confirm that recovery or rollback restores the environment to a defined valid stateVerification SHALL confirm that compliance reassessment records the applicable Compliance FindingsVerification SHALL confirm that backup and restoration preserve the applicable environment configuration, state, and recordsVerification SHALL confirm that Retirement terminates or transfers the applicable infrastructure resources according to the approved retirement criteriaVerification SHALL confirm that Retirement preserves the records required by the applicable retention policyVerification SHALL confirm that the lifecycle record preserves Provenance, Evidence, and Traceability from initial deployment through retirementVerification may include:

Initial deployment testsEnvironment validation testsConfiguration change testsState reconciliation testsCompliance reassessment testsUpgrade testsUpgrade rollback testsFailed operation recovery testsBackup testsRestoration testsBaseline revision transition testsMachine Image replacement testsDeployment history inspectionLifecycle record inspectionRetirement testsResource disposition inspectionRecord retention inspectionConnected environment demonstrationsDisconnected environment demonstrationsAir-Gapped Environment demonstrationsEnd-to-end CI/CD Pipeline testsThe verification record SHALL identify:

The tested Infrastructure EnvironmentThe environment identifierThe applicable Operational Lifecycle activitiesThe initial deployment recordThe tested lifecycle transitionsThe prior environment statesThe resulting environment statesThe applicable Crucible DescriptionsThe applicable Baseline revisionsThe initiating actors or automated processesThe applicable acceptance criteriaThe execution resultsThe recovery or rollback resultsThe applicable backup and restoration recordsThe applicable Compliance FindingsThe retirement recordThe resource disposition resultsThe applicable retention policyThe retained recordsThe generated Evidence

Outgoing Traceability

This requirement is realized by:

This requirement also relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference `MO-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 Phase 1 as a CI/CD Pipeline integrated command-line utility that performs build, compliance, dependency capture, and deployment activities.

The Phase 1 workflow:

Retrieves controlled and versioned inputsComposes selected BaselinesBuilds and hardens Machine ImagesCaptures dependencies and Compliance FindingsPerforms Infrastructure DeploymentExecutes predeployment and postdeployment activitiesRecords deployment and compliance resultsTears down environments when they are no longer requiredThe ConOps primarily describes initial deployment and related Phase 1 execution. The broader Operational Lifecycle also includes modification, reassessment, recovery, restoration, upgrade, rollback, and Retirement activities required by this mission objective.

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification of the applicable Operational Lifecycle activities from initial Infrastructure Deployment through Retirement.

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 `MO-006`.

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

Material changes should receive review and should update the related outbound traceability, verification criteria, acceptance criteria, and source records.

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

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

Do not rename this page once it has been cited externally unless a redirect or move plan is in place.

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