MO-002b — Platform Deployment Duration Reduction

Go to MO-002 — Reduced Platform Deployment Timelines

Statement

Crucible SHALL complete the selected Platform Deployment in less time than the approved Deployment Baseline under equivalent measurement conditions.

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-002b preserves the portion of the Original Requirement that requires a reduction in Platform Deployment duration.

The separate requirement derived from MO-002 addresses:

Assessment

The Original Requirement uses reduce without identifying:

The approved Deployment BaselineThe baseline Platform Deployment processThe baseline Deployment DurationThe Platform Deployment selected for comparisonThe activities included in each measurementThe starting eventThe completion eventThe Controlled InputsThe operational contextThe measurement methodThe degree of required reductionThe treatment of failed, incomplete, interrupted, or repeated deploymentsThe phrase from months to days or hours does not establish a controlled comparison because it does not identify a specific baseline duration or a specific measured duration.

MO-002b:

Identifies the approved Deployment Baseline as the comparison pointIdentifies the selected Platform Deployment as the measured activityRequires the selected Platform Deployment to complete in less time than the approved Deployment BaselineRequires equivalent measurement conditions for the baseline and measured Platform DeploymentsSeparates relative duration reduction from the maximum-duration obligation established by MO-002aRemoves through automation because the phrase prescribes an implementation approach rather than the required outcome

Rationale

A claim that Crucible reduces Platform Deployment duration requires an approved and measurable comparison point.

The approved Deployment Baseline records the Platform Deployment process and duration used for comparison. The baseline and measured Platform Deployments require equivalent measurement conditions so that differences in scope, inputs, resources, environment, or measurement method do not produce a misleading duration comparison.

Equivalent measurement conditions include equivalent:

Platform Deployment scopeControlled InputsStarting eventCompletion eventIncluded activitiesOperational contextComputing resourcesNetwork conditionsMeasurement methodMeasurement precisionTreatment of failed, incomplete, interrupted, and repeated deploymentsThe measured Platform Deployment satisfies this requirement when its Deployment Duration is less than the duration recorded by the approved Deployment Baseline under the applicable equivalent measurement conditions.

This requirement establishes a relative improvement over an approved Deployment Baseline. It does not establish the maximum permitted Deployment Duration. MO-002a establishes the absolute duration limit.

Applies To

This requirement applies to:

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

Verification

Verification confirms that:

The approved Deployment Baseline is uniquely identifiedThe approved Deployment Baseline records the baseline Platform Deployment processThe approved Deployment Baseline records the baseline Deployment DurationThe baseline and measured Platform Deployments use equivalent measurement conditionsThe baseline and measured Platform Deployments use equivalent Platform Deployment scopesThe baseline and measured Platform Deployments use equivalent Controlled InputsThe baseline and measured Platform Deployments use equivalent starting and completion eventsThe baseline and measured Platform Deployments include equivalent activitiesThe baseline and measured Platform Deployments use equivalent measurement methodsThe measured Deployment Duration is less than the Deployment Duration recorded by the approved Deployment BaselineFailed, incomplete, interrupted, and repeated deployments receive equivalent treatment in the baseline and measured resultsVerification includes:

Deployment Baseline inspectionBaseline Platform Deployment process inspectionBaseline duration inspectionPlatform Deployment scope comparisonControlled Input comparisonStarting-event comparisonCompletion-event comparisonIncluded-activity comparisonOperational-context comparisonComputing-resource comparisonNetwork-condition comparisonMeasurement-method comparisonMeasurement-precision comparisonStarting-time captureCompletion-time captureElapsed-time calculationDuration comparisonDeployment-result inspectionRepeated Platform Deployment testsEvidence inspectionProvenance inspectionTraceability inspectionThe verification record identifies:

The approved Deployment BaselineThe Deployment Baseline identifier and revisionThe baseline Platform Deployment processThe baseline Platform Deployment scopeThe baseline Controlled InputsThe baseline operational contextThe baseline starting eventThe baseline completion eventThe baseline activities included in the measurementThe baseline measurement methodThe baseline Deployment DurationThe measured Platform DeploymentThe measured Platform Deployment scopeThe measured Controlled InputsThe measured operational contextThe measured starting eventThe measured completion eventThe measured activities included in the measurementThe measured measurement methodThe measured Deployment DurationThe difference between the baseline and measured Deployment DurationsThe 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 comparison of the current Crucible Platform Deployment duration against the approved Deployment Baseline under equivalent measurement conditions.

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-002b.

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

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

The approved Deployment Baseline should identify:

The Deployment Baseline identifierThe Deployment Baseline revisionThe baseline Platform Deployment processThe baseline Platform Deployment scopeThe baseline Controlled InputsThe baseline operational contextThe baseline starting eventThe baseline completion eventThe activities included in the baseline measurementThe baseline measurement methodThe baseline measurement precisionThe baseline Deployment DurationThe treatment of failed, incomplete, interrupted, and repeated deploymentsThe supporting 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-002b#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.