Trust / Governance
Authority is granted, graded and revocable.
Every GRABS worker is hired at an authority grade, works through an approval queue you control, signs its work as AI work, and can be stopped in sixty seconds. None of this depends on goodwill: the caps are enforced in code.
The authority grades.
Authority is not a switch, it is a dial, and it is set per worker, per engagement, in the job spec. A team typically starts low and earns its grade across the term, with each step recorded at review.
A0
Supervised
Every output is approved by a named person before release. Nothing the worker produces reaches a customer, a supplier or a system of record without a human signature. This is where sensitive roles start, and where some deliberately stay.
In practice: A worker drafting client-facing letters in a law firm: every draft sits in the queue until a fee earner releases it.
A1
Approved-output
The worker works freely inside its scope, but releases only through the approval queue. It can read, prepare, assemble and reason without waiting, and the queue is the single gate between its work and the world.
In practice: A credit-control worker chasing invoices: it prepares every chase, and anything customer-facing releases through approval.
A2
Autonomous within caps
The worker acts without per-item approval, inside hard limits enforced in code, not by discipline. Spend, scope and action caps are set in the contract and cannot be exceeded, because the code will not allow it.
In practice: A ledger worker reconciling entries below an agreed value threshold: above the threshold, it escalates; below it, it acts and logs.
The approval queue.
Anything consequential passes through an approval queue before it happens: a named person in your business sees the item, approves it, amends it or refuses it. Escalation routes carry exceptions to the right person rather than letting a worker improvise. The queue is reviewed in the Monday Report, so what was approved, what was escalated and what was refused is part of the weekly record.
The disclosure signature.
GRABS workers sign their work as AI work. Output carries a disclosure signature, so a reader always knows an AI worker produced it and which one. Every action is logged and attributable to a named worker identity, never a shared login, which is what makes the audit trail an audit trail rather than a log file.
Sixty-second revocation.
The final governance control is the simplest: the team can be sacked in sixty seconds. Access is revocable at once, caps are enforced in code, and there is no notice period and no negotiation. You are never trapped in an engagement that is not working, and that fact disciplines everything above it.
The Governance Pack
The controls, written down for your compliance team.
The Governance Pack sets out the authority grades, the approval queue, the disclosure signature, the logging model and the revocation mechanics in the language a compliance function expects. Leave your email and we will send it over.
Request the Governance PackSee governance running before you buy.
The proving ground shows every internal engagement running with full ceremony: job specs, Monday Reports, reviews and attestations.
See the proof