A corrected asset doesn’t become trustworthy because its filename sounds final.
It becomes trustworthy when the correction has a home in the record it changed.
final-two can sit beside final-really-final for years. Both names look careful.
Neither tells the next editor which caption, image, or clip governs the next post.
The problem isn’t untidiness.
It is competing authority.
So give the asset one identity before you give it another filename.
A persistent identifier stays with the work when the filename changes, when the slug changes, when the whole site moves.
The public address may change. The record shouldn’t.
Then separate the three things a crowded folder makes look identical.
The master is the authoritative original, and it is immutable. Not overwritten, not cropped, not colour-corrected and saved on top of itself.
A version changes the content. A retouch, a replacement image, a caption correction: the source itself is now different.
A derivative changes the use, not the content. A web JPEG, a print file, a thumbnail, a square crop, all from the same approved asset.
The words sound close. The decisions aren’t.
Treat a generated thumbnail like a content edit and ordinary work grinds.
Treat a content edit like a thumbnail and a changed asset slips past review.
The relationships differ too.
A derivative stays linked to the master and inherits what the master permits.
A version stays linked to what it superseded.
One says: this is the same work, for another use.
The other says: this is the work that replaces what came before.
So don’t make a correction by exporting another crop and hoping the crop’s name explains it.
Check the asset out.
A check-out lock gives one editor an exclusive hold, which is what stops a second save from quietly competing for the same version.
Check it back in as a new version.
Keep the prior version with a pointer to what replaced it.
Months later the record can still answer which image ran in the autumn catalog — and that question is asked far more often than anyone plans for.
For a substantial change, keep the work on its own branch, linked to the same identity.
The live version stays live. The corrected caption or replacement image can be examined without an unfinished edit becoming the public record.
Number the result honestly.
A typographical fix leaves the version where it was. A change to a factual claim, a figure, or a procedure earns a real bump.
Though the number isn’t the authority.
Status is.
Draft, approved, superseded: those three words tell a creator what can move forward. A timestamp never could.
Which is the whole point of the system.
Generate the next thumbnail, social crop, or proxy only from the version marked current and approved.
Not from whatever was open.
And don’t treat version history as a bin for every duplicate you were afraid to delete.
Most systems keep a bounded number of revisions and prune the oldest.
Preserve the baseline and the decisions that explain the present, and the pruning stays harmless.
Keep the master.
Keep the lineage.
Keep the reason the change happened, in the place the change happened.
The correction may be very small.
Its relationship must not be.
A version is not another file. It is a statement about which file now governs.