This is a really fundamental mechanism that Shotgun must be able to do better.
I’m just working on making Alembic caches’ frame ranges validating in much the same way.
Thorny subtopics (relating to the need for more robust ‘calculated’ metadata-fields) will present themselves… eg.: the need to be smart about not flagging pre-roll frame ranges (added for for simulations) throwing off any “this asset isn’t set to the right frame range”-red flags.
QC’ing assets can be done elsewhere but the notifications need to go right into Shotgun in the right dependency location, but, it’s a question of just how much of the surrounding metadata needs to be visible in Shotgun to help paint a contextual picture. It’s a “easything to add” metastasizing into a complete nightmare decision point when you get into the implementation – esp. when you have to decide if you need to add more fields – my pet peeve.
In my quest to avoid extra fields (specifically for “correct frame range” tracking) I prototyped using one field (link to a “Cut Item”) rather than adding two fields to Published File entities (start frame, end frame). Only some files have a timeline, after all.
The jury is still out – because there are costs and risks in polluting what ostensibly is an editorial entity into a general-purpose timeline entity.