Production model inventory and owner register
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most teams cannot say, without asking around, how many models are scoring live data today, who owns each one and what decision it feeds. Drift monitoring starts with that list, because a model nobody knows is running is the one that will quietly decay for a year.
First tasks
- List the models you already know are scoring live data, with their owners
- Search schedulers, serving endpoints and the registry for models missing from the list
- Ask each business owner what decision the model's output changes
- Flag ownerless models and agree who decides their future
- Recheck the register against serving logs for new or retired models @recurring(quarterly)