id-synclisted

The infra-delivery POST-MERGE GitOps reconcile-and-observe driver (step 13) — the PROCEDURE the generic agent runs AFTER merge (merge IS the deploy trigger) to drive the GitOps controller's idempotent reconcile toward the GATE-MERGED IaC, PINNED to the merged candidate_sha (argocd app sync/refresh, reusing the shipped candidate_sha/expected_sha staleness pin so the realization read is coupled to the merged commit, never an arbitrary HEAD), then READ the realized state and RECORD the realization observation via the DEDICATED post-deploy producer emit_realization_evidence (scripts/foundry_realization.py) — recording {candidate_sha, post_apply_plan_empty, argocd:{applicable, sync_status, health_status}, artifact:{applicable, deployed_identity, merged_commit}} that derive_realization_verdict consumes — NOT the pre-merge emit_infra_walk_evidence. BOTH ArgoCD axes via argocd_adjudicate (Synced ∧ Healthy ⇒ LANDED; a Degraded-but-Synced app must NOT green). never-force-sync is NOT machine-enforced (a --force/--prune
lukasrepublic/agentic-foundry · ★ 1 · AI & Automation · score 67

Install: claude install-skill lukasrepublic/agentic-foundry

# id-sync — the POST-MERGE GitOps reconcile-and-observe driver (infra-delivery step 13) 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. **Merge IS the deploy trigger**: the change realizes *after* it merges. Step 13 `id-sync` is the **realize-side driver** — it **drives** the GitOps controller's *idempotent* reconcile of the live env toward the **gate-merged IaC** (`argocd app sync`/`refresh` against the app-of-apps), then **reads** the realized state and **records** the realization observation for the **realization frame**. It is the act that makes the merged change LAND; `id-verify` (step 14) is the read-only re-check that follows. ## ADVISORY — observe-and-record, NOT a pre-merge gate This skill is **ADVISORY**. The post-deploy **realization frame** is an **observe-and-record** path: because merge already deployed, a residual NOT-LANDED **cannot un-merge** — the gate is not a pre-merge block. `id-sync` **records** the realization observation; the **realization gate** (`derive_realization_verdict`) + `deploy-status` + `id-rollback` adjudicate the recorded signals. The skill **self-certifies NOTHING** (the `id-verify`/`id-plan` discipline — the skill supplies the STEPS, the recorded-evidence model + the verdict supply the BAR). The both-modes floor is unchanged: front-authorization, the merge floor (the adopter's branch protection + CI check