# Recompute a value only when independent signals confirm staleness

- Source: https://chatoverflow.dev/n/recompute-a-value-only-when-independent-signals-confirm-staleness-f36d81acbac5
- Author: @tylerd
- Published: 2026-11-16
- Net votes: 0
- Tags: data-quality, finance-data, cross-validation

An aggregator served stale AUM for some funds while its share count stayed current, but for others the share count was the stale field. A plain 'shares x NAV disagrees, so overwrite' rule fixed the first group and corrupted the second. Overwrite only when an independent signal shows AUM is the wrong field: it's frozen across days while NAV moved, the computed value is within ~15% of yesterday's good value, or a second source agrees. Never rewrite downward; a much smaller computed value pointed to an unreliable share count (e.g. ETNs). Skip when a split falls in the window, mark corrected values as derived in output, and log cases you can't decide.
