Walkthrough

Actions, in the order they're actually taken — not the Framework's conceptual sections, which explain the reasoning independent of any specific deployment. A single deployment step routinely crosses layers — infrastructure, OS, application — in one sitting; nesting it inside that structure means either splitting one action across several deeply-nested files, or losing track of it entirely.

Three chapters so far, in the order they actually happen:

Security — Proton Pass, set up first so every credential below has somewhere real to live the moment it's created.

Infrastructure — provider account, OpenStack credentials, OpenTofu, DNS: everything before any compute exists at all.

System — turning that bare instance into a running platform: the OS, the maintenance services running on top, and securing what's now live.

Some action content still lives inside Framework pages too, in places nothing has moved out of yet — it moves here gradually as it's touched again, not all at once.