id-promotelisted

The infra-delivery cross-env PROMOTION orchestrator (step 16) — "this change passed in env N, carry it to env N+1 (e.g. staging→prod)." ADVISORY orchestration that RE-RUNS the existing per-env change-delivery loop in the TARGET env, adding NO new verdict. For the target env it re-derives the GitOps class via classify_gitops(changed_paths, infra_binding) from the frozen change scope × the target profile's infra_binding.gitops_paths, surfaces the ADVISORY id-impact v1 blast_radius hint (a DISPLAY hint for the operator, NOT a routing input — the dropped match_blast engine is NOT used), then drives id-apply's BUILT decide_apply(changed_paths, infra_binding) with its ACTUAL TWO inputs RE-DERIVED in the target env (changed_paths from the frozen change scope; infra_binding from the target profile — NEVER an env-N value, NEVER the removed blast_tier/high_blast_acked args; an unresolvable input REFUSEs, fail-closed). The EXECUTE branch runs the frozen infra_binding.apply against the AWS context the operator has alread
lukasrepublic/agentic-foundry · ★ 1 · AI & Automation · score 67

Install: claude install-skill lukasrepublic/agentic-foundry

# id-promote — the cross-env promotion orchestrator (infra-delivery step 16) The `infra-delivery` step sequence (a documented procedure this skill family forms — no workflow engine or state-machine file ships) drives an IaC change → realized infrastructure, per environment. Step 16 `id-promote` is the **promotion procedure**: *"this change passed in env N — carry it to env N+1 (e.g. staging→prod)."* It is **ADVISORY orchestration** — it defines **NO new verdict** of its own. It **RE-RUNS the existing per-env change-delivery loop in the target environment**, composing the already-shipped primitives over the **next env's** gitops class and binding, then proves the change **LANDED** in the target env through the post-deploy realization frame. A change green in staging is **NOT** auto-green in the next environment. **The merge floor** (the adopter's branch protection + CI checks — see `docs/merge-floor.md`) re-derives at the promotion merge into the target env, the **realization verdict** re-derives landing per env, and **id-apply's `decide_apply`** — re-derived against the target environment's own change scope and `infra_binding` — decides the apply. `id-promote` **REFLECTS** each of those re-derivations; it never substitutes its own assertion for any of them. ## When to trigger - The `infra-delivery` sequence advances to the **promotion step** (step 16) — a change verified in env N is to be carried to env N+1 (staging→prod). - The operator says "`/foundry:id-promote`", "p