Show how every conclusion was reached, long after it was made
Every change in Tovris goes into an append-only audit log, hash-chained per organization. Reports in English and French show the results, the evidence and the reviewer's decision, and anyone with audit access can check that the history has not been altered.
- Who uses it
- Auditor · Admin
- Instruments
- Every pack
- Starts when
- An auditor asks
- In the console
- Audit log · Reports
- Governance API routes permission-tested for every role
- 140
- Kinds of tampering the chain check catches: edit, removal, reordering
- 3
- Roles; auditors read everything and change nothing
- 5
From the build and the simulated Government of Canada test environment · synthetic data
Where the usual process breaks
When an auditor or a review body asks how a conclusion was reached, the answer is usually spread across email, shared drives and someone's memory.
- 01
Logs that administrators can edit are not evidence.
- 02
Reports are assembled by hand and drift from the system of record.
- 03
French versions are produced after the fact, if at all.
- 04
Auditors need to read everything and change nothing.
Four steps, each one a screen and an API route
Each step is part of the product, and each is written to the audit log as it happens.
- 01
Record everything
Every row change, sign-in, API key, publication, review, setting and export is written to the audit log. The database refuses edits and deletions.
- 02
Chain it
Each entry carries the hash of the one before it, per organization. Verification recomputes the chain and points to the first entry that does not match.
- 03
Trace it
From a requirement to its controls, the evidence, the finding, the run trace and the reviewer's decision: each link is stored, not reconstructed.
- 04
Report it
Generate a bilingual report for one system, a selection or the portfolio as PDF, JSON or CSV, and export the audit log with its filters.
audit trail
Action
any change
Audit entry
append-only
Hash chain
per organization
Verify
on demand
Report
EN · FR
What you can show
Audit questions get answered from the record itself.
An audit log with filters, entry detail and CSV export.
A chain check you can run at any time; restoring a backup checks every chain again.
Reports in both official languages that match the screen.
Break-glass access, when it is used, flagged in the log with its reason.
In the console
- Audit log: filters, chain check, export
- Reports from the dashboard and each system
- Settings: retention
Through the API
- GET /api/v1/audit/verify
- GET /api/v1/audit/export.csv
- GET /api/v1/reports/governance
Instruments in scope
Who does what
Auditor · Admin. Every action is checked against the person’s role on the server and written to the audit log.
The rest of the loop
Inventory
Know every AI system your department runs, in the register's own format
Start from the public Government of Canada AI Register, add the governance fields it lacks, and keep one record per system that owners maintain and auditors trust. Tovris imports the register, reports what is missing and exports it back in the published format.
Admin · Owner · GC AI Register · AIA
- Register entries imported, 0 failures
- 412
- Organizations in the published register
- 43
- Published fields, kept under their own names
- 24
Assessment
Assess each system against the DADM, with evidence a reviewer can check
Tovris works out which requirements of the Directive on Automated Decision-Making apply to a system, checks each one against the evidence you linked, and returns one of five results with a confidence score and citations. A person reviews every finding before it counts.
Assessor · Reviewer · DADM · AIA · PSD
- DADM 2025 requirements apply at level III
- 39 of 45
- Samples per requirement behind each confidence score
- 3
- Possible results, including “unable to determine”
- 5
Policy change
When a directive is amended, see every system it affects before you publish
Tovris compares the old and new editions requirement by requirement, shows which systems each change affects and why, and opens reassessment tasks for the systems already assessed. Only the changed requirements are assessed again.
Admin · Owner · DADM 2023 → 2025
- Requirements added by the June 2025 DADM amendments
- 11
- Requirements modified
- 34
- Requirements retired
- 6
Walk through this on synthetic data
We run this use case end to end on the simulated Government of Canada environment, in English or French, and answer questions as we go.
Live walkthrough · English or French · Synthetic data only