MO-005b — Infrastructure Baseline Identification

Go to MO-005 — Reusable and Version-Controlled Infrastructure Baselines

Statement

Crucible SHALL assign a unique Artifact identifier to each Infrastructure Baseline.

Derived From

This requirement derives from:

The Original Requirement states:

The system SHALL establish infrastructure as a reusable and version-controlled asset.[C1]

MO-005b preserves the identification needed to manage infrastructure as a reusable and version-controlled asset by requiring each Infrastructure Baseline to have a unique Artifact identifier.

The separate requirements derived from MO-005 address:

Rationale

A unique Artifact identifier provides a stable identity for each Infrastructure Baseline.

The identifier allows Crucible and external systems to refer to the same Infrastructure Baseline across:

Artifact repositoriesArtifact catalogsBaseline composition recordsApproval recordsRevision-control recordsInfrastructure Deployment recordsCompliance recordsSecurity recordsEvidence recordsProvenance recordsTraceability relationshipsThe Infrastructure Baseline identifier identifies the baseline as a managed Artifact. A separate revision identifier distinguishes one controlled revision of that Artifact from another.

A stable Artifact identifier supports:

Unambiguous Infrastructure Baseline selectionReuse of the same Infrastructure Baseline across multiple Infrastructure DeploymentsComparison of Infrastructure Baseline revisionsRetrieval of Infrastructure Baseline historyAssociation of approvals with the correct Infrastructure BaselineAssociation of deployments with the correct Infrastructure BaselinePreservation of ProvenanceMaintenance of TraceabilityThis requirement does not establish the revision identifier or revision-control behavior. MO-005c addresses those outcomes.

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

Applies To

This requirement applies to:

Artifact identifiersArtifact catalog recordsArtifact repository recordsInfrastructure Baseline approval recordsInfrastructure Baseline revision recordsInfrastructure Deployment recordsEvidenceProvenanceTraceability

Verification

Verification confirms that:

Each Infrastructure Baseline has an assigned Artifact identifierEach Artifact identifier refers to one Infrastructure BaselineNo two Infrastructure Baselines have the same Artifact identifier within the defined identifier scopeThe Artifact identifier remains associated with the Infrastructure Baseline across repositories, catalogs, and related recordsThe Artifact identifier distinguishes the Infrastructure Baseline from an Infrastructure Deployment created from itThe Artifact identifier remains distinguishable from identifiers assigned to individual Infrastructure Baseline revisionsThe verification record preserves Traceability among the Infrastructure Baseline, assigned Artifact identifier, repository records, catalog records, revision records, and deployment records

Referenced By

The following pages reference this requirement:

Delivery Phase

Implementation Status

Requirement Status

Issues

The following unresolved issues affect this requirement:

Notes for Editors

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

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:

as the responsible actorThe Infrastructure Baseline as the identified subjectThe Artifact identifier as the assigned identifierUniqueness of the identifier within the defined identifier scopeThe identifier scheme should define:

The identifier syntaxThe uniqueness scopeThe identifier-issuing authorityThe relationship between an Artifact identifier and a revision identifierThe relationship between the identifier and an Artifact catalog recordThe treatment of identifier collisionsThe treatment of retired Infrastructure BaselinesMaterial 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:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005b#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.