2. Operational Need and Mission

Go to Crucible

Crucible responds to the operational burden created when individual projects independently construct and maintain the infrastructure, image-building, dependency, compliance, transfer, deployment, and lifecycle capabilities needed to deliver software into controlled environments.

These supporting capabilities are necessary, but they do not normally provide the mission-specific functionality that distinguishes one product from another. Reimplementing them across separate projects increases cost, fragments tools and practices, limits reuse, complicates personnel movement, and makes controlled environments harder to reproduce and maintain.

Crucible provides a reusable operational foundation for constructing, hardening, assessing, transferring, deploying, and maintaining software and Infrastructure Environments. It preserves Provenance, Traceability, and Evidence while supporting operations across Connected Environments, Disconnected Environments, and Air-Gapped Environments.

The pages in this section explain the operational problem Crucible addresses and the mission and expected outcomes derived from the approved Mission Objectives and Operational Requirements in Annex C: Requirements. They do not create an independent set of objectives or requirements.

• 2.1 Operational Need
• 2.2 Mission and Expected Outcomes