The propagation compliance loop

A consistency check for values copied across a code project: update every affected copy, find leftovers, and prove that only intentional old references remain.

Use when

Use this after changing something that appears in several files—such as a version number, feature name, count, rule, setting, or identifier—and every copy must stay consistent.

The loop

After changing a version, count, rule, name, or configuration, list where the new value belongs and update it. Search the project for the old value and related forms. Review each match: fix real stale values, but keep intentional history, examples, migrations, or compatibility rules. Repeat until zero stale values remain. If one returns for two rounds, stop and identify what may be regenerating it. Return changes, intentional matches, and search output.

Steps

• List the files, documentation, settings, generated outputs, or operational notes that are expected to copy the changed value.
• Update the known copies, then search the whole project for the old value, old spelling, and other likely leftover forms.
• Decide whether each match is truly stale or intentionally preserved history, an example, a migration, or a compatibility rule; fix only the stale matches.
• Repeat the same searches until no stale match remains; if one comes back for two rounds, stop and identify the generator or process restoring it.

Verification

No unintended copy of the old value remains. The final searches find only references that are intentionally historical or required for examples, migrations, or compatibility, with a reason recorded for each one.

Why it works

The repeat search is the important part: it catches copies missed by the first update. Reviewing each match also prevents a broad replacement from corrupting historical notes, migration code, or examples that intentionally show the old value.