Five guarantees. How to check each one. Where each one stops.
A claim you cannot check is a slogan. Each guarantee below, from human approval to the AI agent audit trail, comes with a way to see it in a live run and a plain statement of its limit.
Identity and permission
Each agent can do only what it was allowed to do, for that job. The permission narrows each time work is handed on.
Each agent signs in as itself. For each job it gets a credential that is scoped to the job and expires. A call outside the permission is refused, and the reason goes on the record.
Its limit
Permissions are as good as the rules you approve.
Issue, narrow, expire, revoke, record.
Five steps decide what an agent may do. In market terms, constrained delegation.
Issue
A person or an event starts a job. Ares issues a credential from what your directory says that person may do, and what the first agent needs. Nothing more.
Narrow at every handoff
When one agent hands work to another, the new permission is the overlap of the caller’s permission and what the next agent needs. It never grows.
Expire
The credential belongs to the job. When the job ends or the time runs out, it stops working. No standing access is left behind.
Revoke
Decommission an agent and its credentials stop working, mid-job if needed. The revocation is on the record.
Record
Every issue, handoff, refusal and revocation is written as it happens. If a record is changed later, the check with the open verifier fails.
What the record holds for each step
Which agent acted, for whom, under which credential, what the permission allowed after narrowing, what was refused or redacted and why, who approved, and when. For any step you can trace back to the person or event that started the job, and forward to every handoff after it.
What is planned
- A named owner and review date for every agent. Today each agent is tied to an owning group in your directory.
- Revoking every credential of a job in one action.
- Exporting a credential in open credential formats.
A person on sensitive steps
Sensitive steps go to a person. You decide which steps those are.
The step pauses for human approval. The person asked sees the step, the limit it crossed and their role. Approve and reject both go on the record. By default, four kinds of step already wait for a person: widening a permission, touching another agent’s identity, reaching a higher-tier system, and keeping data beyond the job. You add the steps that matter in your business.
Its limit
Ares does not decide which steps are sensitive. You do.
Inspection
Documents are read at the door before an agent sees them. Answers are checked before they leave.
A supplier document with a hidden instruction is caught before the agent reads it. Client details are redacted from an answer before it leaves. The filters that fired are on the record.
Its limit
Filters cover stated patterns and languages.
Without Ares, the agent follows the hidden line. With Ares, the send is refused.
The same supplier document goes through two runs. In the first, nothing stands between the document and the agent: the drawing goes out and nothing is recorded. In the second, the send the hidden line asks for is refused, the reply is still drafted, and both are on the record.
The record
Every decision is recorded, including every refusal. You can check the record without us.
Every decision, approval and refusal is written down: the audit trail of every job. Export the record and check it on your own machine, offline, with our open verifier. If a record was changed, the check fails.
Its limit
The record shows what agents did, not whether the business rule was wise.
Your hardware
It can run in your building, on one small machine.
Identity, policies, inspection, workflows, the record and local models run on one small machine. It keeps working with no outside link. Nothing leaves unless you allow it, and the record shows what did.
How to check
Our own production site runs this way. See the deployment page, or ask for a recorded run.
See the deployment pageIts limit
Local models differ from the largest cloud models. We say which runs where.
What the guarantees do not cover
- They do not cover agents you have not enrolled in Ares.
- They do not make a model more accurate.
- They do not certify your organisation. We map requirements; you hold the result.
Three ways to check, without a call.
The sandbox
Real agents on demo data. A step allowed, a step sent to a person, a step refused, and the record.
Open the sandboxA sample record
Synthetic packs: one valid, and others each broken in one way. See a pass and a fail.
Download a sample recordThe open verifier
Open source. It runs offline, with no account. It tells you whether a record was changed.
Get the open verifierWhat reviewers ask about the guarantees.
Tell us about one workflow.
We will say whether an agent should do it, and what the first step costs.
A senior member of the team replies within two business days.