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.
- Who uses it
- Admin · Owner
- Instruments
- DADM 2023 → 2025
- Starts when
- An admin drafts a new policy version
- In the console
- Policies · Tasks
- Requirements added by the June 2025 DADM amendments
- 11
- Requirements modified
- 34
- Requirements retired
- 6
From the build and the simulated Government of Canada test environment · synthetic data
Where the usual process breaks
The directive was amended in June 2025. Finding out what changed meant comparing two long pages side by side, then guessing which systems were affected.
- 01
Clauses were renumbered between editions, so comparing section numbers misleads.
- 02
Some changes are only a French rewording; others change what a system must do.
- 03
Owners hear about amendments late, if at all.
- 04
Earlier conclusions stay on file as if the old rules still applied.
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
Draft the new version
An admin creates the new version from the official text. Every quote is extracted from the stored source and checked word for word, and a person verifies the encoding.
- 02
Compare editions
Tovris matches requirements by stable keys, not clause numbers, and classes each change as added, modified (substantive, translation or editorial) or retired.
- 03
See the impact
Before anything is published, the impact analysis lists the affected systems with reasons, the findings that are now stale and the evidence linked to them.
- 04
Publish and reassess
An admin publishes. Systems assessed before get a reassessment task, and starting it reassesses only the changed requirements.
policy change
New version
verified quotes
Diff
by requirement key
Impact
systems · findings
Publish
admin approval
Tasks
changed only
What you can show
Amendments stop being a research project. The change record says what changed; the task list says who has to act.
A change record per version: added, modified and retired requirements, with old and new text.
Translation-only changes listed, but not sent back for reassessment.
An impact report per system, with the reason it is affected, on screen and as CSV.
Reassessment tasks for owners, with notices in both languages.
In the console
- Policies: versions, verification and publishing
- Change record and impact report
- Tasks
Through the API
- GET /api/v1/versions/{id}/diff/{other}
- POST /api/v1/versions/{id}/publish
- GET /api/v1/policy-changes/{id}
Instruments in scope
Who does what
Admin · Owner. 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
Risk monitoring
Catch drift and unfair outcomes between assessments
Tovris watches data quality, input drift and output measures for each system. When a measure crosses its line, the result is filed as evidence, findings are raised on the linked requirements, a reassessment task opens, and your ticketing system hears about it.
Owner · Assessor · DADM 6.3
- Default drift alert line (Population Stability Index)
- 0.2
- Injected breaches caught in testing, no false alarms
- 2 of 2
- Ticket priorities on the signed webhook
- P1–P4
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