Home/Platform/Governance
Governance

One governed engine

One catalog of agents, skills and documents for the whole organisation. Every piece of work runs through it.

Wakalix governs AI coding agents from one catalog that decides which agents exist, what each may touch per repository, product and person, and when a risky step must wait for a named person; every new agent version is evaluated before teams get it.

Transcript

One standard, every team. How Larkfield keeps its code consistent when everyone has their own coding agent.

A year on, Larkfield has three teams, in Madrid, Kraków and Pune, and fourteen developers.

Each one works in their own coding tool: Claude Code, Codex, Copilot or OpenCode. Claire wants one way of writing code, not fourteen.

Lukas, the architect, writes a standard once, for the whole organization.

A person checks it in every review. He takes it, and it is in force at once.

Every decision in force goes into the work each agent is given, with the reason it is there. Here it is for Priya, in Claude Code.

And here is the same work packet for Ana, in Kraków, who works in Codex. The same decisions, in the same words.

Every repository also carries the organization's own rules, for whichever coding tool opens it. One upgrade brings a checkout up to date.

Every team uses the same agents, at the same version: the developer agent at version eighteen, the reviewer at nine.

Their tests run here, so everyone can see that every skill still passes.

The reviewer agent checks each change. This one broke the new standard, so it went back with a note saying what to fix.

The next attempt read the note and fixed it, and this time the review passed.

Upkeep reads the notes people leave. Reviewers in three teams sent work back for the same reason, so it proposes a new standard.

Lukas reads what each reviewer said, and keeps it as a standard.

He applies it, and agents read it from their next run.

Decide once, and every agent, in every tool, on every team, works to it. That is Wakalix.

Fine-grained access

Per repository, product, person and agent.

Risk stops and asks

Risky steps wait for a named person to decide.

Tested before use

Every new agent version is evaluated before teams get it.

Questions

What is AI agent governance?

One place that decides which agents exist, what they may touch, and when they must ask a person.

How do I stop agent sprawl?

One shared catalog instead of a private set per developer.

Read more