====== Workspace ====== [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] ===== Discussion ===== A Workspace provides an identified working area in which a person, automated process, or [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflow]] accesses and processes selected revisions of managed content. A Workspace can contain: * Checked-out repository content * Selected [[dido:99_annexes:annex-b-terms-and-definitions:r:revision|Revisions]] * [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layers]] * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] * Application source * [[dido:99_annexes:annex-b-terms-and-definitions:d:declarative_configuration|Declarative Configuration]] * Build inputs * Generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] * Intermediate results * Execution logs * Validation results A Workspace can exist on a developer system, within an automated execution environment, or as part of a [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]]. Within Crucible documentation, a Workspace provides the bounded working context in which Crucible consumes selected repositories, performs [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]], processes deployment-related steps, and produces identifiable results. ===== Definition ===== //identified working area containing selected managed content and execution inputs used by a person or automated process to perform one or more operations// ===== Source ===== DIDO-controlled term adapted from established version-control, software-build, development-environment, and CI/CD practices. ===== Note ===== A Workspace is a working context rather than the authoritative source of the managed content it contains. Content in a Workspace can derive from one or more repositories and identified [[dido:99_annexes:annex-b-terms-and-definitions:r:revision|Revisions]]. A Workspace differs from a repository. A repository records and manages revisions of content, while a Workspace contains selected content used for an identified execution or activity. A Workspace differs from an [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_environment|Execution Environment]]. The Workspace contains the selected working content and inputs; the Execution Environment supplies the resources and conditions under which operations execute. A Workspace can be temporary or persistent. ===== Example ===== A CI/CD Pipeline creates a Workspace, checks out identified revisions of an Image Layer repository and an Infrastructure Baseline repository, adds optional application source, and invokes Crucible to perform Baseline Composition and deployment-related operations. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.