public:99_annexes:annex-b-terms-and-definitions:c:crucible_description

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:c:crucible_description [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:c:crucible_description [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Crucible Description ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Crucible Description is a machine-processable [[public:99_annexes:annex-b-terms-and-definitions:d:declarative_description|Declarative Description]] that binds the controlled inputs, selections, relationships, constraints, and intended lifecycle operations for a Crucible build or deployment.
 +
 +A Crucible Description may identify image sources, provisioning sources, infrastructure sources, pinned versions, target providers, image requirements, compliance posture, deployment requirements, and target-environment information.
 +
 +The Crucible Description references controlled source repositories and other external artifacts rather than embedding every implementation artifact directly. Crucible retrieves the referenced sources and records their resolved revisions before performing the selected lifecycle operations.
 +
 +The term distinguishes this machine-processable Crucible artifact from an ordinary narrative description used in architecture, requirements, explanatory text, or documentation.
 +
 +===== Definition =====
 +
 +//machine-processable [[public:99_annexes:annex-b-terms-and-definitions:d:declarative_description|declarative description]] that binds the controlled inputs, selections, relationships, constraints, and intended lifecycle operations for a Crucible build or deployment//
 +
 +===== Source =====
 +
 +Specialized from declarative configuration, build specification, deployment description, and infrastructure orchestration usage for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +A Crucible Description supports repeatability by making selected inputs, versions, relationships, and intended operations explicit.
 +
 +Within a section that has already introduced the full term, the shortened term **Description** may refer to a Crucible Description when the meaning remains unambiguous.
 +
 +An unlinked use of the ordinary word “description” does not necessarily identify a Crucible Description.
 +
 +===== Example =====
 +
 +A Crucible Description identifies a [[public:99_annexes:annex-b-terms-and-definitions:r:rhel]] image source, an Ansible provisioning source, a Kubernetes infrastructure source, pinned source revisions, an Oracle Cloud Infrastructure Provider Plugin, and a [[public:99_annexes:annex-b-terms-and-definitions:s:stig]] compliance posture.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>