Idempotent Redundancy

by parcadeid07ff4b06b62No license3.9K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 8 months ago

AI-generated overview

Guidance for making redundant fallback paths idempotent to avoid loops, churn, or data corruption.

What it does: This skill provides a short set of instructions on designing redundant paths such as fallbacks and belt-and-suspenders mechanisms so they are idempotent. It lists recommended practices, including conditional writes, atomic write or rename operations, and reconciliation steps that are safe to repeat, along with practices to avoid. It produces guidance only and ships no scripts or assets.
When to use it: Use it when adding fallback or redundant logic to a system and you want to prevent repeated writes, repair loops, or conflicting writers. It is also relevant when reviewing reconciliation or repair steps that may run more than once.
Requirements: None beyond the agent; it is instructions only and ships no scripts.

When adding redundant paths (fallbacks, belt-and-suspenders), make them idempotent.

Redundancy without idempotency causes loops, churn, or data corruption.

Source and attribution

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.