The rules your work has to follow

Reads a project's own files and existing settings, then suggests rules it can show evidence for — none of which take effect until a person approves them.

Write, change and keep a history of rules, held either as files on your own machine or in a shared library with permissions.

Decides exactly where a rule applies — which files, languages, teams, countries or parts of the business — using one shared way of describing scope.

Lets one rule depend on another, refuses circular dependencies, and marks a rule not-applicable when what it depends on has not been met.

Move a set of rules somewhere else as one bundle, losing nothing, with duplicates and contradictions found before anything is saved.

Rule changes go to named approvers who see exactly what would change, and every decision is kept permanently.

A sealed space to write your own always-the-same check when none of the built-in types can express it.

Build any of the built-in check types by filling in a form, with no rule syntax to learn.

Bring checks written in the programming language you prefer, run in a sealed space with no access to your files, the network or the clock, capped on memory and stopped if they run too long.