DevOps, CI/CD & Platform Engineering
9 clusters, spanning half-life layers 1–3: Source control workflows, CI/CD systems, Pipeline concepts, Containers, Orchestration, Infrastructure as Code, GitOps, Artifacts & secrets, Platform engineering.
Clusters
Section titled “Clusters”Source control workflows
Branching strategy and review discipline transfer to every host and every team. Monorepo tooling is Layer 3.
CI/CD systems
Triggers, jobs, matrices, caching and artefact passing are the same five concepts everywhere. YAML schemas transfer to nothing and are the whole…
Pipeline concepts
Layer 1 and the durable half. Deployment strategy reasoning is independent of every tool that implements it.
Containers
See
universal-foundations/containers. Listed here because image optimisation and multi-stage builds are a DevOps concern in practice.Orchestration
The declarative reconciliation loop — desired state, actual state, controller — is the transferable idea and it is Layer 1. Compose does not have it,…
Infrastructure as Code
State, plan/apply, drift and the dependency graph transfer across Terraform, OpenTofu, Pulumi and CDK. Ansible is the odd member — it is…
GitOps
Git as the desired-state source and continuous reconciliation transfer completely between the two members; picking one is close to arbitrary.
Artifacts & secrets
Secret lifecycle — issue, rotate, revoke, audit — and dynamic vs static credentials transfer to every cloud secret manager.
Platform engineering
Golden paths and self-service are organisational ideas that transfer; the tooling barely exists yet and churns.