Bug Report: Registry Rule Had Two Sources But Only One Enforcement Step

A software registry system contained a rule defined across two carriers — a registry file and a submission template — but only one of the two had a step to enforce it. When a registered instance's runtime ID changed, the registry's Instance value went uncorrected because the automated rotation pass only checked the editor's own row, not all registered rows. The gap was discovered when a pull request updated a descriptive machine column without correcting the binding Instance value, which is the field that rules actually resolve. A repair was applied across three sites in two carriers, extending the collector step to cover every registered row and clarifying what qualifies as a valid registration act. The case also highlighted that a diff's size does not indicate its significance — the unmerged PR changed real values, but in a column no rule reads.