Concepts
Concepts
The ideas this repository demonstrates, separated from the YAML that implements them: GitOps as a dependency hierarchy rather than a slogan, progressive complexity in a platform API, and zero trust that is enforced by policy rather than asserted in a README.
Each page here explains why the platform is shaped a particular way and links to Platform for how it is wired. If you will never deploy this, these are the pages still worth reading.
The platform in three bands, and where the boundary between clouds falls.
One API that starts at an image and a port and grows to a production application.
Why reconciliation beats deployment, and why the dependency graph is the design.
Default-deny at the network, no ambient credentials — and where the model is relaxed.
The design method, the gates that enforce it, and where the process is expensive.