Canada’s guide on agentic AI, mapped line by line.
The Government of Canada published its Guide on the Use of Agentic Artificial Intelligence on 15 September 2026. Six of its points concern what an agent may do and what is recorded. For each: what Ares does today, what needs configuration, and what it does not do.
Six points, six answers.
Points are paraphrased from the guide. Read the guide for the exact text.
A review step before an agent changes the state of a system
- State
- Needs configuration
- What Ares does
- Workflows put a person on the steps you name. The step waits until that person approves or rejects it. Separate rights control who may create, change and run a workflow.
- What the record shows
- Who was asked, what they saw, what they decided, and when. Approvals and rejections are both on the record.
- What remains yours
- Deciding which actions change state in your systems and need review, and naming the reviewers.
Logs kept in a system the agent cannot change
- State
- Does today
- What Ares does
- Every decision is written to the record as it happens. The agent does not choose what is logged. Each decision is confirmed by more than one party before it is written, and nobody, the agent included, can quietly edit the record.
- What the record shows
- Every decision, refusals included. Your administrators export a job as a replay pack, and your auditor checks it offline with ares-verify, without us.
- What remains yours
- Setting how long the record is kept, and who in your organisation may read it.
A clear identity for every agent
- State
- Does today
- What Ares does
- Every agent is enrolled with its own identity, from your directory. Ares is Entra ID native; other directories are on request. No agent shares an account with another.
- What the record shows
- Which agent acted, for whom, under which credential, at every step.
- What remains yours
- Keeping your directory accurate, and retiring agents you no longer use.
Read-only access by default
- State
- Needs configuration
- What Ares does
- An agent can do only what its access policy allows, for that job. You write the policy, so an agent reads and does not write until you grant more. Calls outside the policy are refused.
- What the record shows
- Every refusal, with what was outside permission. Every change to a policy.
- What remains yours
- Writing read-only policies for new agents, and approving each grant of write access.
A way to stop an agent from outside the agent
- State
- Does today
- What Ares does
- Your administrators revoke an agent in Ares, not in the agent. Revoking a credential ends every credential derived from it, including in the middle of a job. Every call after that is refused.
- What the record shows
- Who revoked what and when, and each call refused after it.
- What remains yours
- Deciding who may stop an agent, and when they should.
Text from outside treated as data, not as instructions
- State
- Needs configuration
- What Ares does
- Inbound content is read at the door before the agent sees it. Filters catch hidden instructions and redact what you name. Filters cover stated patterns and languages, and you choose which filters run.
- What the record shows
- Each hidden instruction caught and each redaction, with the filter that fired.
- What remains yours
- How your agent and its model handle the text that passes. Ares does not change how a model reads its input.
Paraphrased from the Government of Canada Guide on the Use of Agentic Artificial Intelligence (15 September 2026). Six points only; the guide covers more. Not legal advice.
Reading the states
Three rows work today with no extra setup: the record, agent identity and the outside stop. Three need configuration, because the guide leaves the rule to you: which actions need review, what an agent may read and write, and which filters run on inbound text. Ares enforces the rule you set, and records every decision made under it.
This page maps six points of the guide. Read the guide itself for the rest. For defence and government programs, see defence and government.
What this page is not
This page maps Ares features to a published framework. It is not legal advice, and it does not certify compliance. Your obligations depend on your system, your role and your jurisdiction; check them with your counsel.
What it does not do
- Ares does not decide which actions need review. You do.
- It does not change how a model reads text. It inspects the text before the agent sees it.
- It does not certify that your use of agents follows the guide.
Take the mapping into your review.
Tell us about the workflow under review. The architecture and security brief covers the architecture, the data flows and how the record is protected, at the depth these pages leave out. We send it after a short NDA.
A senior member of the team replies within two business days.