Идемпотентность и резервные пути выполнения
engineering
idempotent-redundancy is a Claude Code skill that establishes a pattern for safely introducing redundant execution paths — fallbacks and belt-and-suspenders logic — without risking infinite loops, unnecessary churn, or data corruption. The core principle: redundancy is only safe when every step is idempotent. The skill directs Claude to use `_is_merge: true` for Braintrust updates, check for an existing value before writing (falling back only when data is absent), apply atomic write-then-rename for file operations, and design reconciliation steps so they can be re-run any number of times without side effects. It explicitly prohibits unconditional writes in fallback paths, multiple writers overwriting each other, and repair actions that can trigger further repairs. Relevant for any system where resilience is built through redundancy but data integrity under failure and retry conditions is non-negotiable.
- #idempotency
- #redundancy
- #data-integrity
- #atomic-operations
- #error-recovery