1. Parsing Terraform
2. IAM Policy Verification (Z3)
3. Cloud Cost Budget Enforcement
4. Network Reachability
5. Release Boundary Verification
6. Converting Results to Diagnostics
Every guard exposes ato_diagnostic() method that converts its native result into a unified InfraDiagnosticResult:
7. Working with Audit Traces
8. Emitting Verification Context documents
Every guard’sto_verification_context() runs the verification from raw inputs and emits a portable Verification Context v1.0 document. To get an ADMIT decision, mint an attestation bound to the same claim and evidence:
qwed-infra guard’s to_verification_context(), a VERIFIED result without attestation_token demotes to UNVERIFIABLE/DENY. A forged, expired, revoked, or non-matching token produces BLOCKED/DENY. (This differs from the qwed-verification POST /verification-context/from-diagnostic path, which returns BLOCKED/DENY for a missing token — see the fail-closed matrix.)