← ClaudeAtlas

devopslisted

Carry an infrastructure change from intent to verified effect: what a change must carry before apply, what "applied" does not prove, which changes a revert cannot reverse, what a credential can do that the instruction never said, and the evidence that closes a change. Not how any one tool is written.
xobotyi/cc-foundry · ★ 23 · DevOps & Infrastructure · score 84
Install: claude install-skill xobotyi/cc-foundry
Three biases decide most calls: - **Applied is not in effect.** A tool's success is a claim the tool makes about its own target. Whether the effect exists is measured at the service, the socket, the resolver, the peer, or the guest. A change closes on the measurement and never on the claim. - **A revert is not a rollback.** Re-applying the previous declaration restores what a tool can recreate from a declaration and nothing the forward change emitted: deleted data, rotated secrets, withdrawn routes, migrated schemas, destroyed objects. - **The target is decided by the credential and the state the command runs against, not by the code.** A reviewed change lands where the kubeconfig, backend, inventory, or token points, and a plan is a projection of one state at one moment. Read both before the first mutation. ## Target - **Name the target by identifiers that cannot be confused**: account or project ID, cluster API endpoint, host key and address, backend and workspace, node and VMID, zone ID. `prod` is a label, not a target. GitHub deployed a reviewed network configuration to the wrong environment on 2024-03-11. - **Plan against the state that apply will use, immediately before apply.** Never apply a plan older than the last change to the target, and never a plan made with refresh disabled. GitLab applied a three-week-old Terraform plan on 2023-07-07; drift had turned it into a plan that destroyed 617 resources. - **A missing or substituted state file is