MO-001 — Repeatable, Compliant, and Secure Infrastructure Environments [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== MO-001 — Repeatable, Compliant, and Secure Infrastructure Environments ======

[[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]]

===== Original Requirement =====

> //Crucible SHALL enable rapid creation of repeatable, compliant, and secure infrastructure environments.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

===== Assessment of Original Requirement =====

The Original Requirement preserves the approved mission objective but does not express independently testable normative statements.

The following Specification Discipline and Authoring findings apply:

  * **Enable** is a weak verb that describes facilitation rather than an observable behavior performed by [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * **Rapid** does not identify a duration, threshold, baseline, or comparison method
  * **Repeatable** does not identify the [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]] or comparison criteria required to determine equivalence
  * **Compliant** does not identify the [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_baseline|Compliance Baseline]] or acceptance criteria
  * **Secure** does not identify the [[dido:99_annexes:annex-b-terms-and-definitions:s:security_baseline|Security Baseline]] or required security controls

The Original Requirement combines the following independently testable outcomes:

  * Infrastructure Environment creation
  * Deployment duration
  * Repeatability
  * Compliance
  * Security

The Original Requirement does not identify the Controlled Inputs, baselines, thresholds, or evaluation criteria required to verify these outcomes.

The Original Requirement therefore requires:

  * Replacement of **enable** with observable Crucible behavior
  * Definition of the duration or performance criterion represented by **rapid**
  * Identification of the Controlled Inputs and comparison criteria used to determine repeatability
  * Identification of the Compliance Baseline and acceptance criteria used to determine compliance
  * Identification of the Security Baseline and required controls used to determine security
  * Separation of the independently testable outcomes
  * Confirmation that the derived requirements collectively preserve the complete intent of MO-001

The decomposition preserves ''MO-001'' as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.

===== Proposed Statements =====

The Original Requirement is decomposed into independently identifiable proposed replacement requirements:

{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001#1|js navbar nocookie maxjs#1 id#crucible_mo_001_requirements_nav}}

===== Requirement Status =====

<todo>Review and approve the proposed decomposition of MO-001 into independently testable requirements.</todo>

<todo>Determine whether the child requirements under MO-001 collectively supersede MO-001.</todo>

<todo>If the child requirements are accepted as the complete replacement for MO-001, mark MO-001 as superseded and preserve this page as the parent Traceability record.</todo>

----
===== Issues =====

The following unresolved issues affect the decomposition of MO-001:

<todo>Define the duration, threshold, baseline, and measurement method represented by rapid.</todo>

<todo>Identify the Controlled Inputs and comparison criteria used to determine whether Infrastructure Environments are repeatable.</todo>

<todo>Identify the Compliance Baseline and acceptance criteria used to determine whether an Infrastructure Environment is compliant.</todo>

<todo>Identify the Security Baseline and required controls used to determine whether an Infrastructure Environment is secure.</todo>

<todo>Determine whether the child requirements under MO-001 provide complete coverage of the approved intent of MO-001.</todo>

----
===== Notes for Editors =====

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

This page is a non-leaf requirement page and retains a trailing '':start'' in its namespace.

The child requirements are leaf requirement pages and omit a trailing '':start'' from their namespaces.

The ''indexmenu'' displays the child requirement pages contained within the MO-001 namespace. Explicit child-page links may be included while the decomposition is being developed and removed after the child pages have been created and finalized.

This page preserves:

  * The Original Requirement
  * The assessment of the Original Requirement
  * The reason for decomposition
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] to the proposed replacement requirements
  * The unresolved cross-cutting issues affecting the decomposition
  * The supersession decision

The Original Requirement should not be marked as superseded until the requirement owner:

  * Approves the proposed decomposition
  * Approves the child requirements
  * Confirms that the child requirements collectively preserve the complete approved intent of MO-001
  * Confirms that no additional child requirements are required

After supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment.

Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>