Write a concise ADR for a platform architecture choice with consequences and review triggers.
The platform team chose Argo CD for Kubernetes deployments, but the reasoning lives in Slack and one slide deck. New teams keep asking whether GitHub Actions would be simpler. ADR recipe: status -> context -> decision -> consequences -> review trigger The common trap is writing a decision announcement instead of the context and consequences future teams need. Status Accepted, 2026-06-18, owned by Platform Delivery. Status tells readers whether the record is proposed, accepted, superseded, or deprecated. Context Teams need audited Kubernetes deploys, declarative rollback, namespace isolation, and a path that security can inspect. Context should capture the forces acting…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in