An approved-models registry nobody has to sneak around

Every time this conversation starts, someone proposes a monitoring solution: scan the downloads, keyword-watch the model names, catch the bad ones after they’re already in the building.

That’s a police camera. It races the user, and it loses — model names are trivial to mirror, rename, or bury.

The better architecture is a gated model registry: the company talks to zero model shops directly, because everything goes through our approved catalog. If it’s not on the shelf, it can’t get in.

The rules that make it work

• SSO is identity, not access control. It confirms “you’re an employee,” not “you get to see 5 models and Steve gets 8.” Approved = approved, for everyone.
• Enforce at intake, not at the edge. One permanent gate where we vet, pin the revision, and hash the files. No chasing.
• Enforce in the serving layer, too. The platform that loads models refuses anything unsigned. Even a careless engineer can’t serve an unvetted model.
• Give security the audit log, not the keys. They get full visibility; they don’t get to throttle the pipeline.

Build the wall and you don’t have to watch the gate. That’s the whole pitch.