Governance
Rules, actually followed.
One catalog of rules, carried everywhere.
Branching, code review, coding standards, decision records, spec-driven development: each is a rule in one catalog, universal or conditional. The rules and the files behind them are carried into every governed repository, and a repository that drifts from them gets a reviewed change that brings it back.
- One catalog of rules, universal or conditional
- Carried into every repository as a reviewed change
- Drift comes back as a change to that repository
Branch protection. No sweet-talking.
Agents open pull requests into the integration branch you name, on GitHub, GitLab, Bitbucket or Azure DevOps. A guard on the machine refuses any push to it or to main, a branch prefix confines the fleet, and switching push off removes the push URL altogether.
- Integration branch, branch prefix and push switch, per project
- Refused at push time, on the machine itself
- Gate commands and standing instructions, per project
Every rule, every repository, one grid.
Every rule against every repository, in one grid: current, behind, drifted, blocked, opted out. An enforced rule that fails is a deficiency, and an agent opens the change that fixes it; an advisory one is reported. Re-read the estate whenever you like.
- Enforced and advisory bands
- A fix opened for what fails
- Re-read on demand
Three reviews. No rubber stamp.
Independent reviewers read the change and the spec: a code review, a security review, and a check against the acceptance items. Blockers are fixed before anything ships, and a change to authentication, credentials, migrations or personal data waits for a person.
- Code review, security review, verification — each its own pass
- Blockers fixed before it ships
- Security-sensitive changes wait for a human
What a governed repository carries
The same small set of files, in every repository.
Every governed repository carries the same small set of files, so an agent finds the rules in the same place everywhere.
- A hub file at the root: the hard rules and a router to everything else
- The policies the rules are made of — branching, code review, coding standards, decision records
- The check script the agents run, and the hooks that run it before every commit and push
- The skills an agent loads for the stack it is working in
Rules, for something that knows better.
Sign up and pick the plan that fits the repositories you would govern first, and the standards they have to keep.