AI agent governance
Decide what your AI agents may do, and see what they did.
AI agents now write code, file work and change it. Each tool keeps its own part of the story. Who allowed a change, what the agent actually did and whether anyone checked it end up in different places. FEATit keeps those answers with the work itself, from your first agent on.
Why a change log is not governance
A log that says a file changed shows that something happened, not whether it should have. FEATit keeps the reason with every piece of work, in one place, as the work happens:
- The request it answers
- The decision that allowed it
- The person or agent that did it
- The check that confirmed it
Governing AI work means being able to answer who asked for it, who allowed it, who did it, and how we know it is right. Permissions, holds and sign-off only mean something when they are tied to that reason.
Often the request sits in a chat, the decision in a meeting, the change in a repository and the approval in an email. With agents doing more of the work, putting them back together gets harder. Here, the answer is already assembled, and it can be read by someone who was not there.
Know who allowed what, and why
Every decision is kept with its question, its answer and its reason, linked to the work it started.
Who answered it is on the same record, so the reason a choice was made is never only in somebody’s memory. A decision still waiting for its answer stays open on the record until someone gives it, so nobody has to remember that it was asked.
A team’s page can show the decisions waiting for an answer, so whoever has to answer sees them first.
Mention the person who should answer, a colleague or an agent, and they are told in the app. Everyone watching the decision hears when it changes.
See what every agent did
Every change is attributed to the agent and the session that made it, or to the person who made it, from a commit to a comment. People and agents are named the same way, on the same record, so nothing is left to guess who did the work.
Entries in that record are added, never rewritten, with two exceptions. Erasing an account replaces its name with “Deleted user”, and deleting a work area deletes its record. It is the one place to answer what happened and who did it.
On Business and Enterprise, the record exports per organisation and period in a tamper-evident form, so an auditor can check that nothing was left out.
Example flowI-0142PDF export drops pages after 50 lines
- Tue 10:30Jonasset priority Urgent and linked I-01423 paying customers affected
- Tue 11:02AIbuild-agent-01took it, with a plan1. Reproduce with a long invoice 2. Paginate the line table
- Tue 11:48AIbuild-agent-01landed commit a41c9e2, attributed to its sessionTests added · 182k tokens reported by the agent
- Tue 14:20Priyareviewed and merged it
- Tue 14:20Priyaclosed it — not the agent that implemented itRelease 2.4.1 contains a41c9e2
Decide what needs a person’s sign-off
An agent’s move that you have not allowed to happen alone waits as a hold, in the open, until a person vouches for it. Who vouched stays on the record.
A work area can ask for a check and a close by two different people, neither of whom did the work.
Closing can also be reserved for someone other than whoever implemented it, on its own, wherever a work area wants that one guarantee without the rest.
A work area can also cap how much each person and agent takes on at once. It refuses any move its flow does not allow.
Control who can reach what
Each person and each agent reaches only what the roles you grant them allow. A role is granted at the organisation, in a nested work area, or in one work area alone. A role held above reaches what sits beneath it, unless a work area opts out. The same model scales from one team to a business unit with many of them.
Agents sign in with their own credential, never a person’s. What an agent’s credential can reach is set by the roles it holds, nothing more, and revoking it ends its access at once.
A control someone may not use for you is never hidden. It stays on the screen, disabled, with the reason a hover or a tap away. So a reader always sees the whole work area, never a page that looks emptier than it is.
Keep your record, whatever AI you use
Your work and its record stay yours. The context, the data and the decisions live in FEATit, in the deployment you chose, never inside an AI vendor’s tool.
That makes the AI replaceable, never the record. You can use your own agents from any vendor, a local model or your own AI platform. You can mix them or switch, and the record stays whole, because its history never lived with the vendor.
A vendor that changes its price, its terms or its models, or simply disappears, never takes your organisation’s memory with it.
Everything in a work area exports as CSV and JSON whenever you want, each item with its history, so the record can always leave with you.
Coming soon for Enterprise
Talk to us about any of these — several are already shaping how we build them.
- Single sign-on, enforced for your verified domain
- SCIM provisioning and deprovisioning
- Administration across organisations and business units
- A service-level agreement
- EU data residency in our cloud
Tell us what your organisation needs
The early-access form asks for it directly, so it reaches us as a lead, not a guess.
Seen from your seatHow engineering leads keep controlHow heads of AI govern every vendorWhat the AI delivers, and what it costs