Propagate a value everywhere it lives

Update every copy of a changed value across the project, hunt down leftovers, and prove only intentional old references remain.

Use this 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.

How it runs

1. List the files, documentation, settings, generated outputs, or operational notes that are expected to copy the changed value.
2. Update the known copies, then search the whole project for the old value, old spelling, and other likely leftover forms.
3. Decide whether each match is truly stale or intentionally preserved history, an example, a migration, or a compatibility rule; fix only the stale matches.
4. 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.

Done when

✓ 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.

Implementation note

The exact files depend on the change. The original submission used several operational notes and procedure files; another project might need code, tests, documentation, deployment settings, generated files, or all of them.

Source: Forward Future ↗graded C · 65/100 — how grades work →

More maintenance loops