====== MO-005a — Infrastructure Baseline Artifact Management ======

[[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:start|Go to MO-005 — Reusable and Version-Controlled Infrastructure Baselines]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL manage each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] as an [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]].

===== Derived From =====

This requirement derives from:

  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:start|MO-005 — Reusable and Version-Controlled Infrastructure Baselines]]

The Original Requirement states:

> //The system SHALL establish infrastructure as a reusable and version-controlled asset.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

MO-005a preserves the portion of the Original Requirement that treats infrastructure as a managed asset by identifying the managed subject as an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] and the managed representation as an [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]].

The separate requirements derived from MO-005 address:

  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005b|MO-005b — Infrastructure Baseline Identification]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005c|MO-005c — Infrastructure Baseline Revision Control]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005d|MO-005d — Approved Infrastructure Baseline Selection]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005e|MO-005e — Infrastructure Baseline Reuse]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005f|MO-005f — Approved Infrastructure Baseline Preservation]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005g|MO-005g — Infrastructure Deployment Baseline Traceability]]

===== Rationale =====

Managing an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] as an [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] gives the baseline a controlled representation that Crucible can store, retrieve, inspect, compare, approve, select, and apply.

An Infrastructure Baseline Artifact can contain or reference:

  * Infrastructure definitions
  * Configuration definitions
  * Machine Image references
  * Image-layer references
  * Package and dependency references
  * Security configuration
  * Compliance configuration
  * Deployment parameters
  * Validation criteria
  * Supporting metadata
  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] information
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] information

Artifact management establishes the controlled representation required for identification, revision control, approval, selection, reuse, preservation, and deployment Traceability.

This requirement does not define the identifier assigned to the Infrastructure Baseline. MO-005b addresses identification.

This requirement does not establish revision control. MO-005c addresses revision control.

This requirement does not require selection or reuse of the Infrastructure Baseline. MO-005d and MO-005e address those outcomes.

===== Applies To =====

This requirement applies to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]
  * Infrastructure Baseline content
  * Infrastructure Baseline metadata
  * Artifact repositories
  * Artifact storage
  * Artifact retrieval
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

===== Verification =====

Verification confirms that:

  - Each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] has a managed [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] representation
  - The Artifact contains or references the content that constitutes the Infrastructure Baseline
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] stores the Artifact
  - Crucible retrieves the Artifact
  - Crucible exposes the Artifact content and associated metadata for inspection
  - The Artifact representation remains distinguishable from an Infrastructure Deployment created from the Infrastructure Baseline
  - The management record identifies the Infrastructure Baseline and its Artifact representation
  - The management record preserves the required [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:02-crusible}}

===== Delivery Phase =====

Implemented and Verified.

===== Implementation Status =====

<todo>Assess whether the current Crucible implementation manages each Infrastructure Baseline as an Artifact.</todo>

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

<todo>Review and accept MO-005a as a proposed derived requirement created from the evaluation and decomposition of MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft.</todo>

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

The following unresolved issues affect this requirement:

<todo>Define the content that constitutes an Infrastructure Baseline Artifact.</todo>

<todo>Define the metadata required for each Infrastructure Baseline Artifact.</todo>

<todo>Identify the repository or storage mechanism used to manage Infrastructure Baseline Artifacts.</todo>

<todo>Define the storage, retrieval, and inspection behaviors required for Infrastructure Baseline Artifacts.</todo>

<todo>Define the criteria used to distinguish an Infrastructure Baseline Artifact from an Infrastructure Deployment created from that baseline.</todo>

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

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

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

The parent MO-005 page is a non-leaf page and retains a trailing '':start'' in its namespace.

Changes to the Statement should preserve:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor
  * The [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] as the managed subject
  * The [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] as the controlled representation
  * Management of each Infrastructure Baseline as an Artifact

The Artifact representation should identify or reference:

  * The Infrastructure Baseline content
  * The Artifact type
  * The associated metadata
  * The repository or storage location
  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

Material changes should receive review and should update the verification criteria, source records, and Issues section.

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

<code dokuwiki>
{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005a#Statement&noheader&nofooter&noeditbtn}}
</code>

Do not rename this page after an external citation unless a redirect or move plan is in place.

----

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