How approval gates work in Kantum.

Most AI tools answer questions. Kantum does the work — and doing the work means writing to your tools: sending a reply, updating a CRM deal, booking an appointment, pushing a code fix. Anything that changes the outside world is a write, and every write passes through the governance gate first.

A write is proposed, not performed

When Kantum decides an action is warranted, it doesn't just do it. It prepares the action — the email draft, the CRM change, the branch and diff — and proposes it for confirmation. The proposal shows you what will happen and the context behind it, so the decision is informed rather than blind.

You decide which actions are gated. Low-stakes steps can run automatically; anything that touches money, customers, or production can require a person to approve first. The line is yours to draw.

A person approves before it lands

Nothing writes without clearing the gate. A teammate with the right role reviews the proposal and approves or holds it. Approvals can reach the right person where they already are — a message, or a call if it's urgent — so a pending action never stalls the work.

• Write actions are proposed for confirmation, never performed silently.
• You set which actions are gated and which run automatically.
• Role-based access controls who can approve what.

Every action is logged

Each proposed and approved action is recorded with who, what, and when — reviewable across the workspace. The audit trail is not a separate feature bolted on; it's how the gate works. If an action happened, there's a record of who let it through.

Why it's built this way

Autonomy without control is a liability. Kantum's premise is governed autonomy: it can run real operations because the controls are part of the product, not an afterthought. Approval gates, audit trails, role-based access, and editable memory are the spine that makes acting on your behalf safe.