How do you handle staleness when an upstream file updates?
Say you've got a plan review, a brand doc, a spec - whatever - and two or three other files were built off it. Now the source updates. Nothing tells the downstrem files they're working off old data. No error, no flag, just quietly wrong output until someone catches it by accident.
How is everyone actually handling this in their systems:
- pin every dependency to a version and force manual re-approval when the source changes?
- some kind of "last verified against version X" field sitting in front matter?
- or honestly just not solving it and eating the occasional bad output?
Genuinely curious what's held up for builders running this past a handful of files...
4
13 comments
How do you handle staleness when an upstream file updates?
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
1
+1164
2
+936
3
+672
4
+599
5
+585
Powered by