MO-002a — Maximum Platform Deployment Duration

Go to MO-002 — Reduced Platform Deployment Timelines

Statement

Crucible SHALL complete the selected Platform Deployment within the maximum Deployment Duration specified by the applicable Acceptance Criteria.

Derived From

This requirement derives from:

The Original Requirement states:

Crucible SHALL reduce platform deployment timelines from months to days or hours through automation.[C2]

MO-002a preserves the portion of the Original Requirement that establishes a target duration for completing a Platform Deployment.

The separate requirement derived from MO-002 addresses:

Assessment

The Original Requirement uses from months to days or hours without identifying:

The maximum permitted Deployment DurationThe applicable Platform DeploymentThe starting eventThe completion eventThe activities included in the measured durationThe applicable operational contextThe measurement methodThe treatment of failed, incomplete, interrupted, or repeated deploymentsThe Acceptance Criteria used to determine whether the measured duration is acceptableThe terms days or hours provide alternative and unbounded target ranges rather than a measurable performance threshold.

MO-002a:

Replaces days or hours with a maximum Deployment DurationIdentifies Crucible as the responsible actorIdentifies the selected Platform Deployment as the measured activityRequires the applicable Acceptance Criteria to specify the maximum permitted Deployment DurationSeparates the maximum-duration obligation from comparison against an approved Deployment BaselineRemoves through automation because the phrase prescribes an implementation approach rather than the required outcome

Rationale

Organizations require predictable Platform Deployment timelines to support development, integration, testing, evaluation, release, recovery, and operational planning.

A qualitative or unbounded target such as days or hours does not establish an objectively verifiable performance obligation. A maximum Deployment Duration provides a measurable limit based on defined measurement boundaries.

The applicable Acceptance Criteria establish:

The selected Platform DeploymentThe operational contextThe activities included in the measured deploymentThe starting eventThe completion eventThe maximum permitted Deployment DurationThe measurement methodThe required measurement precisionThe treatment of failed, incomplete, interrupted, or repeated deploymentsDifferent Acceptance Criteria can apply to different:

Platform typesDeployment scopesInfrastructure sizesComputing resourcesNetwork conditionsConnected EnvironmentsDisconnected EnvironmentsAir-Gapped EnvironmentsInitial deploymentsRepeated deploymentsRecovery deploymentsThis requirement establishes an absolute maximum Deployment Duration. It does not require the measured duration to improve upon an approved Deployment Baseline. MO-002b establishes the relative duration-reduction requirement.

Applies To

This requirement applies to:

constructionInfrastructure DeploymentProvisioningCompliance AssessmentDeployment ValidationConnected EnvironmentsDisconnected EnvironmentsAir-Gapped EnvironmentsCI/CD PipelinesEvidenceProvenanceTraceability

Verification

Verification confirms that:

The applicable Acceptance Criteria identify the selected Platform DeploymentThe applicable Acceptance Criteria identify the Platform Deployment activities included in the measurementThe applicable Acceptance Criteria identify a defined starting eventThe applicable Acceptance Criteria identify a defined completion eventThe applicable Acceptance Criteria specify the maximum permitted Deployment DurationThe measured Deployment Duration begins when the defined starting event occursThe measured Deployment Duration ends when the defined completion event occursThe selected Platform Deployment reaches the state required by the defined completion eventThe measured Deployment Duration does not exceed the maximum permitted Deployment DurationFailed, incomplete, interrupted, and repeated deployments receive the treatment specified by the applicable Acceptance CriteriaVerification includes:

Acceptance Criteria inspectionPlatform Deployment scope inspectionControlled Input inspectionDeployment-event inspectionStarting-time captureCompletion-time captureElapsed-time calculationPlatform state inspectionDeployment-result inspectionRepeated Platform Deployment testsConnected Environment testsDisconnected Environment testsAir-Gapped Environment testsEnd-to-end CI/CD Pipeline testsThe verification record identifies:

The applicable Acceptance CriteriaThe selected Platform DeploymentThe operational contextThe Platform Deployment activities included in the measurementThe selected Controlled InputsThe defined starting eventThe defined completion eventThe recorded starting timeThe recorded completion timeThe measured Deployment DurationThe maximum permitted Deployment DurationThe treatment of any failed, incomplete, interrupted, or repeated deploymentThe observed resultThe generated Evidence

Requirements Realized By

This requirement is realized by:

Related Architecture Sections

Referenced By

The following pages reference this requirement:

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires measurement of the current Crucible implementation against the maximum Deployment Duration specified by the applicable Acceptance Criteria.

Requirement Status

Draft

This requirement derives from MO-002 in the Crucible System Requirements Specification, Version 1.1 Draft.

Notes for Editors

This requirement page should retain the stable requirement identifier MO-002a.

This page is a leaf requirement page and omits a trailing :start from its namespace.

Changes to the Statement SHALL preserve the maximum Platform Deployment duration intent derived from MO-002.

The applicable Acceptance Criteria should identify:

The selected Platform DeploymentThe operational contextThe activities included in the measurementThe starting eventThe completion eventThe maximum permitted Deployment DurationThe measurement methodThe required measurement precisionThe treatment of failed, incomplete, interrupted, and repeated deploymentsThe required EvidenceMaterial changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:mo-002a#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.