1. Introduction

Go to Crucible

This section introduces Crucible, explains its purpose and scope, identifies its intended audience, and establishes the conventions used throughout the Crucible wiki.

Crucible provides a controlled 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 management, and compliance automation into a reproducible lifecycle.

Crucible supports Connected Environments, Disconnected Environments, and Air-Gapped Environments. It separates provider-independent architectural intent from provider-specific implementation and preserves Traceability, Provenance, and Evidence across lifecycle stages.

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