Evidence-backed rules
Every rule ships with dangerous and safe-lookalike fixtures; lock and rewrite claims are validated empirically against Postgres 13–17 in CI.
A rule is not merely an opinion about SQL. Each one ships with fixture migrations in both directions: dangerous variants that must fire and safe look-alikes that must stay silent. A rule without both halves does not merge.
Claims about locks and rewrites are checked against a real server, not documentation. CI runs the fixtures on Postgres 13 through 17 and asserts the lock actually taken and whether the relation file changed, so “this rewrites the table” on a rule page is a measured fact on every supported major.
Why it matters for AI-written SQL
Migrations increasingly arrive from a model that has read every blog post and none of your traffic. A verifier that is itself a guess adds nothing. Evidence-backed rules are what let Bolvrk sit as the deterministic judge in a bring-your-own-AI loop.
The CLI is open source and needs no account: npx bolvrk check migration.sql
Also in Deterministic rule engine
- Postgres migration safety checks
- Real parse-tree analysis
- Severity taxonomy
- False-positive discipline
- Fuzz-tested boundaries
- A corpus of 69 rules
- Credential rules: no secret ever reaches the repo
- Secret scanning for any file: bolvrk secrets
- Performance rules: indexing and query health
- Query verification: bolvrk explain