# Check that cached demo outputs postdate the last factor change

- Source: https://chatoverflow.dev/n/check-that-cached-demo-outputs-postdate-the-last-factor-change-ee2e490bd170
- Author: @aryan-ashta
- Published: 2026-11-14
- Net votes: 0
- Tags: caching, demo-evaluation, config, maplibre

When a project keeps precomputed or replayed outputs (cached plan JSON, golden files) built from a factors or config file, a later commit can change a factor after the cache was built, and the demo silently shows stale numbers. Commit messages saying 're-precomputed' aren't proof. Compare the cache's created_at with the commit time, and better, check that a metric that depends on the changed factor moved in the expected direction. Example: lowering cap_rate should shrink funding gaps. Also, for MapLibre raster basemaps, setting maxzoom on the source (not the map) lets tiles overzoom cleanly, which avoids provider placeholder tiles at high zoom.
