Your AI, safe and well governed.
Proof, not promises.
We write the rules for your AI with you, test it before it goes live and keep it under control once it runs. At every step, you get evidence your auditor can re-examine.
Three situations, three ways in.
You have no written rules yet.
Your teams already use AI, with no policy and no register. In 90 days you have a one-page policy, a register of your uses and a first case tested.
Ready to govern→An AI system has to go live.
An assistant, a copilot or an agent is stuck in pilot, or a bank, a client or a regulator is asking for evidence. We test it adversarially and hand you its evidence file.
Under test→Your teams already hand data to AI.
Names, card numbers, secrets: they leave in the AI tools your teams use. We have them masked on the device, before they leave it, in supported tools such as Claude Code, Codex and Cursor, and we set the rules of use.
Talk to us→Rules on one side, safety on the other. Each holds the other up.
Governance
What are our rules, and who decides?
- A one-page policy, written with your teams
- A register of your AI uses, with risk tier and next review
- Roles: who approves, who watches, who answers
- Mapped to the texts that apply: AMF, OSFI E-23, Quebec Law 25, ISO/IEC 42001
AI safety
Does our AI behave as intended, and can we prove it?
- Before and after go-live: adversarial testing, an evidence file, a new test at every change
- Sensitive data: masked on the device, before it leaves
- Guardrails: what goes into your AI and what comes out is checked and put to the test
- Local first: the controls run on your devices, with the ProofAgent platform
A written rule → a test → a guardrail → evidence in the register.
This is no longer a matter of principle. It is a date.
The Autorité des marchés financiers' expectations on artificial intelligence governance take effect for the institutions it supervises.
— months left
Guideline E-23 on model risk management takes effect — AI models are explicitly in scope.
— months left
An agent already running on the day the rules take effect will have to be documented retroactively, on behaviour that was never measured. Testing before production costs a fraction of reconstructing it afterwards. Dates to be confirmed against the text in force at the time of your engagement.
The Agent Deployment Proof File.
A productised, repeatable deliverable, built to hold up before a regulator, a board or a risk committee — and to be re-examined piece by piece by your own auditor.
Does not constitute an assurance or audit engagement in the regulatory sense.
- Findings report linked to timestamped traces
- Documented replay set (attacks, configurations)
- Re-verification protocol for your auditor
- Findings mapped to applicable frameworks
- Re-verification workshop with your teams
90 days to be ready to govern your AI agents.
We wrote our method down in a book, 90 Days to AI Agent Governance Readiness, co-written with the founder of ProofAgent: twelve steps in four stages — see, decide, write, run — to go from improvised policy to written rules, tested on a first agent. It is the path we walk with you.
We've built — and governed — our own agents.
DocFlow is a tool we designed, built and put into production for Quebec's notarial profession — a field where rigor and traceability are not optional.
We know where agents break because we've built them. It's our proof of competence — not a client, not a demo that "our governance works".
docflow.ca
- Document automation — Quebec notarial sector
- In real-world use, on real files
- Designed, built and governed by us
We train your teams to govern agentic AI.
Beyond the file: we make your teams autonomous. Understand the risks specific to agents that act — and learn to govern them.
AI governance fundamentals
The frameworks (ISO 42001, NIST AI RMF, EU AI Act, AMF/OSFI), roles and responsibilities, and what separates defensible evidence from policy on paper.
Agentic system risks
What changes when an agent acts: tool use (MCP), privilege escalation, agent-to-agent coordination, agent identity, and red-teaming.
Test and defend your agents
The method in practice: adversarial evaluation, decision gates, building a proof file, and engaging an auditor or regulator.
What people ask us before we start.
What is AI agent governance?
It is the set of controls, guardrails and evidence that lets an organisation answer "yes" when asked whether it has a grip on an AI that acts: an agent that calls tools, triggers transactions or decides without a human validating every step. Governing an agent is not just an AI usage policy: it has to cover the agent's privileges, its tools, human oversight, traceability, and the evidence that it was put to the test before going into production.
What is an agent deployment proof file?
It's our core deliverable: a documented file gathering the agent's scope, the adversarial attacks we ran against it, execution traces, findings linked to those traces, decision gates (pass / review / block) and the mapping to applicable frameworks. The key point: it is built to be re-examined by your own auditor, not merely read. Reproducibility is partial and stated as such — we document what can be replayed and what cannot.
Do you certify or guarantee my AI agent's compliance?
No, and that's deliberate. Nobody can guarantee the behaviour of a probabilistic system. What we produce is defensibility: evidence that lets you justify your decisions to a board, an auditor or a regulator. Our work does not constitute an assurance engagement or an audit within the meaning of professional standards, and we are not a certification body — independence comes from your organisation's own auditor, who can re-examine the file.
Which frameworks do you work from?
Depending on your sector and exposure: the AMF's expectations in Québec, OSFI Guideline E-23 on model risk management, ISO/IEC 42001 and 42005, the OWASP Agentic AI Top 10, the NIST AI Risk Management Framework, and the EU AI Act where it applies. We don't sell a framework: we establish with you which ones apply, then map every finding in the file to the corresponding requirements.
When should you bring us in?
Before production, while the agent is still in pilot — that's when findings are cheapest to fix. We also step in on agents already in production when a regulatory deadline, a risk committee or an auditor calls for evidence — and at every material change afterwards: swapping the model, the tooling or the scope invalidates the previous evidence. And if your agents have no written rules yet, we start there: the 90-day programme comes before the test. Building the agent itself is not our business: we put you in touch with a builder partner, and we govern it with you.
Does this apply to my sector?
Our criterion isn't the sector, it's the situation: an organisation that already has an AI agent in pilot or production, touching money, sensitive data or consequential decisions, where somebody — risk, compliance, the board, a regulator, a professional order — has to answer for it. In practice that covers financial services and insurance, healthcare, professional services, the public sector and professional orders.
Where are you based, and do you work in French?
Aurelia Ops is a Canadian firm based in Montréal, Québec. We work in French and in English, on site or remotely, anywhere in Canada. Proof files, workshops and training are delivered in your organisation's language.
Deploy your AI agents — and stay defensible.
We'll pick an agent already in pilot or production with you, and show you what a proof file your auditor can re-examine looks like.
contact@aureliaops.comGovern. Protect. Prove.
See what a proof file contains
Piece by piece: what your auditor receives, what they can re-run, and what we do not promise.