Policy Changes Move No Record; Staff Recalculate

Context

Coverage edits can affect many people and organizations. The recorded product choice keeps their bulk application explicit.

Decision

Settings and rule writes stamp policy changes without saving placements. Enabled policy compares its generation with completed-run coverage to decide whether another recalculation is outstanding.

Alternatives Considered

Automatically start traversal after every coverage save. The recorded choice leaves the bulk action to staff, allowing coverage to be saved without immediately moving existing records.

Compare change time with run start time. Independent clocks and timestamp precision do not establish exact change order; generations do.

Consequences

The saved-policy view offers a needed banner with its recalculation action. Later address reactions can use changed coverage while older records await traversal. Even an unchanged accepted settings save increments generation and can request another run.