Dependency Capture identifies, obtains, records, and preserves the Dependencies required to perform a selected Operational Lifecycle activity.
Crucible treats Dependency Capture as a controlled lifecycle activity rather than an informal packaging step. The captured dependency set provides the inputs needed to reproduce a construction, assessment, transfer, deployment, validation, maintenance, or recovery activity without relying on undocumented or unavailable resources.
Crucible identifies the direct and transitive Dependencies required by the selected lifecycle activity.
Dependencies can include:
A direct Dependency is explicitly referenced by the selected input or lifecycle activity. A transitive Dependency is required by another Dependency.
Dependency identification must account for both forms when the selected activity cannot complete without them.
Crucible captures an identified Dependency from an authorized source.
The capture activity records information needed to identify and retrieve the Dependency, including:
Crucible does not treat an unspecified latest version, mutable tag, undocumented workstation file, or unrecorded external service as a reproducible Dependency.
When an external resource cannot be captured directly, the resulting record identifies the unresolved Dependency and the effect on the selected lifecycle activity.
A Dependency Manifest identifies the Dependencies associated with a controlled lifecycle activity or resulting artifact.
The Dependency Manifest records:
The Dependency Manifest provides a controlled description of the dependency set. The manifest does not replace the preserved Dependency content.
A Dependency Record preserves information about an individual Dependency and its use.
A Dependency Record can identify:
Dependency Records allow a reader or automated process to determine which Dependency contributed to a result and where the preserved content resides.
Crucible preserves captured Dependencies in a Dependency Store or another authorized repository.
Preservation protects the Dependency from loss, unrecorded replacement, or reliance on a source that may later become unavailable.
The preservation activity records:
Preserving a Dependency does not authorize its use. Applicable security, licensing, compliance, export, import, and organizational controls continue to govern the Dependency.
Crucible verifies that a preserved Dependency corresponds to the identified Dependency.
Verification can include:
A successful integrity check establishes that the evaluated content matches the recorded value. It does not independently establish that the Dependency is secure, compliant, licensed, approved, or suitable for a particular use.
In a Connected Environment, Crucible can capture Dependencies from authorized external repositories and services.
Before operating in a Disconnected Environment or Air-Gapped Environment, Crucible must identify and preserve the Dependencies required by the selected lifecycle activity.
The preserved dependency set can be:
The disconnected lifecycle activity must not depend on an unauthorized or unavailable resource outside the applicable operational boundary.
The capture and preservation result identifies:
The preserved dependency set becomes a controlled input to subsequent construction, assessment, transfer, deployment, validation, maintenance, reproduction, or recovery activities.
| Requirement | Statement |
|---|---|
| FR-DEPC-001 — Capture Build Dependencies |
Crucible SHALL perform Dependency Capture for Build Dependencies. |
| FR-DEPC-002 — Preserve Dependencies in a Dependency Store |
Crucible SHALL preserve captured Build Dependencies in a managed Dependency Store. |
| FR-DEPC-003 — Produce a Transfer Bundle |
Crucible SHALL produce a Transfer Bundle containing captured Build Dependencies. |
| FR-DEPC-004 — Populate Offline Repositories |
Crucible SHALL populate Offline Repositories in a Disconnected Environment from a Transfer Bundle. |
| FR-DEPC-005 — Dependency Store Implementation Independence |
Crucible SHALL permit the implementation of a Dependency Store to change without changing the Dependency Capture Contract. |
The linked leaf requirement pages remain the canonical sources.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.