Time spent finding the final version of something is pure loss. It appears on nobody’s timesheet, it is nobody’s job, and across a team it is hours a week.
A convention only works if a script applies it. A convention people are asked to follow is a convention that holds for a fortnight and then degrades into six dialects and a folder called final-v3-USE-THIS.
The fields worth encoding: client, project, asset type, variant, ratio, version and date. Sortable, greppable, and unambiguous six months later, which is the only test that matters.
What is the highest-return thing to automate in a content team?
File naming and versioning. It is pure overhead, it is invisible on any timesheet, and a script removes it permanently.
Why not just ask people to follow a convention?
Because conventions applied by humans decay into dialects within weeks. One applied by a script does not.