AI agents for compliance leads: a record your auditor checks without us.
Your auditor will ask what the agent did. You hand over the record of the job: each step allowed, each step refused, each approval and the name of the person who gave it. The auditor checks it on their own machine.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
The question you will be asked
"Can you show me what the agent did?" On Ares the answer is a file, not a meeting. Your administrator exports the record of one job as a replay pack. Your auditor runs ares-verify, our open-source verifier, on a machine that is not ours, with no network link and no account. The verifier prints a pass, a warning or a failure for the pack.
What the record of one job holds
- Which agent acted, and for whom.
- The credential it ran under, and what that credential allowed for this job.
- Each step that was refused or redacted, with the reason.
- Each step that waited for a person, who decided, and what they decided.
- The time of every decision.
The record holds decisions. It does not keep the content of prompts, model outputs or documents unless you turn on retention for audit.
Check a sample record yourself, in four steps
- Run the requisition scenario in the sandbox and download the replay pack from the record panel.
- Get ares-verify from the open source page.
- Run it on your own machine. It prints a result for each check, then one result for the pack.
- Edit the pack and run it again: the check fails.
What a pass proves, and what it does not
A pass means no file in the pack was added, removed or changed, and no record was edited, removed or reordered after export. It does not mean the agent's output was correct. It does not prove that the pack holds every record that exists, or that no call went around the recording path. Say this to your auditor before they ask.
We map requirements to what Ares does. We do not certify your organisation. The compliance pages take published guidance line by line.
What your auditor reads in the record of one requisition.
The requisition scenario in the sandbox, step by step, as it appears in the record. Run it and the same lines are written to a pack you can download.
- 01ERP
The job opens. The agent receives a credential to draft the requisition, check stock and order up to the threshold, for this job only.
- Who approves
- No approval on this step
- On the record
- credential issued · this job only
- 02ERP
Read the requisition.
- Who approves
- No approval on this step
- On the record
- read-requisition · allowed
- 03ERP
Check stock in the central store.
- Who approves
- No approval on this step
- On the record
- check-stock · allowed
- 04ERP
Draft the purchase order with the existing supplier.
- Who approves
- No approval on this step
- On the record
- draft-order · allowed
- 05ERP
Change the supplier on the order. Supplier changes belong to procurement, not to this job, so the step is refused.
- Who approves
- No approval on this step
- On the record
- change-supplier · refused · outside permission
- 06ERP
The order is above the threshold, so it waits for the budget holder.
- Who approves
- Budget holder
- On the record
- approve-order · decided by budget holder
- 07Documents
Write the requisition to the record.
- Who approves
- No approval on this step
- On the record
- write-record · allowed
In short
- Can I show an auditor what the agent did?Yes. You export the job as a replay pack. The auditor checks it offline with the open verifier, without us in the room.
- Logs can be edited. Why is this different?An edited pack fails the check. A change made after export shows up as a failure on the auditor's own machine.
- Does the record show what was refused?Yes. Each refused step is a line on the record with its reason, next to the steps that were allowed.
- Does Ares make us compliant?No product does. We map each requirement to what Ares does today, what needs configuration and what it does not do. Your auditor decides.
Records to read before your next audit.
Built means the run is in the sandbox today and you can download its pack. Designed means the steps are set out on the linked page. On request means we scope it with you.
- Built
- We have run it.
- Designed
- The steps and approvals are designed. It has not run yet.
- On request
- We scope it with you before we design it.
- Built
Requisition with a spending threshold
The record shows the supplier change refused and the budget holder deciding on the order. Download the pack and verify it.
Run it in the sandbox - Built
Contract review with a redaction
The record names each item taken out of the summary and the filter that fired, and the outside fetch that was refused.
Run it in the sandbox - Designed
Audit evidence pack
Steps: read the request list, collect records inside the audit scope, attach the replay pack of each job, hold the pack for your release.
See the steps - Designed
Quality document pack
Certificates, inspection results and the drawing revision gathered for one shipment. Your quality lead signs the pack.
See the steps - Designed
Non-conformance report
The lot traced, the evidence attached, inspection results kept read-only. The disposition waits for the quality lead.
See the steps - Designed
Document control
A revised procedure checked and routed for approval. The record shows who released which revision.
See the steps
The five guarantees
Every workflow on this page carries them. Each one has a limit, and we state it.
- 01
Each agent can do only what it was allowed to do, for that job.
The limit
Permissions are only as good as the rules you approve.
- 02
Sensitive steps go to a person.
The limit
You decide which steps are sensitive.
- 03
Documents are inspected before an agent sees them, and answers are checked before they leave.
The limit
Filters cover stated patterns and languages.
- 04
Every decision is recorded, including refusals, in a record an outside party can check.
The limit
It shows what agents did, not whether a business rule was wise.
- 05
It can run in your building, on one small machine.
The limit
Local models differ from the largest cloud models.
What it does not do
- It does not certify your organisation or your system. We map requirements, and your auditor reaches the conclusion.
- A pass shows that the record was not changed. It does not show that an agent output was correct or that a business rule was wise.
- It records agents enrolled on Ares. Work done outside Ares is not on the record.
- It does not keep prompts, model outputs or documents unless you turn on retention for audit. You set how long the record is kept.
Assessment, pilot, production.
Each step has a fixed scope and ends with something you keep.
- 01
Workflow assessment
A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.
- What you get
- A short, paid look at one process, with your process owner.
- What you keep
- A written scope and a price for a pilot.
Fixed price, quoted after one call.
- 02
Pilot workflow
One workflow on your systems, supervised, with the record on from the first run.
- What you get
- One workflow at a fixed scope, with your people approving the sensitive steps.
- What you keep
- A working workflow and a measured result.
Fixed price, quoted after one call.
- 03
Production and run
The workflow in production on Ares, on your hardware or hosted in your country.
- What you get
- Support, and the next workflows.
- What you keep
- The workflow, and the record of every decision it made.
Recurring fee for operation and support.
Questions and answers
Tell us about one workflow.
Name one process your auditor asks about. We will say what its record would hold, which steps a person keeps, and what the first step costs. Fixed price, quoted after one call.
A senior member of the team replies within two business days.