A model-backed check should not block a merge on day one. Give it three rungs, a ledger, and a promotion rule, and it will eventually tell you whether it deserves that authority β with data instead of opinions.
Teams usually pick one of two bad defaults. Either the model runs as a comment bot nobody reads, or it gets wired straight into a required check and the next month disappears into flaky red Xs. This post is the middle path: a CI/CD integration where hooks, fixtures, and flake control decide when a model check graduates from advisory to blocking.
The ladder at a glance
Each rung has a different job, a different cost profile, and a different exit criterion. You move up only when the rung below is boring.
Rung Where it runs Blocking?β¦