====== Capability Layer ====== [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] ===== Discussion ===== A Capability Layer is an [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layer]] that adds a defined operational, platform, service, or workload capability to a source [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]]. The layer may add software packages, runtime services, configuration, policies, agents, orchestration components, monitoring tools, or workload-specific dependencies. A Capability Layer separates capability-specific content from the operating-system, guest-configuration, and security-hardening layers on which it depends. This separation supports controlled change, reuse, comparison, and independent maintenance of the capability. Applying a Capability Layer produces a [[dido:99_annexes:annex-b-terms-and-definitions:c:capability_image|Capability Image]]. ===== Definition ===== //[[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|image layer]] that adds a defined operational, platform, service, or workload capability to a source [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|machine image]]// ===== Source ===== Generalized from layered machine-image, platform-engineering, configuration-management, and workload-image usage and specialized for the Crucible architecture and operational model. ===== Note ===== A Capability Layer identifies the controlled changes used to add a capability. A Capability Image identifies the resulting Machine Image after those changes have been applied. A Capability Layer may depend on a specific operating-system family, processor architecture, security posture, or preceding Image Layer. ===== Example ===== A Kubernetes Capability Layer adds container-runtime packages, Kubernetes services, node configuration, network components, and cluster-management tools to a Hardened Image. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.