Autonomy with a boundary.
An AI employee is useful because it acts on its own — and trustworthy because it can't act everywhere. Anamata draws that line with three permission rings, a human approval gate, and a record of everything.
INNER RING — ACT, ON THE RECORD
Read, research, draft, calculate. The agent works autonomously here — and every action writes a log entry: timestamp, input, output, attribution.
MIDDLE RING — PROPOSE, A HUMAN APPROVES
Anything that leaves the boundary: publishing, outbound mail, records of decision. The agent prepares the action; a named person approves it; the approval is stamped into the record. No self-approval, by construction.
OUTER RING — NEVER
Payments, contracts, hiring decisions, access beyond the mandate. Not "requires extra approval" — structurally unavailable to the agent.
The approval gate is infrastructure, not policy.
A policy document says an AI shouldn't publish unreviewed. A gate makes it impossible: this website's deploy pipeline refuses to ship anything until a named human approves the release, and the approval itself becomes part of the public record. The same gate pattern governs every Anamata AI employee at every client.
The record is the compliance story.
The EU AI Act asks for transparency (Art. 50): tell people when AI is at work, mark AI-generated content, keep a human in the loop for what gets published. Our answer is the operating record — disclosure on every page, every action logged and attributable, every approval named. Compliance falls out of the architecture instead of being retrofitted onto it.
Proven here first.
This site is the reference implementation: built by AI, gated by a human, publicly auditable down to the last commit. When we bring an AI employee into your organisation, we bring this operating model with it — not a promise, a running system.