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:

Assessment

The Original Requirement identifies infrastructure as an asset but does not require a unique identifier for the managed asset.

Without a unique identifier, an evaluator cannot reliably distinguish:

One Infrastructure Baseline from another Infrastructure BaselineAn Infrastructure Baseline from an Infrastructure Deployment created from itReferences to the same Infrastructure Baseline across repositories, catalogs, deployment records, and EvidenceThe identity of an Infrastructure Baseline from the identity of one of its revisionsThe Original Requirement does not identify:

The object receiving the identifierThe uniqueness boundary for the identifierThe relationship between the identifier and the Infrastructure Baseline ArtifactThe use of the identifier in selection, reuse, deployment records, Provenance, and TraceabilityThe Evidence required to demonstrate identifier uniquenessMO-005b:

Identifies Crucible as the responsible actorIdentifies the Infrastructure Baseline as the object receiving the identifierIdentifies the assigned identifier as an Artifact identifierRequires the identifier to be uniqueSeparates Infrastructure Baseline identity from revision identification and Version ControlSeparates identification from Artifact management, selection, reuse, immutability, and deployment traceability

Rationale

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

The identifier enables Crucible and external systems to reference the same Infrastructure Baseline across:

Artifact repositoriesArtifact catalogsBaseline composition recordsApproval recordsVersion Control systemsInfrastructure Deployment recordsCompliance recordsSecurity recordsEvidence recordsProvenance recordsTraceability relationshipsThe Infrastructure Baseline identifier identifies the baseline as a managed Artifact. A separate revision identifier can distinguish individual revisions of that Artifact.

The stable Artifact identifier supports:

Unambiguous baseline selectionReuse of the same baseline across multiple Infrastructure DeploymentsComparison of baseline revisionsRetrieval of baseline historyAssociation of approvals with the correct baselineAssociation of deployments with the correct baselinePreservation of ProvenanceMaintenance of TraceabilityGeneration of auditable EvidenceThis requirement does not establish the revision identifier or revision-management behavior. MO-005c establishes Version Control requirements.

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

Applies To

This requirement applies to:

Artifact identifiersArtifact catalog recordsArtifact repositoriesBaseline composition recordsBaseline approval recordsVersion Control recordsInfrastructure Deployment recordsCompliance recordsSecurity recordsEvidenceProvenanceTraceability

Verification

Verification confirms that:

Each Infrastructure Baseline has an Artifact identifierThe Artifact identifier refers to one Infrastructure BaselineNo two Infrastructure Baselines have the same Artifact identifier within the applicable 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 baseline revisionsThe identification record preserves the required Evidence, Provenance, and TraceabilityVerification includes:

Infrastructure Baseline inspectionArtifact identifier inspectionIdentifier uniqueness testingArtifact catalog inspectionArtifact repository inspectionCross-repository identifier comparisonBaseline composition record inspectionBaseline approval record inspectionVersion Control record inspectionInfrastructure Deployment record inspectionEvidence inspectionProvenance inspectionTraceability inspectionThe verification record identifies:

The Infrastructure BaselineThe assigned Artifact identifierThe applicable identifier scopeThe associated Artifact catalog recordThe associated Artifact repository recordEach related baseline record inspectedEach duplicate or conflicting identifier detectedThe uniqueness determinationEach identified failure or exceptionThe observed resultThe generated Evidence

Requirements Realized By

This requirement is realized by:

Related Architecture Sections

Referenced By

The following pages reference this requirement:

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification that the current Crucible implementation assigns a unique Artifact identifier to each Infrastructure Baseline.

Requirement Status

Draft

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

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.

Changes to the Statement should preserve the Infrastructure Baseline identification intent derived from MO-005.

The identifier scheme should define:

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