Source Summary: Terraforming the Cloud on Hetzner
Source Identity
- title:
Terraforming the Cloud: Provisioning and Configuring Vault on Hetzner via Terraform and Ansible - type: blog post
- path:
blog-src/content/posts/terraforming-the-cloud-provisioning-configuring-vault-hetzner-terraform-ansible/index.md - date published: 2026-04-12
Scope
Implementation chronicle for the C1 local lifecycle and C2 remote durability execution on the Hetzner Vault runtime.
Key Points
- the runtime was implemented in two explicit slices: local lifecycle and S3-backed durability
- strong prior design work reduced later integration problems to confined local defects rather than architecture crises
- remote durability was modeled around lineage-aware pointers, metadata, and bounded slot rotation
- logical snapshot comparison required a separate fingerprint because file hashes alone were not stable indicators of unchanged logical state
Notable Claims
- design quality changed the nature of problems encountered during implementation
- remote durability was intentionally modeled as coherent secondary durability rather than as the sole source of runtime truth
Affected Wiki Pages
- ../topics/ephemeral-castle-hetzner-vault-runtime
- ../topics/tazlab-secret-and-identity-flow
- ../topics/tazlab-crisp-program-map
Open Questions
- Should the wiki next split C1 and C2 into dedicated subpages with state contracts, evidence, and failure modes?