====== 3. Operational Environment ======

[[dido:02-crusible:start|Go to Crucible]]

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] operates across environments that differ in connectivity, deployment location, trust relationships, and transfer restrictions.

These environmental conditions affect how Crucible accesses source repositories, obtains dependencies, constructs and assesses environments, transfers artifacts, deploys resources, and preserves [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]], [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].

Crucible separates environmental conditions from the operational intent expressed through [[dido:99_annexes:annex-b-terms-and-definitions:d:declarative_description|Declarative Descriptions]], [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]], and lifecycle controls. This separation allows the same operational concepts to apply across different environments while provider-specific implementations address the technologies, interfaces, and restrictions of each environment.

The pages in this section describe the external conditions within which Crucible operates. They establish context for the operational flows described in later sections and do not create additional capabilities or requirements.

===== Contents =====

  * [[dido:02-crusible:03-operational-context:03-01-connectivity-conditions|3.1 Connectivity Conditions]]
  * [[dido:02-crusible:03-operational-context:03-02-deployment-environments|3.2 Deployment Environments]]
  * [[dido:02-crusible:03-operational-context:03-03-security-domains-and-transfer-boundaries|3.3 Security Domains and Transfer Boundaries]]

{{indexmenu>dido:02-crusible:03-operational-context#1|js navbar nocookie maxjs#2 id#crucible_operational_environment_nav}}

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>