1. Introduction

Go to Crucible

This section introduces Crucible, explains its purpose and scope, identifies its intended audience, describes how to use this wiki, and establishes the conventions used throughout the document.

Crucible provides a controlled and reproducible approach for constructing, hardening, assessing, transferring, deploying, and maintaining software and Infrastructure Environments. It combines Declarative Descriptions, composable Baselines, Machine Images, Infrastructure as Code (IaC), Dependency Capture, deployment automation, and compliance automation into a coordinated operational lifecycle.

Crucible supports operations in Connected Environments, Disconnected Environments, and Air-Gapped Environments. It preserves Traceability, Provenance, and Evidence across lifecycle stages and transfer boundaries.

Crucible supports Accredited Software Factory objectives, but Crucible does not grant Accreditation, Operational Approval, or an Authority to Operate (ATO). The responsible governance, assessment, and authorizing authorities make those determinations using the governing criteria, assessment results, and supporting Evidence.