Id Sync

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 past the read leaves a non-LANDED record derive_realization_verdict FAILs — machine-derived, not skill-prose enforcement). Fail-closed ArgoCD direction — a missing/unreachable/indeterminate ArgoCD ⇒ NOT-LANDED, never a silent advisory pass. ADVISORY observe-and-record (NOT a pre-merge gate); NOT-LANDED is a tracked incident state feeding the realization gate / deploy-status / id-rollback. Never issues a mutating tofu apply / destructive prune.

mkdir -p ~/.claude/skills/id-sync
curl -L https://claudskills.com/skills/id-sync/SKILL.md \
  -o ~/.claude/skills/id-sync/SKILL.md

@misc{id-sync-2026,
  author    = {lukasrepublic},
  title     = {Id Sync [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/id-sync/}
}