dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001:mo-001b

This is an old revision of the document!


MO-001a — Infrastructure Environment Creation

Crucible SHALL create an Infrastructure Environment from the selected Controlled Inputs.

This requirement derives from:

MO-001b — Deployment Duration

This requirement derives from:

The Original Requirement states:

Crucible SHALL enable rapid creation of repeatable, compliant, and secure infrastructure environments.[C1]

MO-001b preserves the portion of the Original Requirement that characterizes Infrastructure Environment creation as rapid.

The separate requirements derived from MO-001 address:

The Original Requirement uses rapid without identifying:

  • A defined start condition
  • A defined completion condition
  • A measurable duration
  • An applicable threshold
  • An operational context
  • A comparison baseline
  • Acceptance Criteria

The term rapid therefore does not support objective verification.

MO-001b:

  • Replaces rapid with the measurable concept Deployment Duration
  • Identifies Crucible as the responsible actor
  • Identifies creation of the Infrastructure Environment as the measured activity
  • Requires evaluation against applicable Acceptance Criteria
  • Separates deployment-duration performance from environment creation, reproducibility, security, and compliance outcomes

Organizations require predictable Infrastructure Environment creation timelines to support development, testing, evaluation, deployment, recovery, and operational planning.

A qualitative term such as rapid does not establish an objective performance obligation. Deployment Duration provides a measurable quantity based on defined start and completion conditions.

The applicable Acceptance Criteria establish the duration threshold for the relevant operational context. Different Acceptance Criteria can apply to:

  • Different Infrastructure Environment types
  • Different deployment sizes
  • Different computing resources
  • Different network conditions
  • Connected Environments
  • Disconnected Environments
  • Air-Gapped Environments
  • Initial deployments
  • Repeated deployments
  • Recovery or replacement activities

Separating the duration requirement from MO-001a permits Crucible to satisfy the environment-creation requirement while independently passing or failing the applicable Deployment Duration Acceptance Criteria.

This requirement does not define the content of the Infrastructure Environment, the equivalence criteria used for Reproducibility, or the Security Baseline and Compliance Baseline applied to the Infrastructure Environment. The other requirements derived from MO-001 establish those outcomes.

Verification confirms that:

  1. The applicable Deployment Duration Acceptance Criteria identify a defined start condition
  2. The applicable Deployment Duration Acceptance Criteria identify a defined completion condition
  3. The applicable Deployment Duration Acceptance Criteria identify a maximum permitted duration or another objective duration threshold
  4. The measured Deployment Duration begins when the defined start condition occurs
  5. The measured Deployment Duration ends when the defined completion condition occurs
  6. The measured Deployment Duration satisfies the applicable Acceptance Criteria

Verification includes:

  • Acceptance Criteria inspection
  • Deployment event inspection
  • Start-time capture
  • Completion-time capture
  • Elapsed-time calculation
  • Infrastructure Environment state inspection
  • Repeated duration measurements
  • Connected Environment tests
  • Disconnected Environment tests
  • End-to-end CI/CD Pipeline tests

The verification record identifies:

  1. The applicable Deployment Duration Acceptance Criteria
  2. The operational context
  3. The selected Controlled Inputs
  4. The applicable Infrastructure Environment type
  5. The defined start condition
  6. The defined completion condition
  7. The recorded start time
  8. The recorded completion time
  9. The calculated Deployment Duration
  10. The applicable duration threshold
  11. The observed result
  12. The generated Evidence

Phase 1 and subsequent phases

Not Assessed

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

Draft

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


This requirement page should retain the stable requirement identifier MO-001b.

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

Changes to the Statement SHALL preserve the deployment-duration intent derived from MO-001.

The applicable Acceptance Criteria should define:

  • The measured activity
  • The start condition
  • The completion condition
  • The duration threshold
  • The operational context
  • Any permitted exclusions
  • The required measurement precision

Material 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-001:mo-001b#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.

The Original Requirement states:

Crucible SHALL enable rapid creation of repeatable, compliant, and secure infrastructure environments.[C1]

MO-001a preserves the portion of the Original Requirement that requires Crucible to create an Infrastructure Environment.

The separate requirements derived from MO-001 address:

The Original Requirement uses enable, which describes facilitation rather than the behavior Crucible performs.

The Original Requirement also combines Infrastructure Environment creation, deployment duration, reproducibility, security, and compliance within one normative statement. Each outcome can be implemented, verified, and traced independently.

MO-001a:

  • Replaces enable with the direct action create
  • Identifies Crucible as the responsible actor
  • Identifies the Infrastructure Environment as the required result
  • Identifies the selected Controlled Inputs as the source used to create the Infrastructure Environment
  • Separates Infrastructure Environment creation from the independently verifiable duration, reproducibility, security, and compliance outcomes

Infrastructure Environment creation provides the foundational outcome upon which the remaining requirements derived from MO-001 depend.

The selected Controlled Inputs identify the approved and controlled material used during Infrastructure Environment creation. Controlled Inputs include applicable descriptions, baselines, configurations, Image Layers, Machine Images, packages, and other required Artifacts.

Creating an Infrastructure Environment from selected Controlled Inputs supports:

  • Deterministic input selection
  • Configuration control
  • Subsequent reproduction and comparison
  • Independent evaluation of security and compliance outcomes

This requirement does not establish a required creation duration, equivalence criterion, Security Baseline, or Compliance Baseline. The other requirements derived from MO-001 establish those outcomes.

Verification confirms that:

  1. Crucible uses the selected Controlled Inputs to create the Infrastructure Environment

Verification includes:

The verification record identifies:

  1. The selected Controlled Inputs
  2. The applicable input identifiers and revisions
  3. The applicable Crucible Description
  4. The applicable Baseline Composition
  5. The applicable Provenance
  6. The observed result
  7. The generated Evidence

Phase 1 and subsequent phases

Not Assessed

Implementation status requires verification that the current Crucible implementation creates an Infrastructure Environment from the selected Controlled Inputs.

Draft

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


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

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

Changes to the Statement SHALL preserve the Infrastructure Environment creation intent derived from MO-001.

Material 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-001:mo-001a#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.

  • dido/02-crusible/99-annexes/annex-c-requirements/01-mission-objectives/mo-001/mo-001b.1784559188.txt.gz
  • Last modified: 2026/07/20 07:53
  • by nick_dido