Team policy: block on critical
Platform teams pick the severity that fails CI, critical only, warning and above, or any finding, and tune or silence any rule from the dashboard. On Team and above the policy governs every connected check, CI, bolvrk check --remote and the API alike.
Team policy is one place to decide what fails a build. The block threshold, critical only, warning and above, or any finding, and per-rule overrides that re-rank or silence a rule. It is set on the dashboard and applied by the hosted service to every connected check: CI, bolvrk check --remote and the API alike. It is never read from a file a commit can change; a rules block in bolvrk.json is refused.
bolvrk policy pull copies the block threshold into bolvrk.json so a local run blocks on exactly what CI blocks on.
Repository ignores are the other lever
A house-style rule a repository has decided against belongs in that repository’s ignore map, with a reason. Team policy is for the decisions a platform team wants applied everywhere; the ignore map is for the ones that belong with the code.
The CLI is open source and needs no account: npx bolvrk check migration.sql