C2 - Crucible Concept of Operations

Go to Annex B: References

Citation

Dido Solutions, Inc. and Jackrabbit Consulting, Inc., Crucible Concept of Operations (ConOps), Version 1.0 Accepted, 6 June 2026.

Reference Identifier

[C2]

Document Title

Crucible Concept of Operations

Document Type

Concept of Operations

Version

Version 1.0

Date

6 June 2026

Issuing Organizations

Dido Solutions, Inc.Jackrabbit Consulting, Inc.

Description

The Crucible Concept of Operations describes how Crucible is intended to operate.

The document defines the Phase 1 operational concept in which the forge command-line utility runs non-interactively as one or more CI/CD pipeline steps. It describes baseline composition, Machine Image construction, dependency and compliance-finding capture, infrastructure deployment, connected-to-disconnected transfer, and compliance Evidence generation.

The document also records the future Phase 2 web-management concept and the strategic, unscheduled direction toward increased native execution.

The Concept of Operations contextualizes the [C1] Crucible System Requirements Specification and remains subordinate to the System Requirements Specification and the Engineering Constitution. Where the Concept of Operations conflicts with an approved requirement, the approved requirement controls. :contentReference[oaicite:0]{index=0}

Document Status

Accepted

The project owner accepted Version 1.0 on 6 June 2026.

Operational Concepts

The Concept of Operations addresses:

Phase 1 command-line operationCI/CD pipeline integrationImage-layer baseline compositionInfrastructure baseline compositionOptional application sourceMachine Image constructionDependency captureCompliance-finding captureInfrastructure deploymentConnected-to-disconnected transferOffline package-repository populationCompliance Evidence supporting SCTM, RMF, and ATO activitiesPhase 2 web managementStrategic native execution

Related Requirements

The Concept of Operations provides operational context for:

FR-BAS-001 through FR-BAS-004FR-DSO-001 through FR-DSO-006FR-DEPC-001 through FR-DEPC-005FR-AG-001 through FR-AG-005FR-COMP-008 through FR-COMP-010FR-UI-001 through FR-UI-002INT-001INT-002FUT-007 through FUT-009

Related Architecture Decisions

The Concept of Operations identifies relationships to:

ADR-003, Baseline CompositionADR-004, Dependency Capture and Offline TransferADR-005, Operating-System-Agnostic Compliance EngineADR-006, Native Execution StrategyADR-007, Interface Phasing

Related Documents

Citation Format

Use the following link when citing this reference:

[[dido:02-crusible:99-annexes:annex-b:cr-002:start|[C2]]]

For a requirement ConOps Relationship section:

===== ConOps Relationship ===== The Crucible Concept of Operations describes this requirement as part of the Phase 1 CI/CD-embedded workflow [[dido:02-crusible:99-annexes:annex-b:cr-002:start|[C2]]].

Notes for Editors

Maintain this page as the stable citation target for the Crucible Concept of Operations.

Update the version, date, document status, and citation when a new controlled revision supersedes Version 1.0.

Preserve the reference identifier [C2] and the namespace cr-002.

Do not rename this page once it has been cited externally unless a redirect or move plan is in place.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.