Skip to content

Guardrails and limits

Our forward-deployed engineers build every agent inside the same guardrails from its first day: limits, permissions, an audit trail and a stop switch. This page covers the limits, the permissions and the stop switch, and lists what agents never do.

The audit trail has its own page. It and the stop switch come from our reusable tooling. The limits and the permissions are written for your workflow.

Limits are the bounds on what an agent may do. There are three kinds.

Kind of limit What it bounds Examples
Amounts How big a single action may be A ceiling on the value of an order. A tolerance on the difference between an invoice price and the purchase order price. A maximum quantity on an inventory adjustment.
Customer and supplier lists Whose work the agent may act on by itself The customers whose orders it may enter. The suppliers it may send follow-ups to.
Time windows When it may act Supplier emails only during business hours. No write-backs to the ERP during month-end close or a physical inventory.

Five rules apply to every limit.

  1. Limits are written down before a level starts, next to the threshold for that level. The figures are set for each workflow with the workflow owner, which is why none appear in these docs.
  2. The operations layer enforces them, not the agent. Our engineers build each limit in as ordinary software, the same kind of check that tests an order against a credit limit. The check runs before an action is carried out. It does not depend on the AI model following an instruction.
  3. A case outside the limits is not dropped. It becomes an exception and goes to a person, with the reason stated.
  4. A limit changes only with the workflow owner’s sign-off. Every change is recorded with who signed it off and when. An agent cannot change its own limits.
  5. Limits are not a way around a promotion review. The level sets what kind of work the agent does on its own. The limits set how much of it. More autonomy takes a review.

An agent has only the access its workflow needs.

  • An agent that enters sales orders can read customers, items, prices and credit status, and it can create sales orders. It cannot change a price list, raise a credit limit or see purchasing.
  • An agent that matches supplier invoices can read purchase orders and receipts, and it can enter invoices. It cannot create a supplier, change bank details or release a payment.

Each agent has its own service account, so your ERP’s own history shows which transactions an agent made. Your IT team creates that account and can disable it at any time, which cuts the agent off from the ERP whatever else is happening. Access and credentials covers how these accounts are set up and removed.

When an agent sends email, it sends from an address your IT team sets up for that workflow, under a name and signature the workflow owner decides.

Permissions and limits do different jobs. Limits bound what the agent may do inside its workflow. Permissions make everything outside its workflow impossible, whatever the agent attempts.

The stop switch halts an agent at once. The emergency stop on a machine is a fair comparison. It is in plain sight and it works immediately. Using it is never the wrong call, and restarting takes a deliberate step.

Every stop switch is built to do the same five things when someone uses it:

  1. The agent takes no new work.
  2. Work it had started but not yet written to the ERP is held for a person.
  3. The queue stays where it is, and your people work it by hand.
  4. The stop is recorded: who used it, when and, if they say, why.
  5. The agent stays stopped until the workflow owner, or the deputy the owner has named, restarts it.

The workflow owner decides who can use the stop switch. The list includes the people who work the queue every day, because they are the first to see something going wrong.

Each workflow owner names a deputy who can do everything the owner can. That includes restarting a stopped agent and signing off a change to a limit.

A stop does not undo transactions the agent completed before it. If some of them are wrong, the audit trail shows which ones, and they are put right in the ERP.

The stop switch is not the only control. The workflow owner can also move the workflow down a level.

Stop switch Move down a level
What it does Halts the agent. People do the work. Keeps the agent working with less autonomy, for example back to a person approving every transaction.
Who can do it Anyone the workflow owner has named The workflow owner
How fast At once At once
What it takes to undo The workflow owner or the deputy restarts the agent A promotion review
  • Physical work. Agents do not pick, pack, count or move material, and they do not operate machinery. The autonomy ladder applies to fully digital work only.
  • Anything outside their workflow. An agent built for order entry does not answer an AP question because someone asks it to.
  • Change their own limits or their own level. Both belong to the workflow owner.
  • Approve their own work. Where a transaction needs an approval, the approval is always a person’s.
  • Write to the ERP by a route the ERP does not support. Every write goes through the operations layer. See Attaching to your existing ERP.
  • Act without a record. Every action goes into the audit trail with its inputs, its decision and its result.