| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001:start [2026/07/15 12:52] – nick_dido | dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001:start [2026/07/22 08:51] (current) – nick_dido |
|---|
| ====== MO-001 ====== | ====== MO-001 — Repeatable, Compliant, and Secure Infrastructure Environments ====== |
| |
| [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]] | [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]] |
| |
| ===== Statement ===== | ===== Original Requirement ===== |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL create [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]] that satisfy the applicable acceptance criteria for deployment time, [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], security, and compliance. | > //Crucible SHALL enable rapid creation of repeatable, compliant, and secure infrastructure environments.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] |
| |
| ===== Source Statement ===== | ===== Assessment of Original Requirement ===== |
| |
| > Crucible SHALL enable rapid creation of repeatable, compliant, and secure infrastructure environments. | The Original Requirement preserves the approved mission objective but does not express independently testable normative statements. |
| | |
| ===== Source ===== | |
| | |
| Crucible System Requirements Specification, Version 1.1 Draft, Mission Objectives, MO-001. | |
| | |
| ===== Assessment ===== | |
| | |
| The source statement preserves the approved mission objective but does not express a fully testable requirement. | |
| |
| The following Specification Discipline and Authoring findings apply: | The following Specification Discipline and Authoring findings apply: |
| |
| * **Enable** is a weak verb that describes facilitation rather than the behavior [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs | * **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 | * **Rapid** does not identify a duration, threshold, baseline, or comparison method |
| * **Repeatable** does not identify the controlled inputs or comparison criteria required to determine equivalence | * **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 applicable compliance baseline or acceptance criteria | * **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 applicable security baseline or required security controls | * **Secure** does not identify the [[dido:99_annexes:annex-b-terms-and-definitions:s:security_baseline|Security Baseline]] or required security controls |
| * The source statement combines deployment time, reproducibility, security, and compliance into one compound objective | |
| |
| The normalized Statement replaces the weak verb and undefined qualifiers with a direct action and references to applicable acceptance criteria. | The Original Requirement combines the following independently testable outcomes: |
| |
| ===== Rationale ===== | * Infrastructure Environment creation |
| | * Deployment duration |
| | * Repeatability |
| | * Compliance |
| | * Security |
| |
| Organizations often require substantial manual effort to construct [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]], apply security configurations, perform compliance assessments, and reproduce the resulting environments. | The Original Requirement does not identify the Controlled Inputs, baselines, thresholds, or evaluation criteria required to verify these outcomes. |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] reduces this effort by coordinating: | The Original Requirement therefore requires: |
| |
| * Declarative configuration | * Replacement of **enable** with observable Crucible behavior |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Descriptions]] | * Definition of the duration or performance criterion represented by **rapid** |
| * Reusable [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] | * Identification of the Controlled Inputs and comparison criteria used to determine repeatability |
| * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] | * Identification of the Compliance Baseline and acceptance criteria used to determine compliance |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layers]] | * Identification of the Security Baseline and required controls used to determine security |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] | * Separation of the independently testable outcomes |
| * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] construction | * Confirmation that the derived requirements collectively preserve the complete intent of MO-001 |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:provisioning|Provisioning]] | |
| * Compliance assessment | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] generation | |
| |
| The [[dido:99_annexes:annex-b-terms-and-definitions:s:security_plane|Security Plane]] governs the application and verification of security controls throughout these activities. | 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. |
| |
| Controlled and repeatable workflows support [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], security control application, compliance evaluation, and consistent environment creation across connected and disconnected operational contexts. | ===== Proposed Statements ===== |
| |
| ===== Applies To ===== | The Original Requirement is decomposed into independently identifiable proposed replacement requirements: |
| |
| This requirement applies to: | {{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}} |
| |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] | ===== Requirement Status ===== |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Descriptions]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layers]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] construction | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:provisioning|Provisioning]] | |
| * Compliance assessment | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:s:security_plane|Security Plane]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] integration | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] management | |
| |
| ===== Verification ===== | <todo>Review and approve the proposed decomposition of MO-001 into independently testable requirements.</todo> |
| |
| - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] creates an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] from controlled declarative inputs and reusable [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] | <todo>Determine whether the child requirements under MO-001 collectively supersede MO-001.</todo> |
| - Verification SHALL confirm that environment creation satisfies the deployment time acceptance criteria defined for the applicable test | |
| - Verification SHALL confirm that repeated execution with equivalent controlled inputs produces equivalent [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]] according to defined comparison criteria | |
| - Verification SHALL confirm that the workflow applies the security controls required by the selected security baseline | |
| - Verification SHALL confirm that the resulting environment satisfies the acceptance criteria defined by the selected compliance baseline | |
| - Verification SHALL confirm that each identified [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_finding|Compliance Finding]] is recorded in the applicable compliance output | |
| |
| Verification may include: | <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> |
| |
| * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] tests | ---- |
| * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] build tests | ===== Issues ===== |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] tests | |
| * Compliance scan tests | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] generation tests | |
| * Repeated build comparisons | |
| * Repeated deployment comparisons | |
| * Connected and disconnected workflow demonstrations | |
| * End-to-end [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] tests | |
| |
| The verification record SHALL identify: | The following unresolved issues affect the decomposition of MO-001: |
| |
| - The controlled inputs | <todo>Define the duration, threshold, baseline, and measurement method represented by rapid.</todo> |
| - The applicable deployment time acceptance criteria | |
| - The environment comparison criteria | |
| - The selected security baseline | |
| - The selected compliance baseline | |
| - The observed results | |
| - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | |
| |
| ===== Traceability ===== | <todo>Identify the Controlled Inputs and comparison criteria used to determine whether Infrastructure Environments are repeatable.</todo> |
| |
| This requirement supports: | <todo>Identify the Compliance Baseline and acceptance criteria used to determine whether an Infrastructure Environment is compliant.</todo> |
| |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start|FR-CFG-001 through FR-CFG-005]] | <todo>Identify the Security Baseline and required controls used to determine whether an Infrastructure Environment is secure.</todo> |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:start|FR-IMG-001 through FR-IMG-006]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:start|FR-DEP-001 through FR-DEP-007]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:start|FR-AG-001 through FR-AG-005]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:start|FR-COMP-001 through FR-COMP-010]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:start|FR-DSO-001 through FR-DSO-006]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:start|FR-BAS-001 through FR-BAS-004]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-10-dependency-capture-and-offline-transfer:start|FR-DEPC-001 through FR-DEPC-005]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:12-key-value-proposition-requirements:kvp-001:start|KVP-001 — Reduce environment deployment timelines]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:12-key-value-proposition-requirements:kvp-003:start|KVP-003 — Improve deployment repeatability]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:12-key-value-proposition-requirements:kvp-004:start|KVP-004 — Improve compliance consistency]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:12-key-value-proposition-requirements:kvp-005:start|KVP-005 — Reduce configuration drift]] | |
| |
| KVP identifies a Key Value Proposition requirement. | <todo>Determine whether the child requirements under MO-001 provide complete coverage of the approved intent of MO-001.</todo> |
| |
| This requirement also relates to: | ---- |
| | ===== Notes for Editors ===== |
| |
| * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] | This page should retain the stable parent requirement identifier ''MO-001''. |
| * [[dido:02-crusible:06-machine-images-and-image-layers:start|6. Machine Images and Image Layers]] | |
| * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]] | |
| * [[dido:02-crusible:08-dependencies-and-air-gap-operations:start|8. Dependencies and Air Gap Operations]] | |
| * [[dido:02-crusible:09-compliance-and-security:start|9. Compliance and Security]] | |
| * [[dido:02-crusible:10-reproducibility-provenance-and-traceability:start|10. Reproducibility, Provenance, and Traceability]] | |
| |
| ===== ConOps Relationship ===== | This page is a non-leaf requirement page and retains a trailing '':start'' in its namespace. |
| |
| The Crucible Concept of Operations describes Phase 1 as a command-line utility invoked through [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] steps. | The child requirements are leaf requirement pages and omit a trailing '':start'' from their namespaces. |
| |
| The Phase 1 workflow: | 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. |
| |
| * Composes [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layers]] and [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] | This page preserves: |
| * Builds and hardens [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] | |
| * Captures dependencies and [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_finding|Compliance Findings]] | |
| * Performs [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] | |
| * Produces supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | |
| | |
| This workflow provides the operational realization of environment creation, [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], security control application, and compliance evaluation. | |
| | |
| ===== Delivery Phase ===== | |
| | |
| Phase 1 and subsequent phases | |
| | |
| ===== Implementation Status ===== | |
| | |
| Not Assessed | |
| | |
| Implementation status requires verification against the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation and applicable acceptance criteria. | |
| | |
| ===== 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-001`. | * 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 |
| |
| Changes to the Statement SHALL preserve the approved intent of the source requirement. | The Original Requirement should not be marked as superseded until the requirement owner: |
| |
| Material changes should receive review and should update the related Traceability, verification criteria, and source records. | * 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 |
| |
| The Source Statement should preserve the original wording from the controlling System Requirements Specification. | After supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment. |
| |
| Do not rename this page once it has been cited externally unless a redirect or move plan is in place. | Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records. |
| |
| ---- | ---- |