Write the evidence ledger before the prose
Research becomes fragile when discovery, interpretation and drafting happen in the same chat. Keep a separate ledger that records the claim, source passage, date, uncertainty and final sentence before the writing starts to flow.
We replace fictional evidence rows with a completed source comparison and show exactly why an overstated sentence must change.
Follow a real Canadian policy question from three primary documents to supported sentences and a dated update record.
Keep in mind: The ledger verifies limited claims about a consultation. It does not establish policy effectiveness or a final legal requirement.
In this article6 sections
Editorial note: The claim ledger is a research method, not proof that a draft is accurate. The writer remains responsible for opening the sources, resolving disagreements and removing claims the evidence cannot support.
Use a real question small enough to verify
Our question is: what can a Canadian reader accurately say about the federal AI transparency consultation on September 21, 2026? It is narrow enough to answer from primary documents and current enough to show why dates matter. The exercise compares a participation page, a discussion paper and the federal announcement.
These are real sources, not fictional evidence rows. The writing decisions below are our analysis of what each document supports. We do not claim to have measured whether the proposals prevent harm, obtained an unpublished government position or reviewed a final law. Those would require different evidence. An AI assistant can help organize the ledger, but it cannot close those gaps by writing a fluent transition.
Give each source one job
Use the participation page for the current process and deadline. Use the discussion paper for the questions being considered. Use the announcement for what the government said when launching the exercise. Their institutional relationship matters: three government pages about one consultation are not three independent confirmations of its effectiveness.
Record the title, URL, section and access date. Keep your own interpretation in a different field from an exact quotation. If you save a reference copy, respect the source’s reuse terms and your organization’s records rules. The aim is to make the later sentence recoverable, not to collect a large folder nobody will revisit.
The completed ledger
We checked the participation page and discussion paper for the claims below. A source can support a narrow statement while leaving a broader statement unproved. That is where the writing decision earns its place in the record.
Scroll the table sideways to see every column.
| Claim under consideration | Source and relevant part | Writing decision |
|---|---|---|
| The consultation runs July 23 to September 23, 2026 | ISED participation page: status and dates | Report the dates with an as-of date; recheck before submission. |
| The discussion includes notices, synthetic-content identification and agent records | ISED discussion paper: five transparency areas | Describe questions and proposals, not enacted duties. |
| These proposals have reduced fraud | No outcome evaluation in this source set | Do not report an achieved reduction. |
| Submissions are confidential by default | Participation page warns of possible public posting | Warn readers to review the submission instructions and omit private information. |
Turn an overstatement into a supported sentence
Draft to reject: “Canada now requires every AI service to label its content and publish agent logs.” The source pack establishes a consultation, not that universal present-tense duty. Adding a link to the discussion paper would not repair the claim.
A supported replacement is: “Canada is consulting on transparency measures that include identifying synthetic content and recording AI-agent activity.” If the sentence discusses participation, add the checked deadline and direct readers to the official page. Keep the policy question and the practical instruction separate so each can be updated without silently changing the other.
Ask an assistant to identify which ledger row supports each factual sentence. Treat that mapping as a draft too: open the source and check the passage. An invented row identifier is no more reliable than an invented URL.
What to do when the pages disagree
This source comparison did not establish a conflict over the dates. For a future update, suppose a participation page changes its deadline while an older announcement keeps the original one. Record both versions and investigate which page governs current submissions. Do not rewrite the announcement’s history or ask a model to vote between the dates.
If the controlling source remains unclear, narrow the claim and contact the source through its official route. A useful ledger can contain “not resolved.” The unresolved field protects the draft from turning a research problem into false certainty.
Canada’s AI transparency consultation guideRead the policy context behind the three-source example.
Build the next update from the claims that can expire
Mark the deadline, consultation status and submission instructions for another check. The five discussion areas may remain historically accurate after participation closes, while “you can submit now” becomes wrong. That distinction is why a page-wide fresh date is not enough to establish that each claim was reviewed.
Keep the prior sentence and the reason for changing it. If the earlier article was wrong, use a correction appropriate to the significance of the error. If events simply moved on, describe the new stage. The result is a research workflow with an inspectable history, rather than a new polished draft detached from its evidence.
Continue with the original sources
These claim-relevant primary and first-party references support the reporting above. Open them for technical detail, current requirements and subsequent updates.
- canada.caCanada's AI transparency consultation ↗The official July 23 announcement, including the consultation dates and the five subjects on which Canada requested feedback.
- ised-isde.canada.caISED discussion paper: Enhancing trust in AI through increased transparency ↗The government discussion paper that frames the transparency questions; it is consultation material, not a final rule.
- ised-isde.canada.caISED: Have your say on advancing AI transparency in Canada ↗The official participation page for the consultation scheduled from July 23 to September 23, 2026.
Finished reading? Save that here without waiting for a timer.
Rewritten throughout on September 21, 2026, with a complete worked method, explicit evidence limits and checked primary sources.
See something we should fix or clarify? Read the corrections policy or tell the newsroom. Material changes are noted here.
