id-implementlisted

# id-implement — author the IaC for the intended change on a branch (infra-delivery step 5) The `infra-delivery` step sequence (a documented procedure this skill family forms — no workflow engine or state-machine file ships) drives an infra change → merge. Step 5 is the **change-authoring** step. After the contract is frozen at authorize, this is where the generic agent **authors/edits the IaC** for the intended change — scaffold/edit the OpenTofu/Kubernetes files to the handbook conventions — **on a branch**. It is a PROCEDURE skill the generic agent **runs**. It **runs NO plan and mutates NOTHING** — it writes *files*. The authored IaC is **branch-quarantined** (it never touches `main`, and it never `apply`s or otherwise mutates live cloud state), and it **NAMES the frozen intended-change manifest** (the `tofu-plan` checkpoint's operator-frozen `intended` set in the acceptance-contract) it must keep the edit **in sync** with — so the downstream read-only `id-plan` plan can attribute the change for the operator/reviewer at the merge floor. ## ADVISORY — not a gate, no machine-adjudicated GREEN claim This skill is **ADVISORY**. It **authors files** + records an authoring observation; it does **NOT gate, approve, or block** any merge, and it does **NOT** decide its own PASS. The bound is the **operator-frozen contract**, not this skill — `id-implement` keeps the authored change in sync with the frozen `intended` set so the downstream `id-plan` output lets a human attribute