A complete walkthrough of building a declarative deployment CLI from scratch — one that generates its own config files, enforces policy before acting, and audits everything it does. Table of Contents The Problem Architecture Overview Part A — The Engine The Manifest: Single Source of Truth The Tool That Writes Its Own Infrastructure The API Service The CLI Subcommands Part B — The Eyes and the Brain Instrumentation: /metrics in Pure Python The Policy Sidecar: OPA Writing Rego Policies Gated Lifecycle: deploy and promote The Status Dashboard The Audit Report The Chaos Experiments Lessons Learned Replication Guide The Problem Most DevOps tooling asks you to write config files by hand. You write a docker-compose.yml , an nginx.conf , maybe a Kubernetes manifest — and then you maintain all of them separately. When something changes, you update three files instead of one, and they drift apart. SwiftDeploy flips this. You write one file — manifest.yaml — and the tool derives everything else from it.…