Architecture
Tool ownership, public contracts, and lifecycle boundaries.
Version v0.1 of the documentation is no longer actively maintained. The site that you are currently viewing is an archived snapshot. For up-to-date documentation, see the latest version.
Concepts
Architecture, security, and state boundaries.
These pages explain why ainfra separates project configuration, contracts,
infrastructure state, host configuration, and workload deployment.
Security model
Threat assumptions, enforced invariants, and verification layers.
Project configuration and locking
Committed desired state and generated template provenance.
State and secrets
Backend requirements, secret references, and recovery.
Template strategy
How ainfra turns versioned template source into reviewable infrastructure.