<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[The Old Guardian’s Substack]]></title><description><![CDATA[Truth over narrative, every time. No parties, no tribes, no agenda.]]></description><link>https://www.theoldguardian.ca</link><image><url>https://substackcdn.com/image/fetch/$s_!ChDO!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba010f10-0b41-4234-90ec-1c87c7233e20_1280x1280.png</url><title>The Old Guardian’s Substack</title><link>https://www.theoldguardian.ca</link></image><generator>Substack</generator><lastBuildDate>Thu, 15 Oct 2026 22:23:23 GMT</lastBuildDate><atom:link href="https://www.theoldguardian.ca/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[The Old Guardian]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[theoldguardian@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[theoldguardian@substack.com]]></itunes:email><itunes:name><![CDATA[Christopher Allen]]></itunes:name></itunes:owner><itunes:author><![CDATA[Christopher Allen]]></itunes:author><googleplay:owner><![CDATA[theoldguardian@substack.com]]></googleplay:owner><googleplay:email><![CDATA[theoldguardian@substack.com]]></googleplay:email><googleplay:author><![CDATA[Christopher Allen]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Covid - THE MAZE]]></title><description><![CDATA[Canada told vaccine-injured Canadians it would be there for them. Then it hired an accounting firm to make sure it didn&#8217;t have to be.]]></description><link>https://www.theoldguardian.ca/p/the-maze</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/the-maze</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Tue, 13 Oct 2026 09:45:50 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/aac08e14-f584-4f79-bca4-70c4f5594e18_1672x940.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>THE OLD GUARDIAN</p><p>theoldguardian.ca  |  Independent Investigative Journalism</p><p>By Chris Allen  |  The Old Guardian  |  September 2026</p><p>Michael Oesch used to walk across countries.</p><p>Not metaphorically. Literally. Thousands of kilometres on foot, across Canada, the kind of thing most people put on a bucket list and never do. He did it. He was that kind of man.</p><p>In October 2022, he took his fourth COVID dose. Thirty-six hours later he was walking with his granddaughter when his leg stopped working. Just stopped. He couldn&#8217;t lift it. The MRI showed a lesion near the top of his spinal cord. He lost the ability to walk. He now lives in long-term care.</p><p>He applied to Canada&#8217;s Vaccine Injury Support Program. They said no.</p><p>No explanation that distinguished his case from the ones they did approve. Just no.</p><p>Cameron Hitchcock was 29 when his kidneys started failing after his second Pfizer dose. Nephrotic syndrome. Five months in hospital. Kidney failure. Dialysis six days a week now, still waiting for a transplant. He arranged his treatment schedule around a trip to Ottawa to testify publicly, because in five years no formal Canadian institution had made space to hear him. His VISP claim was approved. He is one of 252.</p><p>Same program. Same government promise. One man recognized, still on dialysis. One man denied, no longer able to walk.</p><p>To understand how that happened, you have to go back to before the program existed. To a contract clause. And a promise that was never quite what it sounded like.</p><p>What the Promise Actually Was</p><p>December 2020. Justin Trudeau announced the Vaccine Injury Support Program alongside the beginning of the rollout. What he said was this:</p><p>&#8216;By getting vaccinated, we protect one another and our way of life. The chances of this are extremely rare -- less than one in a million -- and we have a duty to help if this occurs.&#8217;</p><p>It sounded like a commitment born of decency. A government saying: we&#8217;re asking this of you, and if it goes wrong, we&#8217;ll be there.</p><p>It was also, buried in the fine print of a pharmaceutical contract nobody was talking about publicly, a legal obligation.</p><p>Pfizer&#8217;s advance purchase agreements -- the ones signed with governments around the world in 2020 and 2021 -- contained standard indemnification language. Governments were required to shield Pfizer from lawsuits arising from their vaccines. And as a condition of that indemnification, they were required to create and maintain what the South African version of the contract called &#8216;a no-fault compensation fund sufficient to undertake and completely fulfil the indemnification obligations.&#8217;</p><p>VISP wasn&#8217;t created because it was the right thing to do. It was created because it was in the contract.</p><p>Procurement Minister Anita Anand confirmed the indemnification publicly at the time: &#8216;All countries, generally speaking, are faced with the issue of indemnification of companies, especially in cases of novel technologies like this. Yes we are, and we are definitely not different than any other country in this world.&#8217;</p><p>She was right about that. What she didn&#8217;t mention was that a 2017 Public Health Agency of Canada document, updated in 2019, had already established that during a pandemic, indemnity clauses should be standard practice to protect supply. This was planned before COVID existed. The promise Trudeau made in December 2020 had a contractual architecture behind it that had been built two years earlier.</p><p>Daniel Freiheit is a Toronto lawyer, LSO certified in corporate and commercial law, who has represented multiple VISP claimants and testified about the program at the Allison Inquiry in September 2026. He confirmed that Canada&#8217;s advance purchase agreement with Pfizer follows the same indemnification structure as the contracts exposed in other countries. The jurisdiction clause in Canada&#8217;s version was redacted.</p><p>The program the government announced as a humanitarian commitment was, in contractual terms, a liability management mechanism for a pharmaceutical company.</p><p>Sources: Trudeau announcement, December 2020. Anita Anand public statement, December 2020. PHAC 2017/2019 pandemic indemnity policy. South African Pfizer contract, Pretoria High Court 2023, Bureau of Investigative Journalism. Daniel Freiheit, Allison Inquiry September 9, 2026 and interview September 24, 2026.</p><p>The Accounting Firm</p><p>Here is something the government noticed early on: it had a conflict of interest.</p><p>It had approved the vaccines. It had signed the indemnification clause. It had promised to compensate people harmed by those same vaccines. A draft 2023 government report put it plainly -- administering the compensation program itself would create &#8216;a conflict of interest that would arise from serving as both the approver of the vaccines and the one that compensated people for the harms vaccines caused.&#8217;</p><p>The solution was not to resolve the conflict. It was to hire someone else.</p><p>In February 2021, PHAC put out a call for proposals. Companies had roughly three weeks to apply. Four did. The winner was Raymond Chabot Grant Thornton Consulting Inc., since rebranded as Oxaro.</p><p>Four Conservative MPs who later investigated the contract wrote: &#8216;There was no clear indication that Oxaro had credible experience in healthcare or in the administration of health-related claims.&#8217;</p><p>That&#8217;s understating it. Oxaro&#8217;s cited relevant experience was administering a memorial grant program for first responders and liquidating an insolvent life insurance company. They had never run a health claim adjudication program of any kind. The Health Minister pushed them to launch three months ahead of schedule anyway.</p><p>The budget was $65.2 million over five years covering operations, administration, and actual claim payments combined. What happened was that Oxaro received $80.8 million total and directed $36.3 million of that -- 67 percent -- to administration. As one former worker told Global News: &#8216;It&#8217;s frustrating. I can&#8217;t help these individuals out.&#8217;</p><p>Freiheit called VISP the only secret tribunal he knows of in Canadian law. The names of the medical professionals reviewing applications were never made public. The appeals process was not explained to claimants -- it had to be obtained through Freedom of Information requests.</p><p>Oxaro got paid on time. Every time. While claimants waited 18 months or more for a case manager to be assigned.</p><p>Sources: Global News investigation, July 2025. Draft 2023 PHAC/Health Canada VISP review report. Conservative MP letter to Health Minister, July 2025. Daniel Freiheit, interview September 24, 2026.</p><p>The Numbers</p><p>Trudeau said the chances of serious injury were less than one in a million.</p><p>By December 2025, 3,557 Canadians had applied to VISP.</p><p>252 were approved.</p><p>7.1 percent.</p><p>A peer-reviewed comparative analysis of 14 COVID vaccine injury compensation jurisdictions, published in the journal Vaccine in March 2025, found Canada&#8217;s review approval rate at 19.92% as of November 2024 -- an improvement, but still well below most comparable countries. Japan, Taiwan, and South Korea all operate above 50%. Germany and France higher still.</p><p>Thailand&#8217;s system runs differently. The National Health Security Office provides mandatory preliminary compensation within 30 days of a claim. Subcommittees must complete their review within 30 days and announce results within five. The amounts per claim are smaller than Canada&#8217;s maximum payouts. But by early 2022 -- before Canada had approved barely a handful of claims -- Thailand had already compensated 12,714 people to the tune of roughly $45 million USD.</p><p>Cameron Hitchcock is still on dialysis six days a week. Michael Oesch still lives in long-term care. Both went to Ottawa in September 2026 to tell their stories to the Allison Inquiry, a forum built by volunteers, because in five years no government body had created a formal space to hear them.</p><p>3,557 Canadians applied. 252 were compensated. The rest were told, in one form or another, to keep waiting.</p><p>Among those who did not receive compensation: 225 claimants whose applications were denied not on medical grounds, but because they missed a procedural three-year deadline. Their injuries were never assessed. Under VIAP, those 225 have been reinstated. Whether their claims will now be evaluated on merit -- rather than process -- remains to be seen.</p><p>Sources: PHAC VISP program statistics, December 2025. Comparative COVID-19 vaccine injury compensation systems, Vaccine journal, March 2025. Cameron Hitchcock and Michael Oesch, Allison Inquiry public testimony, September 2026.</p><p>The Conflict That Came Back</p><p>In April 2026, PHAC took over direct administration of the program, now renamed the Vaccine Impact Assistance Program. The conflict of interest that was serious enough to require outsourcing in 2021 was apparently no longer serious enough in 2026. No public explanation was offered for the change.</p><p>The person now running VIAP is Nancy Hamzawi, President of PHAC since June 2025. She is not a medical professional. Her background is chemical engineering and public administration. Before becoming PHAC President, she served as Assistant Deputy Minister of Health Canada&#8217;s Health Products and Food Branch -- the branch that authorized COVID-19 vaccines for use in Canada. She moved to PHAC as Executive Vice-President in February 2023, in the middle of the program&#8217;s worst period of non-approvals and administrative chaos.</p><p>The woman now overseeing compensation for people harmed by vaccines previously helped oversee the authorization of those vaccines. The conflict the government once said it needed to outsource to avoid is now sitting in the office of the person running the program directly.</p><p>Nobody has been asked to account for that publicly.</p><p>The transition also came with a hard deadline. October 1, 2026, was the cutoff for incomplete VISP applications. Claimants who had started applications but not yet submitted were required to do so by 11:59 p.m. that night -- or they would need to begin again under the new VIAP structure and forms. For people dealing with serious, ongoing health consequences, the administrative pressure of a hard restart cutoff is not a minor inconvenience. It is another barrier dressed in paperwork.</p><p>Sources: PHAC organizational structure, canada.ca, April 2026. Nancy Hamzawi biography, phac.gc.ca. CBC News, PHAC takeover announcement, April 2026.</p><p>The Legal Maze</p><p>When injured Canadians try to go around VISP -- when they try to find some other path to accountability -- they run into what Freiheit calls a maze.</p><p>Want to sue Pfizer? You get redirected to VISP. You can technically name Pfizer as a defendant, but Pfizer then brings in Health Canada through a third-party claim. The case bounces. The years pass. The legal costs grow. The injured person waits.</p><p>Courts in Canada remain deeply deferential to Health Canada&#8217;s regulatory judgment. As Freiheit put it plainly: &#8216;Courts trust the system, because Health Canada said so.&#8217; The internal ATI documents that show what Health Canada was actually concluding privately -- the possible myocarditis link nineteen days before the public was told no association existed, the CAEFISS data unavailable in real time, the surveillance progressively wound down -- have not yet been tested in a Canadian courtroom. Nobody knows yet what they mean legally.</p><p>A class action is working its way through the Alberta courts, naming both the Government of Canada and the Province of Alberta. It alleges negligence, misfeasance in public office, and conduct that amounts to assault and battery on the public. It is in early stages. These things take years.</p><p>In the meantime, the maze holds.</p><p>Sources: Daniel Freiheit, interview September 24, 2026. CanLII case summaries, vaccine injury litigation. ATI Release A-2025-001410, Health Canada, July 2026.</p><p>What the Documents Show</p><p>This piece connects to a larger body of work.</p><p>The Old Guardian&#8217;s What They Knew series, published in September 2026, examined 2,460 pages of Health Canada&#8217;s internal pharmacovigilance records obtained through ATI Release A-2025-001410. Those documents showed that Health Canada&#8217;s own reviewers concluded a possible link between the vaccine&#8217;s second dose and myocarditis in young males in May 2021 -- nineteen days before the public was told no clear association existed. They showed that fatal report monitoring for the bivalent vaccine was removed from monthly tracking at Pfizer&#8217;s request. They showed that adverse event data from CAEFISS was not available to Health Canada in real time as of June 2022, when 58 million doses had already been administered.</p><p>The surveillance system that was supposed to catch rare injuries had documented gaps. The compensation system that was supposed to acknowledge them couldn&#8217;t get out of its own administrative structure. The legal system redirects anyone who tries to hold someone accountable back into the same failing program.</p><p>None of this required malice. That&#8217;s the part worth sitting with. The indemnification clause was standard policy written years earlier. The outsourcing decision made a kind of bureaucratic sense. The conflict of interest was real and the government acknowledged it. The surveillance reductions were documented negotiations. Each piece had a reason. Together they built something that left Michael Oesch in long-term care and Cameron Hitchcock on dialysis without adequate explanation, redress, or accountability.</p><p>That&#8217;s not incompetence. That&#8217;s architecture.</p><p>The Promise, Five Years Later</p><p>Trudeau said the chances were less than one in a million.</p><p>3,557 Canadians disagreed -- with their bodies, with their claims, with their presence in an Ottawa committee room in September 2026.</p><p>The program that was supposed to be there for them consumed more than half its budget before most of them were heard. It was administered by a firm that had never run a health claim program. Its medical reviewers were kept anonymous. Its appeals process required a Freedom of Information request to find. It paid its administrator on time and in full while claimants waited a year and a half for a case manager.</p><p>And when the administrator&#8217;s contract ran out, the government quietly brought the whole thing back in-house -- into the same agency that approved the vaccines in the first place.</p><p>Michael Oesch walked across Canada. He cannot walk now. The program said no.</p><p>Cameron Hitchcock will be on dialysis again tomorrow. The program said yes. He still had to go to Ottawa on his own to be heard.</p><p>The promise was less than one in a million.</p><p>There were 3,557 of them.</p><p>Sources and Notes</p><p>Global News, July 2025</p><p>Primary mainstream investigation into VISP: Oxaro contract, administrative cost breakdown, worker testimony. globalnews.ca/news/11258737</p><p>Vaccine journal, March 2025 (ScienceDirect)</p><p>Peer-reviewed comparative analysis of 14 COVID-19 vaccine injury compensation programs. Canada, Japan, Taiwan, South Korea, Thailand, Germany, France. Approval rate data.</p><p>South African Pfizer contract, Pretoria High Court 2023</p><p>Standard indemnification language: governments required to indemnify Pfizer and maintain a no-fault compensation fund. Bureau of Investigative Journalism primary reporting.</p><p>Procurement Minister Anita Anand, December 2020</p><p>Public confirmation of indemnification clauses as standard in all Canadian COVID vaccine contracts.</p><p>PHAC 2017/2019 pandemic indemnity policy document</p><p>Pre-pandemic policy establishing indemnity clauses as standard practice during pandemics. Predates COVID by two years.</p><p>Daniel Freiheit, Lion Law, Toronto</p><p>LSO Certified Specialist, Corporate and Commercial Law. Allison Inquiry testimony September 9, 2026. Interview with The Old Guardian September 24, 2026. Confirmed Canadian contract structure, characterized legal landscape as a maze, identified VISP as only secret tribunal in Canadian law he is aware of.</p><p>ATI Release A-2025-001410, Health Canada, July 15, 2026</p><p>2,460 pages of internal pharmacovigilance records. Myocarditis internal timeline (p.62). CAEFISS real-time data gap (p.198). Surveillance wind-down documentation (BBRS Signal Tracking, May 29, 2023).</p><p>PHAC organizational structure, canada.ca, April 2026</p><p>Nancy Hamzawi confirmed as PHAC President since June 2025. Previous role: ADM Health Canada Health Products and Food Branch. No medical training.</p><p>Cameron Hitchcock and Michael Oesch</p><p>Public testimony, Allison Inquiry, September 2026. Both named voluntarily and publicly. Cameron Hitchcock: VISP approved. Michael Oesch: VISP denied.</p><p>Conservative MPs letter, July 2025</p><p>Four Conservative MPs to Health Minister demanding probe into Oxaro contract and VISP mismanagement following Global News investigation.</p><p>The Old Guardian is an independent investigative outlet based in Toronto. The full What They Knew series and ATI Release A-2025-001410 are available on request. Contact: tips@theoldguardian.ca</p><p>The Old Guardian  |  theoldguardian.ca  |  tips@theoldguardian.ca</p>]]></content:encoded></item><item><title><![CDATA[MAiD - Given Every Opportunity to Answer, No One Did]]></title><description><![CDATA[THE OLD GUARDIAN INVESTIGATES]]></description><link>https://www.theoldguardian.ca/p/maid-given-every-opportunity-to-answer</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/maid-given-every-opportunity-to-answer</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Sun, 20 Sep 2026 18:30:56 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/9265c3fa-6751-48d9-890c-964a91798189_1672x941.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>THE OLD GUARDIAN INVESTIGATES</p><p>The death of Brigitte Stegemann at a Belleville-area long-term care home raises two unresolved legal questions. The people positioned to answer them have not.</p><p>By Chris Allen   |   The Old Guardian   |   September 17, 2026</p><p>THREE OPPORTUNITIES, THREE SILENCES</p><p>Brigitte Stegemann, known to her family as GG, died on July 10, 2026, at The Pearl, a 41-bed long-term care home in Cannifton, Ontario, formerly operated as E.J. McQuigge Lodge. She was 83 years old and had been diagnosed five months earlier with stage IV stomach cancer. Her death was provided under Canada&#8217;s medical assistance in dying program.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>On August 17, 2026, her granddaughter and Power of Attorney for personal care, Brigitte Kranendonk, filed a formal complaint with Ontario&#8217;s Chief Coroner, requesting review by the province&#8217;s MAiD Death Review Team. The complaint asks the Coroner to examine whether the process that led to GG&#8217;s death complied with the Coroners Act and the Criminal Code.</p><p>In the month since, The Old Guardian has given three parties direct, repeated, and specific opportunity to respond to the questions this complaint raises. Pearl Care Homes Inc., which operates the facility, was contacted on August 14 and again on August 24, with a total of six specific questions about the events leading to GG&#8217;s death. Neither message received a reply. Dr. Catherine Koester, the physician who provided the procedure, was contacted on August 24 with five specific questions and given until September 5 to respond. That deadline passed without a reply.</p><p>On September 9, both parties were sent a final, explicit right-of-reply notice, listing the specific claims that would appear in this report and setting a final deadline of September 16. Pearl Care Homes&#8217; first point of contact returned a delivery failure; the notice was redirected the same day to the facility&#8217;s administrator and two other staff members. As of publication, no response has been received from Pearl Care Homes Inc., from Dr. Koester, or from anyone acting on their behalf, at any address, at any point in this five-week window.</p><p>That silence does not, on its own, prove anything happened the way GG&#8217;s family says it did. It does mean this report proceeds without the benefit of an account from either party positioned to explain what the documented record does not.</p><p>WHAT THE RECORD SHOWS</p><p>Some of this is not in dispute.</p><p>Pearl Care Homes Inc., Ontario Corporation Number 1634259, was formed by amalgamation on January 1, 2005, from Keay Nursing Homes Inc. and 854822 Ontario Inc. It is licensed by the Ontario Ministry of Long-Term Care and managed by UniversalCare Canada Inc. The facility&#8217;s Ministry inspection record over the relevant period shows no findings specific to consent. A Critical Incident inspection on January 8, 2026, addressed a complaint about POA communication, logged as intake #00163634, but the complaint was not substantiated at the level of a written notification; that inspection window overlaps with the period the family says MAiD discussions with GG were privately restarted. Ministry inspections of long-term care homes assess compliance with care standards; they are not designed to evaluate the specific process by which MAiD consent is obtained, which is a separate legal and medical framework. The absence of an inspection finding here answers a narrower question than it might appear to.</p><p>Dr. Koester has practiced independently in family medicine since June 2008, through her professional corporation, Kate Koester Medicine Professional Corporation, based out of a clinic in Newburgh, Ontario, serving Lennox and Addington County, which includes Cannifton. She holds no hospital privileges and has no prior record of discipline with the College of Physicians and Surgeons of Ontario. The coroner&#8217;s complaint against her, filed August 17, is the first documented regulatory action of any kind involving her practice.</p><p>Her name has appeared inconsistently across public accounts of this case, including in the family&#8217;s own written complaint. To be precise: the physician identified here is Catherine Louise Koester, CPSO registration number 84550, confirmed directly against the College&#8217;s public register. A separate, unrelated physician registered under the surname Kester, CPSO registration number 72393, practices at Sunnybrook Health Sciences Centre in Toronto and has no connection whatsoever to this case.</p><p>WHAT THE FAMILY SAYS HAPPENED</p><p>Everything beyond the documented record above originates with reporting by Kelsi Sheren, a Canadian veteran, author, and MAiD-focused commentator who has published two detailed accounts of this case on her Substack since late July. Her reporting is based on an eighty-minute interview she conducted with Brigitte Kranendonk on July 22, a written statement the family posted publicly to Facebook, and the family&#8217;s written complaint to the coroner, which Kranendonk provided to her directly. The Old Guardian&#8217;s own contact with Kranendonk began in July and stalled in August after an initial exchange; this report does not have an independent account from her. What follows should be read as exactly that: one family&#8217;s account, filtered through one other outlet&#8217;s reporting, of events they were not present for in full, made public while a coroner&#8217;s investigation remains open.</p><p>According to that reporting, staff at The Pearl privately restarted conversations with GG about medical assistance in dying during a roughly ten-day period when Kranendonk was away, and these conversations were not disclosed to her at the time. GG is described in this reporting as profoundly hearing-impaired, completely deaf in one ear with limited hearing in the other, and as experiencing frequent periods of lethargy and unresponsiveness in her final months, a detail relevant to any account of what she could hear or process during this period. Formal eligibility assessments took place on July 6 and 7, attended by GG&#8217;s daughter, son-in-law, and Kranendonk herself, and the reporting describes GG as unable to recall basic facts about her own family during at least one of these sessions. On the morning of July 10, Kranendonk reportedly told her grandmother directly that she still had the right to refuse. GG is described as having remained silent through the procedure that followed, giving no verbal confirmation of consent. Separately, the reporting states that paperwork related to the MAiD application was completed by a member of facility management after a provision date had already been scheduled, that the date was then moved forward by one day to accommodate the physician&#8217;s schedule without consulting the family, and that GG had, months earlier, explicitly declined MAiD on the basis of her Christian faith.</p><p>Each of these claims was put directly to Pearl Care Homes and, where relevant, to Dr. Koester, in the right-of-reply notices sent September 9. Neither responded to any of them. Sheren&#8217;s own reporting notes a parallel outcome: she states that she independently requested the death certificate, both required eligibility assessments, the signed MAiD request and its witness, and any waiver of final consent, and that none had been produced as of her July 27 report.</p><p>THE TWO QUESTIONS NOBODY WILL ANSWER</p><p>Two specific, resolvable facts sit underneath everything else in this case, and both remain unknown because the only two people positioned to answer them have not.</p><p>The first is whether a written Waiver of Final Consent existed for GG, under section 241.2(3.2) of the Criminal Code. This matters because the law does not, in every case, require a verbal confirmation of consent immediately before a MAiD provision. A person assessed as eligible under Track 1 can sign a written arrangement in advance, waiving that final verbal step, specifically to cover situations where they may lose the capacity to confirm it later. If such a waiver existed for GG, and was properly obtained, her silence on July 10 would not, on its own, indicate anything went wrong. If no such waiver existed, the law required her active consent that day, and her family&#8217;s account describes a procedure that proceeded without it. This is not a peripheral detail. It is close to the entire legal question the case turns on, and it was asked of Dr. Koester directly, in writing, twice. She has not answered.</p><p>The second is the identity of the second independent assessor. Canadian law requires two separate, independent clinicians to confirm a patient&#8217;s eligibility for MAiD. Nowhere in the record, the family&#8217;s account, the coroner&#8217;s complaint, or anything provided by Pearl Care Homes or Dr. Koester, is that second assessor named. This is not a hypothetical concern. A January 2021 Ministry of Health Decision Briefing Note, obtained separately through a British Columbia freedom of information request, describes an unnamed B.C. physician whose MAiD report lacked a required second assessment confirming eligibility. The Ministry&#8217;s own briefing note recommended referring that case to both the police and the physician&#8217;s regulatory college. It is not known whether that recommendation was acted on. What it establishes is that a missing second assessment is not a paperwork technicality in the eyes of the system meant to catch it. It is something a Ministry of Health, in at least one other documented instance, has treated as serious enough to warrant a criminal referral.</p><p>A PATTERN, NOT AN ISOLATED CASE</p><p>GG&#8217;s case does not exist in isolation, and the questions it raises are not unique to one facility or one physician.</p><p>Ontario&#8217;s own MAiD Death Review Committee published a report in 2024 examining waivers of final consent specifically, drawing on a sixteen-member panel of physicians, ethicists, lawyers, and disability advocates whose job is to review these cases after the fact. That committee could not agree on a consistent standard for how capacity should be evaluated before a waiver is signed. In one case it reviewed, a man with dementia gave no verbal response at all during his provision, and the committee found that silence alone, absent any sign of refusal, was sufficient under the law. In another, a financial beneficiary had signed a waiver on the patient&#8217;s behalf, which the committee flagged specifically because the signer had a stake in the outcome, and it recommended using independent third parties for exactly that reason. The same report notes that a family&#8217;s involvement in a waiver can lapse entirely over time, and that family members may remain unaware such an arrangement exists at all, because a capable adult&#8217;s decision to enter into one is legally their own, and provincial privacy law can prevent a facility from disclosing it without that person&#8217;s consent. Every element of GG&#8217;s case sits inside the exact set of gaps this report already identified, in the province where she died, before she died.</p><p>A separate and unrelated set of documents, obtained through freedom of information requests in British Columbia, shows the same underlying incentive at work in a different oversight structure entirely. An internal memo to that province&#8217;s Deputy Minister of Health in November 2023, which he approved, recommended building a system to weigh MAiD-related referrals specifically because, in the memo&#8217;s own words, referring cases too readily &#8220;may discourage physicians or nurse practitioners from providing MAiD despite high demand.&#8221; Since 2018, that province has referred only 22 cases to regulatory colleges and two to law enforcement, out of thousands reviewed, a rate under 0.2 percent. In several of those rare referrals, the assessor had declared the patient eligible even though their own written assessment did not find all eligibility criteria were met. British Columbia&#8217;s MAiD program and Ontario&#8217;s are governed separately, by different oversight bodies, but the documents from both provinces describe a system built primarily to expand access, with review mechanisms that consistently treat caution as a cost to be weighed against volume, not a floor to be enforced regardless of it.</p><p>That is the system GG&#8217;s case moved through. Whether it worked as intended, or failed her specifically, is a question with a real answer. Three parties who could supply it have been asked directly, repeatedly, and in writing. None of them have.</p><p>EDITOR&#8217;S NOTE</p><p>This report relies on the formal coroner&#8217;s complaint filed by Brigitte Kranendonk on August 17, 2026; Ontario Ministry of Long-Term Care inspection records for The Pearl; corporate registry records for Pearl Care Homes Inc.; the College of Physicians and Surgeons of Ontario&#8217;s public register; Ontario&#8217;s 2024 MAiD Death Review Committee report on Waivers of Final Consent; and freedom of information documents obtained by The B.C. Catholic (July 2025) and Canadian Catholic News (July 2026) regarding oversight of British Columbia&#8217;s MAiD program. The account of events attributed to the Stegemann family in this report is drawn from reporting published by Kelsi Sheren, based on her own interview with Brigitte Kranendonk and documents the family provided to her directly; it is not independent reporting by this outlet, has not been independently verified beyond what is stated here, and the coroner&#8217;s investigation into this matter remains open. Pearl Care Homes Inc. and Dr. Catherine Koester were each given multiple, specific opportunities to respond between August 14 and September 16, 2026, and did not.</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;0ded0be8-301b-459f-bf28-15d397bd650e&quot;,&quot;caption&quot;:&quot;THE OLD GUARDIAN&quot;,&quot;cta&quot;:null,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;lg&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;THE MAZE&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:315040924,&quot;name&quot;:&quot;Christopher Allen&quot;,&quot;bio&quot;:&quot;Welcome, Guardians. Success isn&#8217;t just money, it&#8217;s truth, community, and the journey. This space is for real talk, sharp thinking, and pushing back on the noise. I want your feedback. Speak up. Let&#8217;s build something that lasts.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/3461b478-c850-4d26-bc9c-672624b0cb55_1024x1024.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2026-10-13T09:45:50.886Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/aac08e14-f584-4f79-bca4-70c4f5594e18_1672x940.png&quot;,&quot;cover_image_alt&quot;:null,&quot;canonical_url&quot;:&quot;https://www.theoldguardian.ca/p/the-maze&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:220111853,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:3999531,&quot;publication_name&quot;:&quot;The Old Guardian&#8217;s Substack&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!ChDO!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba010f10-0b41-4234-90ec-1c87c7233e20_1280x1280.png&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/maid-given-every-opportunity-to-answer?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/maid-given-every-opportunity-to-answer?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/maid-given-every-opportunity-to-answer?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/maid-given-every-opportunity-to-answer/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/maid-given-every-opportunity-to-answer/comments"><span>Leave a comment</span></a></p><p></p>]]></content:encoded></item><item><title><![CDATA[Pharmacovigilance - WHAT THEY KNEW | PART 6 OF 6]]></title><description><![CDATA[The Accounting]]></description><link>https://www.theoldguardian.ca/p/what-they-knew-part-6-of-6-the-final</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/what-they-knew-part-6-of-6-the-final</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Fri, 18 Sep 2026 09:45:37 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/80e270fc-f891-42f8-876a-8508050f6704_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>THE OLD GUARDIAN</p><p>theoldguardian.ca  |  Independent Investigative Journalism</p><p>Five parts of primary source documentation. Six comparison entries. What Health Canada&#8217;s internal records show regulators knew, and what Canadians were told instead. The gap is documented. The documents are public. What happens next is a choice.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/subscribe?"><span>Subscribe now</span></a></p><p>By Chris Allen  |  The Old Guardian  |  September 2026</p><p>Primary source: ATI Release A-2025-001410, Health Canada, July 15, 2026</p><p>On November 22, 2022, Anthony Fauci stood at the White House podium for the final time before his planned retirement. A reporter asked about the congressional oversight hearings expected from the incoming Republican majority. Fauci&#8217;s response was unambiguous.</p><p>&#8216;We can defend and explain and stand by everything that we&#8217;ve said. So I have nothing to hide.&#8217;</p><p>On July 29, 2026, Fauci appeared before the Senate Homeland Security and Governmental Affairs Committee under subpoena. He invoked the Fifth Amendment more than one hundred times. He declined to answer what day it was. He declined to answer what colour tie he was wearing. He declined to state what colour the carpet in the committee room was. The Homeland Security Committee voted to hold him in contempt of Congress. He subsequently declined a voluntary appearance before a second Senate panel.</p><p>On August 18, 2026, Dr. David Morens, Fauci&#8217;s senior adviser at NIAID, pleaded guilty in federal court to plotting to conceal COVID-19 research records during the pandemic. The Department of Justice alleged he had used his personal email account to intentionally circumvent public records laws and concealed or destroyed records related to COVID-19 research grants.</p><p>Fauci was not charged in the Morens case. The guilty plea is Morens&#8217;. The contempt proceeding and the text message accountability questions are separate Fauci threads.</p><p>Together they form an institutional portrait that does not require editorial comment. A man who said he had nothing to hide. Surrounded, by 2026, by a contempt finding, a guilty plea from his senior adviser, and 34,000 text messages still being reviewed by Senate investigators -- including a January 25, 2021 message in which he privately told the CDC Director that the vaccine &#8216;theoretically could be associated with miscarriage in the 1st trimester&#8217; while publicly saying there were no red flags.</p><p>This is the opening of Part 6 not because this series is about Anthony Fauci. It is not. It is about what happened in Canada.</p><p>It opens here because Canadian public health policy was downstream of American decisions during the COVID-19 pandemic. When Fauci said masks were unnecessary in February 2020, Canadian public health messaging reflected that. When the six-foot rule became American policy, it became Canadian policy within days. NACI guidance tracked CDC guidance closely. The policy transmission belt between Washington and Ottawa operated in real time.</p><p>The architect of the American policy framework that Canadian guidance was downstream of is now the subject of contempt proceedings, while his senior adviser has pleaded guilty to records destruction. Canadian parliamentarians have never been asked to account for what Canadian guidance adopted from that institutional environment.</p><p>That question belongs in this piece. So do the documents.</p><p>The Comparison: Six Entries</p><p>What follows is a direct comparison of specific public statements against specific internal findings from ATI Release A-2025-001410. Each entry is sourced. Each internal finding is verbatim or closely paraphrased from the documents. No editorial conclusion is appended. The comparison speaks.</p><p>ENTRY 1 -- MYOCARDITIS</p><p>Public -- June 3, 2021 -- Health Canada / PHAC communique to health practitioners:</p><p>&#8216;No clear association has been established between myocarditis/pericarditis and mRNA vaccines, and to date, no regulatory action has been taken in Canada or internationally.&#8217;</p><p>Internal -- May 15, 2021 -- Health Canada SMSR review (ATI p.62):</p><p>Health Canada&#8217;s internal assessment concluded: &#8216;A possible link between the second vaccine dose and the onset of myocarditis among young men aged 16 to 30.&#8217; Three deaths in the global case series. 70% of cases within 7 days of second dose. Israel confirmed rate higher than background in young males.</p><p>Gap: Internal conclusion of possible link -- May 15, 2021. Public communication that no clear association established -- June 3, 2021. Nineteen days.</p><p>ENTRY 2 -- PREGNANCY SAFETY</p><p>Public -- Throughout 2021-2022 -- Health Canada and PHAC communications:</p><p>COVID-19 vaccination characterized as safe for pregnant people. No prominent public communication that clinical trial data for pregnant women was absent.</p><p>Internal -- Health Canada pregnancy ad-hoc review (ATI pp.208, 225, 229, 242, 271):</p><p>&#8216;The safety and efficacy of COVID-19 vaccines have been demonstrated in adults across a range of demographics, except on pregnant and lactating women due to the protection by exclusion during the clinical development stages.&#8217; No observed versus expected analysis for Comirnaty pregnancy outcomes. Canada not tracking vaccination status by pregnancy at population level. Pregnancy registry request to Pfizer -- declined. Health Canada accepted.</p><p>Gap: Pregnant women excluded from trials, vaccinated on extrapolated evidence, no O/E analysis, no population tracking, registry declined -- none of this communicated to pregnant Canadians with the clarity available in the internal documents.</p><p>ENTRY 3 -- SURVEILLANCE RIGOR</p><p>Public -- Throughout authorization period:</p><p>Post-market surveillance described as ongoing and rigorous. No public communication about reduction in monitoring intensity or removal of specific reporting requirements.</p><p>Internal -- BBRS Signal Tracking document, multiple entries (ATI Excel file, ATI pp.329, 349, 365):</p><p>Fatal reports observed versus expected analysis removed from monthly bivalent reporting at Pfizer&#8217;s request. Health Canada accepted. Monthly safety report requirement for all Comirnaty DINs formally closed May 29, 2023 -- internal memo language: &#8216;Repeal/close the following Ts&amp;Cs: The requirement to submit monthly safety reports for all DINs within the authorized Comirnaty product line.&#8217; Standard drug reporting applied by 2023.</p><p>Gap: Surveillance intensity was progressively negotiated down through bilateral exchanges with Pfizer and formally wound down by May 2023. This was not communicated to Canadians as a change in oversight.</p><p>ENTRY 4 -- THE DATA GAP</p><p>Public -- No public communication on this specific gap:</p><p>No Health Canada or PHAC public statement disclosed that real-time CAEFISS adverse event data was unavailable to Health Canada during the rollout.</p><p>Internal -- Health Canada internal pharmacovigilance review, June 2022 (ATI p.198):</p><p>&#8216;A detailed description of the adverse events reported to CAEFISS is not currently available to Health Canada.&#8217; 58,112,512 Comirnaty doses administered in Canada at this date. Two federal agencies. One national adverse event surveillance database. Unavailable to the regulator responsible for vaccine safety assessment in real time.</p><p>Gap: This finding was never publicly disclosed. It exists only in the internal document obtained through ATI Release A-2025-001410.</p><p>ENTRY 5 -- PEDIATRIC AUTHORIZATION</p><p>Public -- Authorization communications for children 6 months to 4 years:</p><p>Authorization presented as based on available evidence. No prominent public communication that no primary series clinical trial data existed for this age group.</p><p>Internal -- Health Canada internal RMP review memo (ATI p.392):</p><p>&#8216;While clinical data for the use of Comirnaty Original and Omicron BA.4/BA.5 vaccine as a primary series is not yet available, based on extrapolation of clinical data from its use as a booster dose.&#8217; Terms and Conditions for this age group were not finalized at the time of authorization -- Pfizer&#8217;s response to proposed terms was documented internally as &#8216;not acceptable,&#8217; content &#8216;under negotiation.&#8217;</p><p>Gap: Youngest Canadians authorized on extrapolated data with no primary series clinical trial data, before safety commitments were finalized. Current Comirnaty Product Monograph (August 10, 2026) states safety is &#8216;inferred primarily&#8217; from older population data. Confirmed in two independent primary sources.</p><p>ENTRY 6 -- THE CANADA-US TRANSMISSION BELT</p><p>Public -- Throughout pandemic period:</p><p>Canadian public health guidance presented as independently derived from Canadian evidence. No public communication that guidance was substantially downstream of American institutional decisions.</p><p>Internal -- Multiple primary sources, 2020-2026:</p><p>NACI guidance tracked CDC guidance closely throughout the pandemic. The six-foot rule, masking guidance, and vaccine safety communications all reflected American institutional positions with minimal lag. Fauci privately flagged first trimester miscarriage risk January 25, 2021 -- same period Health Canada internally flagged pregnancy as special monitoring category. American policy was made by an official who invoked the Fifth Amendment 100 times rather than defend those decisions under oath. His senior adviser pleaded guilty to records destruction.</p><p>Gap: Canadians were never told that the guidance shaping their lives originated substantially from an American institutional environment whose principal decision-maker will not defend his decisions under oath. Canadian parliamentarians have never been asked to account for what Canadian policy adopted from that environment.</p><p>The Government&#8217;s Response</p><p>On September 16, 2026, The Old Guardian sent a formal media request to the Office of Federal Health Minister Marjorie Michel, care of press secretary Emmanuelle Ducharme. The request summarized the five primary findings documented in this series and asked four specific questions:</p><p>Whether Health Canada acknowledges the CAEFISS data sharing gap documented in its own June 2022 internal review, and what steps have been taken to address it.</p><p>Whether the Minister has a response to the documented internal conclusion of a possible myocarditis link in May 2021 and the public communication that no clear association had been established nineteen days later.</p><p>What the Minister&#8217;s response is to the testimony of fifty Canadians at the Allison Inquiry, several of whose described injuries are consistent with adverse event categories tracked in Health Canada&#8217;s own internal pharmacovigilance records.</p><p>Whether the Minister supports a formal parliamentary inquiry into Health Canada&#8217;s COVID-19 vaccine pharmacovigilance conduct.</p><p>A response was requested by September 25, 2026.</p><p>[ This section will be updated with the Minister&#8217;s response or with documentation of non-response upon the September 25 deadline. ]</p><p>Three Data Points: An Institutional Portrait</p><p>The accountability record assembled in this series is Canadian. It is built on Canadian government documents, Canadian regulatory processes, and Canadian compensation program failures. It does not require the American accountability record to stand.</p><p>But the American record exists. And because Canadian policy was downstream of American decisions, it belongs in any complete accounting of what happened.</p><p>Three documented events. No editorial interpretation required.</p><p>November 22, 2022</p><p>&#8216;We can defend and explain and stand by everything that we&#8217;ve said. So I have nothing to hide.&#8217; -- Anthony Fauci, White House podium, final appearance before retirement. On the record. Unprompted.</p><p>July 29, 2026</p><p>Fauci appeared under subpoena before the Senate Homeland Security and Governmental Affairs Committee. He invoked the Fifth Amendment more than one hundred times. He declined to answer what day it was. Senator Josh Hawley asked him what colour tie he was wearing. Fifth Amendment. What colour is the carpet. Fifth Amendment. The committee voted to hold him in contempt. He subsequently declined voluntary appearance before a second panel. A man with a sweeping presidential pardon who still would not answer questions on the record.</p><p>August 18, 2026</p><p>Dr. David Morens, Fauci&#8217;s senior adviser at NIAID, pleaded guilty in federal court to plotting to conceal COVID-19 research records. The Department of Justice alleged he used his personal email account to intentionally circumvent public records laws and concealed or destroyed records related to COVID-19 research grants including an effort to revive a controversial coronavirus grant. Source: Associated Press, August 18, 2026.</p><p>The man who said he had nothing to hide is surrounded, by 2026, by a contempt finding, a guilty plea from his senior adviser, and 34,000 text messages still under review. Canadian policy was downstream of his decisions. Canadian parliamentarians have never been asked to account for what they adopted from that environment.</p><p>The Human Record</p><p>The documents in this series are 2,460 pages. The people in this section are not pages. They are Canadians whose experiences are consistent with the documented failures this series has mapped across five previous parts. They testified publicly under their own names at the Allison Inquiry in September 2026. Their accounts are part of the public record.</p><p>Cameron Hitchcock</p><p>Twenty-nine years old. Active and healthy. Second Pfizer dose, 2021. Diagnosed with nephrotic syndrome. Five months in hospital. Kidney failure. Dialysis six days a week. Waiting for a transplant. He arranged his dialysis schedule around travelling to Ottawa to testify. His Vaccine Injury Support Program claim was approved -- making him one of 252 Canadians the government acknowledged as vaccine-injured out of 3,557 who applied. He is recognized. He arranged dialysis around a trip to Parliament Hill because no formal accountability mechanism existed to hear him publicly.</p><p>Michael Oesch</p><p>He walked across Canada. Thousands of kilometres on foot. Fourth COVID dose, October 2022. Thirty-six hours later, walking with his granddaughter, his leg began dragging. Eventually he could not lift it. Severe neurological problems and spasms. An MRI revealed a 2.8 centimetre lesion near the top of his spinal cord close to his brain. He lost the ability to walk. He now lives in long-term care. His Vaccine Injury Support Program claim was denied. He walked across Canada. Now he can&#8217;t walk. His VISP claim was denied.</p><p>Jamie Daniel</p><p>She spent her career as a medical professional helping people in emergencies. Following COVID-19 vaccination she developed severe neurological symptoms. She was repeatedly dismissed. Called a drug seeker. Eventually diagnosed with transverse myelitis. While hospitalized, in severe pain, asking for help, a psychologist was brought in to discuss MAiD. She was in her early thirties. She had two young children at home. &#8216;I was asking for help,&#8217; she told the inquiry. &#8216;And instead, they offered to euthanize me.&#8217;</p><p>Scott Gorry</p><p>A former parliamentary staffer. He developed myocarditis following COVID-19 vaccination. He wanted to testify at the Allison Inquiry. He died on July 4, 2026 before he could. His sister Dr. Crystal Luchkiw testified in his place. She told the inquiry he had wanted his story told. She was telling it for him.</p><p>These four Canadians. Their injuries are consistent with the adverse event categories documented in Health Canada&#8217;s internal pharmacovigilance records obtained through ATI Release A-2025-001410. The surveillance system that was supposed to detect what happened to them had documented gaps before they received their doses. The compensation system that was supposed to acknowledge their injuries produced different outcomes for each of them -- one approved, one denied, one still waiting, one dead before he could testify.</p><p>The Accounting</p><p>More than thirty democratic countries, including most G7 and Commonwealth nations, have launched major COVID-19 inquiries examining lockdowns, mandates, vaccines, and government decision-making. The United Kingdom. Australia. New Zealand. Ireland. Sweden. Denmark.</p><p>Canada has not.</p><p>The closest Canada came was four days in September 2026. A privately organized forum. Volunteer effort. No government funding. No subpoena power. No findings of fact. Fifty witnesses out of 1,400 who came forward. Built by a Conservative MP, a constitutional lawyer, and their wives, asking each other whether they were supposed to do this.</p><p>When the federal Health Minister&#8217;s office was asked for comment on the Allison Inquiry&#8217;s testimony, the documented response was: &#8216;Vaccines are safe and effective and they save lives. We have no comment on the Allison Inquiry.&#8217;</p><p>That was the Government of Canada&#8217;s official response to fifty Canadians testifying publicly about life-altering injuries.</p><p>The documents are a different response. They are Health Canada&#8217;s own internal records. They show what regulators knew and when. They show what was communicated to the public and when. They show the gap between those two things, documented in the regulator&#8217;s own language, never intended for public release.</p><p>That gap is not a conspiracy. It does not require bad faith to explain. It requires institutional incentives, regulatory capture, the financial architecture of pharmaceutical development, and the political incentives of pandemic management -- operating in a system that was not designed with sufficient transparency to allow the public to know what its regulators were concluding internally.</p><p>The documents are now public. ATI file A-2025-001410. Released July 15, 2026. Available on request.</p><p>Canada has yet to undertake any parliamentary inquiry into COVID-19. More than thirty democratic countries have. The Allison Inquiry was four days. The Health Minister had no comment. The documents exist.</p><p>Cameron Hitchcock is on dialysis six days a week. Michael Oesch lives in long-term care. Jamie Daniel was offered MAiD while asking for help. Scott Gorry wanted to testify and died before he could.</p><p>The documents show what the surveillance system was designed to catch. The documents show what the surveillance system was not designed to catch. The documents show what the compensation system did with the people who fell through the gap.</p><p>This is the accounting.</p><p>What comes next is a choice that belongs to Parliament, to the Minister of Health, and to the Canadians who read these documents and decide what they mean.</p><p>The Old Guardian has documented the record. The record is now public. What happens next is not our choice to make.</p><p>It is yours.</p><p>About This Series</p><p>What They Knew is a six-part investigative series published by The Old Guardian between September 8 and September 2026. The series is built entirely on ATI Release A-2025-001410 -- 2,460 pages of Health Canada&#8217;s internal COVID-19 vaccine pharmacovigilance documents and 81 Excel files released by Health Canada on July 15, 2026, in response to a request filed by The Old Guardian under the federal Access to Information Act.</p><p>All claims in this series are sourced to named primary documents with specific page references. No claim was published without a primary source anchor. The sourcing standard is documented in each part&#8217;s editor&#8217;s notes.</p><p>The series does not claim that COVID-19 vaccines caused mass harm. It documents the gap between what regulatory records show and what the public was told -- and the data architecture failures that made independent verification of that gap impossible from available public information.</p><p>The full ATI release is available to journalists, researchers, and parliamentarians on request. Contact: tips@theoldguardian.ca</p><p>Primary Sources</p><p>ATI Release A-2025-001410</p><p>Health Canada, July 15, 2026. 2,460-page PDF and 81 Excel files. All internal citations in this series reference this release.</p><p>Comirnaty Product Monograph (August 10, 2026, Control Number 300388)</p><p>Current authorized Canadian product label. Independently corroborates ATI findings on myocarditis labelling (October 2024 update) and pediatric authorization evidence base.</p><p>Fauci text messages (August 10, 2026)</p><p>Released by Senators Ron Johnson and Rand Paul from Fauci&#8217;s government iPhone, produced by HHS. Source: ronjohnson.senate.gov. Confirmed by CBS News, The Hill, Newsweek.</p><p>Morens guilty plea (August 18, 2026)</p><p>Federal court. Source: Associated Press, August 18, 2026. CTV News.</p><p>Fauci White House statement (November 22, 2022)</p><p>White House press briefing transcript. Public record.</p><p>Senate Homeland Security hearing (July 29, 2026)</p><p>Fauci Fifth Amendment invocations and Hawley exchange. Confirmed by multiple wire services.</p><p>Allison Inquiry public testimony (September 8-11, 2026)</p><p>Cameron Hitchcock, Michael Oesch, Jamie Daniel, Dr. Crystal Luchkiw for Scott Gorry. All named witnesses testifying publicly under their own names. Public record.</p><p>Schmeling et al. 2023</p><p>Batch-dependent safety of BNT162b2. European Journal of Clinical Investigation. DOI: 10.1111/eci.13998.</p><p>Minister Michel media request (September 16, 2026)</p><p>Sent to emmanuelle.ducharme@hc-sc.gc.ca. Response requested by September 25, 2026. This section will be updated with response or documented non-response.</p><p>The Old Guardian -- theoldguardian.ca -- is an independent investigative outlet based in Toronto, Ontario. What They Knew was researched, reported, and written by Chris Allen.</p><p>Tips, corrections, and source contact: tips@theoldguardian.ca</p><p>The Old Guardian  |  theoldguardian.ca  |  tips@theoldguardian.ca  |  ATI File: A-2025-001410  |  What They Knew -- Complete</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-6-of-6-the-final?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-6-of-6-the-final?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/what-they-knew-part-6-of-6-the-final?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-6-of-6-the-final/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/what-they-knew-part-6-of-6-the-final/comments"><span>Leave a comment</span></a></p><p></p>]]></content:encoded></item><item><title><![CDATA[Pharmacovigilance - WHAT THEY KNEW | PART 5 OF 6]]></title><description><![CDATA[The Data Gap]]></description><link>https://www.theoldguardian.ca/p/what-they-knew-part-5-of-6</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/what-they-knew-part-5-of-6</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Thu, 17 Sep 2026 09:45:29 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/4766911a-e2fa-46ba-be80-5b8f30823a4d_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>THE OLD GUARDIAN</p><p>theoldguardian.ca  |  Independent Investigative Journalism</p><p>The implicit contract of emergency authorization is that rigorous post-market surveillance compensates for what compressed trials cannot capture. Health Canada&#8217;s own internal documents show that surveillance was negotiated down, progressively dismantled, and in at least one documented instance unavailable in real time between the two federal agencies responsible for it. The contract was not kept.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/subscribe?"><span>Subscribe now</span></a></p><p>By Chris Allen  |  The Old Guardian  |  September 2026</p><p>Primary source: ATI Release A-2025-001410, Health Canada, July 15, 2026</p><p>In June 2022, Health Canada produced an internal pharmacovigilance review of Comirnaty. By that point Canada had administered 58,112,512 doses of the Pfizer vaccine. The review was a comprehensive internal assessment of what the regulator knew about the safety of the product it had authorized.</p><p>On page 198 of that review -- obtained by The Old Guardian through federal Access to Information request A-2025-001410 -- appears a single sentence that stops the reader.</p><p>&#8216;A detailed description of the adverse events reported to CAEFISS is not currently available to Health Canada.&#8217;</p><p>CAEFISS is the Canadian Adverse Events Following Immunization Surveillance System -- the national vaccine safety surveillance database administered by the Public Health Agency of Canada. It is the primary mechanism through which adverse events following vaccination are collected, stored, and analyzed in Canada.</p><p>Health Canada is the federal regulator responsible for authorizing vaccines and monitoring their post-market safety.</p><p>By June 2022, 58 million doses into the largest vaccination campaign in Canadian history, these two federal agencies were not sharing complete adverse event data with each other in real time. The regulator responsible for vaccine safety assessment was making decisions based on incomplete information from the surveillance system it was supposed to be relying on.</p><p>That sentence -- written by Health Canada&#8217;s own internal reviewers, in a document never intended for public release -- is the thesis of this piece. Not a conspiracy. Not deliberate concealment. Something more structural and in some ways more troubling: a documented failure of the data architecture that was supposed to tell Canadian regulators what was happening to Canadians.</p><p>It was not the only failure. It was not even the largest one. But it was the one Health Canada acknowledged in its own words.</p><p>The Contract of Emergency Authorization</p><p>When Health Canada authorized Comirnaty on December 9, 2020 under an Interim Order -- a mechanism that allowed faster authorization than the standard drug approval pathway -- it was making a specific implicit promise to Canadians.</p><p>The promise was not that the vaccine was perfectly safe. It was that the evidence available at the time supported authorization, and that rigorous ongoing monitoring would catch anything the compressed pre-authorization timeline could not.</p><p>That is the contract of emergency authorization. Speed in, compensated by vigilance after. The pre-authorization timeline was compressed from years to months. The post-authorization surveillance was supposed to be the safety net that justified that compression.</p><p>The documents in this series tell the story of what happened to that safety net.</p><p>Parts 2 and 3 documented how Health Canada&#8217;s internal signal assessments used materially different language than public communications during the same period, and how surveillance requirements were progressively negotiated down through bilateral exchanges with Pfizer. Part 4 documented the specific data architecture failures in the pregnancy monitoring system -- no observed versus expected analysis for Comirnaty, no population-level tracking of vaccination by pregnancy status, a pregnancy registry request declined by Pfizer and accepted by Health Canada.</p><p>Part 5 assembles the complete picture. Four documented surveillance failures operating simultaneously. A safety net with multiple holes, at a moment when millions of Canadians were relying on it to catch what the trials had not.</p><p>Source: ATI Release A-2025-001410, Health Canada internal pharmacovigilance review, June 2022, page 198.</p><p>Failure One: The CAEFISS Gap</p><p>The Public Health Agency of Canada administers CAEFISS. Health Canada administers Canada Vigilance -- a separate adverse event reporting database. During the COVID-19 vaccine rollout, these two systems were supposed to function as complementary pillars of Canada&#8217;s vaccine safety surveillance architecture.</p><p>The ATI documents show they were not functioning as a unified system. Health Canada&#8217;s internal reviewers were conducting weekly Canada Vigilance database searches and receiving monthly Summary Safety Reports from Pfizer. They were monitoring international regulatory signals through the Article Tracking Sheets documented in the 81 Excel files released alongside the main ATI package. They were producing internal signal assessments and issuing advisement letters to Pfizer when signals warranted action.</p><p>What they did not have -- as their own June 2022 internal review explicitly states -- was a detailed description of the adverse events reported to CAEFISS.</p><p>The practical consequence of this gap is significant. CAEFISS and Canada Vigilance captured overlapping but not identical populations and event types. Healthcare providers submitted reports to one system or the other based on their reporting pathway. Individual patients and families submitted reports through different mechanisms. The two databases together were supposed to give Health Canada and PHAC a complete picture of what was happening in Canada. Instead they were each giving their respective agencies a partial picture, and those partial pictures were not being systematically integrated in real time.</p><p>Two federal agencies. Two databases. 58 million doses administered. The regulator responsible for vaccine safety assessment acknowledged in its own internal documents that it did not have access to the national adverse event surveillance data in real time.</p><p>This is not an allegation that data was hidden or deliberately withheld. Institutional data gaps between co-existing federal agencies are a structural problem that predates COVID. The significance of this particular gap is its timing -- occurring during the largest and fastest vaccination campaign in Canadian history, at the precise moment when real-time surveillance data was most consequential.</p><p>Source: ATI Release A-2025-001410, Health Canada internal pharmacovigilance review, June 2022, page 198. BBRS Signal Tracking document, multiple entries referencing Canada Vigilance database searches.</p><p>Failure Two: The Pregnancy Tracking Gap</p><p>Part 4 of this series documented this failure in detail. Its inclusion here is brief but necessary because it belongs in the complete picture of the surveillance architecture.</p><p>Canada was not tracking vaccination status by pregnancy at the population level. The internal documents confirm this on page 229: &#8216;this information is not tracked in Canada.&#8217;</p><p>The 290 pregnancy-related adverse event reports recorded in Canada to May 2022 -- including 127 classified as serious and 72 spontaneous abortion reports -- existed in a denominator vacuum. The total number of pregnant Canadians who were vaccinated during this period was not precisely known. The rate of adverse pregnancy outcomes in vaccinated versus unvaccinated pregnant Canadians was not calculable from available data.</p><p>Health Canada&#8217;s request for a pregnancy registry -- which would have created the denominator -- was declined by Pfizer in August 2021. Health Canada accepted that answer. The denominator gap remained throughout the entire rollout period.</p><p>A surveillance system that cannot calculate rates cannot detect signals. A signal detection system without a denominator is a passive collection mechanism, not an active monitoring architecture. That is what Canada had for pregnancy outcomes during the COVID-19 vaccine rollout.</p><p>Source: ATI Release A-2025-001410, pages 229, 271, 273-274.</p><p>Failure Three: The Batch Variability Gap</p><p>In 2023, a peer-reviewed study published in the European Journal of Clinical Investigation examined 971,021 reports of suspected adverse effects in the EU and European Economic Area. The study, by Schmeling and colleagues, analyzed Danish national health data and found something that has significant implications for how population-level vaccine safety surveillance is interpreted.</p><p>Adverse event rates varied dramatically by vaccine batch lot number. Batches representing approximately 4% of total doses administered were associated with dramatically higher adverse event reporting rates than other batches, with R-squared values between 0.78 and 0.89 -- indicating strong statistical correlation between batch identity and adverse event reports. The remaining 96% of doses showed much lower and more uniform adverse event rates.</p><p>The mechanism for this finding is manufacturing variability. Different production runs, different manufacturing sites, and different production batches can produce vaccines with differing mRNA concentrations and lipid nanoparticle characteristics. This is a known pharmaceutical manufacturing challenge. It is why lot release testing exists as a regulatory requirement.</p><p>The Canadian connection to this finding is documented in the ATI release. The BBRS Signal Tracking spreadsheets reference manufacturing site changes for Comirnaty including the approval of a WuXi Biologics production site in Germany during the authorization period. Multiple manufacturing sites, multiple production runs, multiple potential sources of batch-level variability -- all operating simultaneously during the Canadian rollout.</p><p>The surveillance architecture implication is significant. Canada Vigilance tracked adverse events by vaccine product and dose number. The BBRS monitoring documents reviewed for this series do not reference lot-level analysis as a standard surveillance tool. If adverse event rates varied significantly by production batch -- as the Schmeling study documents in European data -- then population-level surveillance that did not systematically track lot numbers would miss a signal that lot-level analysis would detect.</p><p>If some batches produced dramatically higher adverse event rates than others, a surveillance system tracking product-level data rather than lot-level data would average those rates together -- diluting the signal from the high-adverse-event batches into the background noise of the low-adverse-event batches.</p><p>This is not a claim that Health Canada knew about specific dangerous batches and concealed them. It is a documented surveillance architecture limitation: the monitoring system was not designed to detect lot-level variation in adverse event rates, and peer-reviewed European data suggests that lot-level variation was real and significant.</p><p>Source: Schmeling M et al., Batch-dependent safety of the BNT162b2 mRNA COVID-19 vaccine. European Journal of Clinical Investigation, 2023. DOI: 10.1111/eci.13998. ATI Release A-2025-001410, BBRS Signal Tracking document, WuXi Biologics manufacturing site references.</p><p>Failure Four: The Surveillance Wind-Down</p><p>Parts 2 and 3 documented the progressive reduction of surveillance intensity through the authorization period. Its inclusion in Part 5 as a fourth surveillance failure is deliberate: it belongs in the complete picture of what the safety net looked like by the time most Canadians received their doses.</p><p>In December 2020, when Comirnaty was first authorized, the surveillance architecture was intensive. Daily Canada Vigilance database searches. Monthly Summary Safety Reports from Pfizer. Active signal monitoring across all authorized DINs. Observed versus expected analyses for fatal reports. Article Tracking Sheets monitoring international regulatory signals in real time.</p><p>By May 29, 2023, Health Canada had issued a formal memo closing the monthly safety report requirement for all Comirnaty DINs. The internal language: &#8216;Repeal/close the following Ts&amp;Cs: The requirement to submit monthly safety reports for all DINs within the authorized Comirnaty product line.&#8217; Standard COVID-19 specific reporting had been replaced with standard drug reporting requirements -- the same framework governing routine medications that had been on the market for decades.</p><p>The surveillance architecture went from maximum intensity to routine post-market monitoring in approximately three years. During that same period, the youngest age group authorization was still relatively recent. Long-term safety data remained incomplete. The batch variability question documented above had not been resolved. The pregnancy tracking gap had not been filled. The CAEFISS data sharing gap had not been publicly disclosed.</p><p>The contract of emergency authorization -- speed in, compensated by vigilance after -- had a time limit that was not disclosed to Canadians. The vigilance ended while the questions remained open.</p><p>Source: ATI Release A-2025-001410, BBRS Signal Tracking document, May 29, 2023 entry. ATI p.329, p.365.</p><p>What the Gaps Mean Together</p><p>Four surveillance failures. Each documented in Health Canada&#8217;s own internal records or in peer-reviewed literature using national health data. Each individually significant. Together, they describe a monitoring architecture that was systematically less capable of detecting rare adverse events than the public was led to believe.</p><p>The CAEFISS gap meant the regulator was working from an incomplete picture of domestic adverse events in real time. The pregnancy tracking gap meant rare adverse pregnancy outcomes could not be detected even if they were occurring. The batch variability gap meant lot-level adverse event signals were invisible to product-level surveillance. The surveillance wind-down meant the monitoring that was supposed to compensate for compressed authorization timelines was progressively dismantled before the long-term safety picture was complete.</p><p>None of these failures required bad faith to produce. They are the predictable outcomes of institutional design choices -- a federal data architecture that kept surveillance databases separate between PHAC and Health Canada, a regulatory framework that relied on manufacturer cooperation for post-market commitments, a surveillance methodology built for population-level signal detection rather than lot-level analysis, and a risk-based approach to reducing monitoring intensity that prioritized administrative efficiency over comprehensive long-term surveillance.</p><p>The cumulative effect of these design choices was a safety net that was less capable than it appeared -- and than the public was told.</p><p>Emergency authorization compressed the pre-authorization timeline. Post-market surveillance was supposed to compensate. The documents show that surveillance was itself compromised by data gaps, negotiated reductions, and progressive wind-down before the safety picture was complete. The contract was not kept.</p><p>Cameron Hitchcock: What the Gap Looked Like</p><p>Cameron Hitchcock was 29 years old, active and healthy, when he received his second Pfizer dose in 2021. His health deteriorated soon after. His body began swelling. His kidneys were losing protein at an alarming rate. He was eventually diagnosed with nephrotic syndrome. What followed was approximately five months in hospital and, ultimately, kidney failure.</p><p>Today Cameron requires dialysis six days a week. He is waiting for a kidney transplant. He arranged his dialysis schedule around travelling to Ottawa so he could testify publicly at the Allison Inquiry in September 2026.</p><p>His Vaccine Injury Support Program claim was eventually approved -- making him one of the 252 Canadians whose claims cleared the compensation threshold out of 3,557 who applied.</p><p>The government&#8217;s own compensation program acknowledged a connection between Cameron&#8217;s vaccination and his kidney failure serious enough to warrant payment. He is, by the program&#8217;s own determination, a vaccine-injured Canadian whose injury met the evidentiary standard for recognition.</p><p>And yet in September 2026, five years after his second dose, he was arranging dialysis around a trip to Ottawa to testify at a privately organized forum because no formal parliamentary inquiry, no government-commissioned review, and no institutional accountability mechanism had ever existed to publicly hear his account.</p><p>The surveillance system that was supposed to detect what happened to Cameron had documented gaps before he received his second dose. The CAEFISS data was not available to Health Canada in real time. Lot-level adverse event analysis was not a standard surveillance tool. The monitoring architecture was already being negotiated down. The data infrastructure that would have caught a signal like his -- if his experience was part of a pattern -- was less capable than the public knew.</p><p>Whether the gaps contributed to Cameron&#8217;s specific outcome cannot be established from available evidence. What can be established is that the safety net was less complete than it appeared, that its limitations were documented internally and not publicly disclosed, and that a man who arranged dialysis around a trip to Ottawa to be heard is still waiting for a kidney while the institutions that were supposed to be watching received a VISP cheque in acknowledgment of what they missed.</p><p>Editor&#8217;s Notes and Primary Sources</p><p>All findings in this piece are drawn directly from ATI Release A-2025-001410, released by Health Canada to The Old Guardian on July 15, 2026, and from peer-reviewed scientific literature. Specific documents cited:</p><p>ATI p.198</p><p>Health Canada internal pharmacovigilance review, June 2022 -- &#8216;A detailed description of the adverse events reported to CAEFISS is not currently available to Health Canada.&#8217; Verbatim internal language.</p><p>ATI p.229</p><p>Canada not tracking vaccination status by pregnancy at population level -- &#8216;this information is not tracked in Canada.&#8217; Verbatim internal language.</p><p>ATI p.271</p><p>August 3, 2021 pregnancy registry request to Pfizer -- declined, Health Canada accepted, no further action taken.</p><p>BBRS Signal Tracking (ATI Excel file)</p><p>Complete internal project tracking log 2020-2023. May 29, 2023 entry documents formal closure of monthly safety report requirements for all Comirnaty DINs. WuXi Biologics manufacturing site approval referenced. Weekly Canada Vigilance database search protocols documented.</p><p>ATI p.329</p><p>Health Canada formal documentation of reduced monitoring intensity -- &#8216;adopting a risk-based approach...reducing oversight on indications where the safety profile has been better characterized.&#8217;</p><p>ATI p.365</p><p>By 2023 -- standard COVID-19 specific reporting framework replaced with standard drug reporting requirements.</p><p>Schmeling et al. 2023</p><p>Batch-dependent safety of the BNT162b2 mRNA COVID-19 vaccine. European Journal of Clinical Investigation. DOI: 10.1111/eci.13998. Danish national health data. 971,021 EU/EEA adverse event reports analyzed. Batch lot identity correlated with adverse event rates at R2 0.78-0.89. Approximately 4% of batches associated with dramatically elevated adverse event reporting.</p><p>Cameron Hitchcock</p><p>Public testimony, Allison Inquiry, September 2026. Nephrotic syndrome following second Pfizer dose 2021. Kidney failure. Dialysis six days weekly. VISP claim approved. One of 252 approved claims from 3,557 applicants.</p><p>The Old Guardian&#8217;s six-part series What They Knew examines Health Canada&#8217;s internal COVID-19 vaccine pharmacovigilance records. Part 6 -- The Accounting -- publishes shortly. ATI file: A-2025-001410.</p><p>If you or a family member experienced a serious adverse event following COVID-19 vaccination, contact The Old Guardian at tips@theoldguardian.ca. Source confidentiality is protected. Verification is required.</p><p>The Old Guardian  |  theoldguardian.ca  |  tips@theoldguardian.ca  |  ATI File: A-2025-001410</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;c8bbd542-2e0d-44ab-b4eb-7912cac41dd0&quot;,&quot;caption&quot;:&quot;THE OLD GUARDIAN&quot;,&quot;cta&quot;:null,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;lg&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;WHAT THEY KNEW | PART 6 OF 6 | THE FINAL PART&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:315040924,&quot;name&quot;:&quot;Christopher Allen&quot;,&quot;bio&quot;:&quot;Welcome, Guardians. Success isn&#8217;t just money, it&#8217;s truth, community, and the journey. This space is for real talk, sharp thinking, and pushing back on the noise. I want your feedback. Speak up. Let&#8217;s build something that lasts.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/3461b478-c850-4d26-bc9c-672624b0cb55_1024x1024.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2026-09-18T09:45:37.033Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/80e270fc-f891-42f8-876a-8508050f6704_1536x1024.png&quot;,&quot;cover_image_alt&quot;:null,&quot;canonical_url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-6-of-6-the-final&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:216227119,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:3999531,&quot;publication_name&quot;:&quot;The Old Guardian&#8217;s Substack&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!ChDO!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba010f10-0b41-4234-90ec-1c87c7233e20_1280x1280.png&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-5-of-6?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-5-of-6?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/what-they-knew-part-5-of-6?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-5-of-6/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/what-they-knew-part-5-of-6/comments"><span>Leave a comment</span></a></p><p></p>]]></content:encoded></item><item><title><![CDATA[Pharmacovigilance - WHAT THEY KNEW | PART 4 OF 6]]></title><description><![CDATA[Protection by Exclusion]]></description><link>https://www.theoldguardian.ca/p/what-they-knew-part-4-of-6</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/what-they-knew-part-4-of-6</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Tue, 15 Sep 2026 09:45:43 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/ac9af8ba-8748-459a-9aab-b12400cb5df2_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>THE OLD GUARDIAN</p><p>theoldguardian.ca  |  Independent Investigative Journalism</p><p>Pregnant women were excluded from Pfizer&#8217;s COVID-19 clinical trials. Then they were vaccinated on extrapolated evidence while Health Canada internally flagged their population for special monitoring. The gap between what was known and what was tracked is documented in federal records -- and in the lives of Canadian women who were never told. </p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/subscribe?"><span>Subscribe now</span></a></p><p>By Chris Allen  |  The Old Guardian  |  September 2026</p><p>Primary source: ATI Release A-2025-001410, Health Canada, July 15, 2026</p><p>Three words appear in Health Canada&#8217;s own internal pharmacovigilance review of Comirnaty. They appear on page 208 of a 2,460-page document obtained by The Old Guardian under federal Access to Information request A-2025-001410.</p><p>The words are: protection by exclusion.</p><p>The full sentence reads: &#8216;The safety and efficacy of COVID-19 vaccines have been demonstrated in adults across a range of demographics, except on pregnant and lactating women due to the protection by exclusion during the clinical development stages.&#8217;</p><p>Protection by exclusion. It is a phrase from the regulatory world meaning that a population is protected from the risks of a clinical trial by not being included in it. It is a standard practice in early-stage drug development for good reasons -- pregnant women are a vulnerable population and trial risks are unknown.</p><p>But protection by exclusion is not the same as evidence of safety. It means the opposite. It means no data exists. It means the question was not answered in the controlled setting that would answer it definitively. It means that when those same excluded women were subsequently vaccinated -- in the millions, across Canada, under varying degrees of social and institutional pressure -- they were vaccinated on the basis of extrapolation, not evidence.</p><p>Health Canada&#8217;s own internal documents say so directly. The product monograph authorized August 10, 2026 says so publicly. And the consequences of that gap -- between what was studied and what was assumed, between what was tracked and what was communicated -- are documented in the lives of Canadian women who were never told that the protection extended to them was not evidence. It was an absence of data dressed as reassurance.</p><p>The Clinical Trial Exclusion: Confirmed in Internal Documents</p><p>Health Canada&#8217;s internal pregnancy ad-hoc review, conducted in 2022, is explicit on this point. Beyond the page 208 passage already quoted, page 225 of the same ATI release states:</p><p>&#8216;Despite their higher risk of SARS-CoV-2 infection, pregnant and lactating women were not included in any initial COVID-19 vaccine trials.&#8217;</p><p>Higher risk of severe COVID-19 outcomes. Excluded from the trials designed to establish safety. Then vaccinated as part of the population for whom vaccination was recommended.</p><p>This sequence -- exclusion, then authorization, then vaccination -- is not a secret. It was acknowledged in regulatory language at the time. What was not communicated with equivalent clarity was what exclusion actually meant for the evidence base. The public messaging in Canada characterized COVID-19 vaccination as safe for pregnant people. The internal documents confirm that characterization was made in the absence of the controlled clinical data that would have supported it.</p><p>The current authorized Comirnaty Product Monograph, dated August 10, 2026, independently confirms this. Section 7.1.1 states: &#8216;There are limited clinical study data from the use of COMIRNATY (Original) in pregnant women.&#8217; For the variant-adapted formulations that Canadians received in 2022 and beyond: &#8216;No clinical study data are available regarding the use of variant-adapted COMIRNATY during pregnancy.&#8217;</p><p>No clinical study data. For the formulations that pregnant Canadians received. That language is on the official product label right now.</p><p>Source: ATI Release A-2025-001410, Health Canada internal pregnancy ad-hoc review, pages 208, 225. Comirnaty Product Monograph, August 10, 2026, Section 7.1.1, p.14.</p><p>No Observed Versus Expected Analysis: The Missing Calculation</p><p>When Health Canada monitors post-authorization adverse events for a vaccine, one of its primary tools is the observed versus expected analysis. It compares the rate of adverse events actually reported against the rate that would be statistically expected in a comparable unvaccinated population of similar size and demographics. A rate above the expected range is a signal. A signal triggers investigation.</p><p>For the myocarditis signal documented in Part 2 of this series, an observed versus expected analysis existed. It was the tool that allowed Health Canada&#8217;s internal reviewers to conclude a &#8216;possible link&#8217; between the second dose and myocarditis in young males.</p><p>For Comirnaty pregnancy outcomes, no such analysis existed.</p><p>Page 242 of the ATI release states it directly: &#8216;Comirnaty: No observed versus expected analysis.&#8217;</p><p>For comparison, Spikevax -- Moderna&#8217;s mRNA vaccine -- had an observed versus expected analysis for pregnancy outcomes during the same period. For Pfizer&#8217;s product, which was the primary vaccine administered to the majority of Canadians, it did not exist.</p><p>Without an observed versus expected analysis, Health Canada&#8217;s internal reviewers were working without the primary statistical tool that would have allowed them to detect whether adverse pregnancy outcomes were occurring at a rate above background. They were monitoring a population they had no baseline to compare against, for a drug they had no primary trial data for, using a surveillance system that -- as documented elsewhere in these records -- was itself operating with incomplete data.</p><p>No observed versus expected analysis existed for Comirnaty pregnancy outcomes. The primary statistical tool for detecting adverse signals was absent for the vaccine most Canadians received.</p><p>Source: ATI Release A-2025-001410, Health Canada internal pregnancy ad-hoc review, page 242.</p><p>Canada Was Not Tracking: The Population-Level Data Gap</p><p>Beyond the absence of an observed versus expected analysis for Comirnaty specifically, there was a more fundamental data gap documented in these records.</p><p>Page 229 of the ATI release states: &#8216;This was not restricted to pregnancy status of the females as the data for this subpopulation is not available; this information is not tracked in Canada.&#8217;</p><p>Canada was not tracking vaccination status by pregnancy at the population level. The country administered millions of doses to women of reproductive age without a systematic mechanism to identify which of those women were pregnant at the time of vaccination, what their pregnancy outcomes were, and whether those outcomes differed from the unvaccinated pregnant population.</p><p>The 290 pregnancy-related adverse event reports recorded in Canada to May 31, 2022 -- including 127 classified as serious and 72 spontaneous abortion reports -- came from a passive surveillance system. Passive surveillance means healthcare providers and patients submit reports voluntarily. The literature consistently documents that passive surveillance systems capture a fraction of actual adverse events -- estimates typically range from five to ten percent of events being reported.</p><p>The 72 spontaneous abortion reports in the Canadian database were assessed against Brighton Collaboration case definitions. The median time to onset was eleven days. The range was two hours to sixty-three days.</p><p>But those reports existed in a denominator vacuum. The total number of pregnant Canadians who were vaccinated during this period was not precisely known. The rate of spontaneous abortion in vaccinated pregnant Canadians compared to unvaccinated pregnant Canadians was not calculable from available data. Health Canada&#8217;s own evaluators noted in their review that Canadian AEFI reports &#8216;lacked clinical evaluation and medical confirmation&#8217; -- that the data quality was insufficient to draw conclusions even from the reports that were submitted.</p><p>The surveillance system was passive, incomplete, and operating without a population-level denominator. That is not a conspiracy. It is a documented failure of data architecture that predates COVID. But it is a failure that had direct consequences for the ability of Canadian regulators to detect rare adverse events in pregnant women even if those events were occurring.</p><p>Source: ATI Release A-2025-001410, pages 229, 273-274, 281. Health Canada internal pregnancy ad-hoc review.</p><p>Pfizer Declined the Registry: A Request on the Record</p><p>Health Canada identified this gap. On August 3, 2021, Health Canada sent a formal request to Pfizer-BioNTech asking the company to implement a pregnancy registry for Canada and reference it in the Canadian Product Monograph.</p><p>A pregnancy registry would have allowed prospective tracking of vaccinated pregnant Canadians and their outcomes. It would have created the denominator that passive surveillance lacked. It would have generated the data that would have made an observed versus expected analysis possible.</p><p>Pfizer declined. The company cited existing post-authorization studies already underway internationally. It stated it had no plans to update the Canadian Product Monograph to include information on pregnancy registries.</p><p>Health Canada accepted this response. The internal BBRS Signal Tracking document records the exchange without editorial comment. The request was made. The response was received. No further action was taken.</p><p>The data gap that prompted the request remained. The absence of an observed versus expected analysis for Comirnaty pregnancy outcomes remained. Canada remained unable to track vaccination status by pregnancy at the population level. And the public messaging continued to characterize COVID-19 vaccination as safe for pregnant people -- a characterization made in the absence of the registry data that would have actually supported it.</p><p>Health Canada asked Pfizer to build the data infrastructure that would have allowed proper pregnancy safety monitoring. Pfizer said no. Health Canada accepted that answer. The data gap remained.</p><p>Source: ATI Release A-2025-001410, BBRS Signal Tracking document, August 3, 2021 entry. ATI page 271.</p><p>What Fauci Texted Walensky: A Cross-Border Parallel</p><p>On January 25, 2021 -- seven months before Health Canada formally requested and was denied a Canadian pregnancy registry -- the director of the National Institute of Allergy and Infectious Diseases sent a text message to the director of the Centers for Disease Control and Prevention.</p><p>The text was from Anthony Fauci to Rochelle Walensky. It was released by Senators Ron Johnson and Rand Paul on August 10, 2026, from Fauci&#8217;s government-issued iPhone, produced by HHS.</p><p>Fauci wrote: &#8216;Since many people have significant cytokines storm and fever after the 2nd dose, this theoretically could be associated with miscarriage in the 1st trimester.&#8217;</p><p>Walensky&#8217;s response called it &#8216;definitely a good point, especially after dose two.&#8217;</p><p>Days later, Fauci publicly stated that thousands of vaccinated pregnant women had shown &#8216;no red flags.&#8217; Seven months later, Health Canada was still trying to get Pfizer to build the data infrastructure that would have allowed detection of rare adverse pregnancy events.</p><p>The Fauci text does not prove vaccines caused miscarriages. It establishes that the senior American public health official who was the dominant voice of the pandemic response privately acknowledged a theoretical first trimester miscarriage risk at the same time his public messaging said no red flags existed. That gap -- between private concern and public reassurance -- ran on both sides of the border simultaneously.</p><p>Canadian public health messaging was downstream of American guidance. When Fauci said no red flags, Canadian health authorities reflected that position. The internal documents on both sides of the border show the picture was more complicated than the public was told.</p><p>Source: Fauci text messages, released by Senators Ron Johnson and Rand Paul, August 10, 2026. Primary source: ronjohnson.senate.gov. CBS News confirmation August 10, 2026.</p><p>The Breastfeeding Gap: Six Years Later</p><p>There is one line in the current authorized Comirnaty Product Monograph -- the document that governs how Canadian healthcare practitioners advise patients on this vaccine right now, in September 2026 -- that captures the scope of what remains unknown.</p><p>Section 7.1.2, under Breastfeeding, states: &#8216;No data are available yet regarding the use of COMIRNATY during breast-feeding.&#8217;</p><p>No data are available yet. Six years after initial authorization. Six years after Canadian nursing mothers made decisions about vaccination based on the reassurance that it was safe. The word &#8216;yet&#8217; implies the data is coming. After six years, it has not arrived.</p><p>This is not a claim that vaccination harmed nursing mothers or their infants. It is a documented fact that six years after Comirnaty was first authorized in Canada, the product label still acknowledges the absence of breastfeeding safety data. The public messaging during the vaccination campaign did not communicate equivalent uncertainty. Nursing mothers were not routinely told that the safety data for their specific situation did not exist.</p><p>Source: Comirnaty Product Monograph, August 10, 2026, Control Number 300388. Section 7.1.2, p.14.</p><p>The Human Cost: Two Ontario Women</p><p>The data gaps documented in this piece are not abstract. They have faces.</p><p>Kayla Pollock is an Ontario woman who received a Moderna booster shot in February 2022. Within days she developed acute transverse myelitis -- inflammation of the spinal cord -- that left her paralyzed from the chest down with limited function in her arms. While hospitalized, she was offered MAiD twice. She refused both times. Her VISP claim remained unfinalized as of the most recent available reporting. Her case was reported by CBC News in April 2026.</p><p>Jamie Daniel spent her career as a medical professional helping people in emergencies. Following COVID-19 vaccination she developed severe neurological symptoms. She was repeatedly dismissed by healthcare providers. Called a drug seeker. Eventually diagnosed with transverse myelitis. While hospitalized, in severe pain, asking for help, a psychologist was brought in to discuss MAiD. She was in her early thirties. She had two young children at home. She testified publicly at the Allison Inquiry on September 11, 2026.</p><p>&#8216;I was asking for help,&#8217; Jamie told the inquiry panel. &#8216;And instead, they offered to euthanize me.&#8217;</p><p>Transverse myelitis is documented in Health Canada&#8217;s internal pharmacovigilance records as one of the neurological adverse events tracked in Canada. The ATI documents show 759 neurological events recorded for Comirnaty in Canada by June 2022. The surveillance system tracked the category. It did not have the data architecture to track the denominators that would have allowed detection of a population-level signal.</p><p>Whether vaccination caused Kayla Pollock&#8217;s or Jamie Daniel&#8217;s transverse myelitis is not a question this series can answer. What this series can document is that the data infrastructure that might have answered that question -- the pregnancy registry Pfizer declined to build, the observed versus expected analysis that didn&#8217;t exist for Comirnaty, the population-level tracking that Canada didn&#8217;t do -- was absent. And in that absence, two women were left without answers. One was told to start her compensation claim over after three years of waiting. The other was offered death while asking for help.</p><p>The data infrastructure that might have detected rare adverse events in vulnerable populations was documented as absent. Two Ontario women were left in that absence without answers.</p><p>Source: Kayla Pollock case -- CBC News, April 2026. Jamie Daniel -- public testimony, Allison Inquiry, September 11, 2026. Neurological adverse events -- ATI Release A-2025-001410, page 198.</p><p>What This Means</p><p>This piece does not argue that COVID-19 vaccines harmed pregnant women, nursing mothers, or women of reproductive age as a population. The evidence does not support that claim and TOG does not make it.</p><p>What the evidence supports is precise and documented. Pregnant women were excluded from the clinical trials that established Comirnaty&#8217;s safety profile. They were subsequently vaccinated on extrapolated evidence while Health Canada internally flagged their population for special monitoring. No observed versus expected analysis existed for Comirnaty pregnancy outcomes. Canada did not track vaccination status by pregnancy at the population level. Pfizer declined to build the registry that would have filled that gap. Health Canada accepted that answer. The public was not told that the evidence base for vaccination in pregnancy rested on extrapolation rather than direct clinical data.</p><p>Three words in Health Canada&#8217;s own internal documents describe what happened to pregnant women in the clinical development of Comirnaty. Protection by exclusion.</p><p>The protection of exclusion from a trial is real. It means pregnant women were not exposed to the risks of an experimental drug in a controlled setting. That is a genuine form of protection.</p><p>But exclusion from a trial is not the same as evidence of safety. And in the gap between those two things -- between the protection of not being studied and the assumption of safety that followed -- millions of Canadian women made decisions about vaccination that the evidence base, honestly communicated, would have allowed them to make differently.</p><p>That gap is the accountability record this piece documents.</p><p>Editor&#8217;s Notes and Primary Sources</p><p>All findings in this piece are drawn directly from ATI Release A-2025-001410, released by Health Canada to The Old Guardian on July 15, 2026, and from the current authorized Comirnaty Product Monograph dated August 10, 2026. Specific documents cited:</p><p>ATI p.208</p><p>Health Canada internal pregnancy ad-hoc review -- &#8216;protection by exclusion during the clinical development stages.&#8217; Verbatim internal language.</p><p>ATI p.225</p><p>&#8216;Despite their higher risk of SARS-CoV-2 infection, pregnant and lactating women were not included in any initial COVID-19 vaccine trials.&#8217; Verbatim internal language.</p><p>ATI p.242</p><p>Comirnaty: &#8216;No observed versus expected analysis&#8217; for pregnancy outcomes. For Spikevax, an O/E analysis existed.</p><p>ATI p.229</p><p>&#8216;This information is not tracked in Canada.&#8217; Canada not tracking vaccination status by pregnancy at population level.</p><p>ATI p.271</p><p>August 3, 2021 pregnancy registry request to Pfizer -- Pfizer declined, Health Canada accepted, no further action taken.</p><p>ATI p.273-274</p><p>290 pregnancy-related adverse event reports in Canada to May 31, 2022. 127 serious. 72 spontaneous abortion reports. Median onset: 11 days. Range: 2 hours to 63 days.</p><p>ATI p.281</p><p>Health Canada evaluators -- Canadian AEFI reports &#8216;lacked clinical evaluation and medical confirmation.&#8217; Data quality insufficient to draw conclusions.</p><p>ATI p.198</p><p>759 neurological events tracked in Canada for Comirnaty by June 2022.</p><p>Comirnaty Product Monograph (August 10, 2026, Control Number 300388)</p><p>Section 7.1.1: &#8216;limited clinical study data&#8217; for COMIRNATY Original in pregnant women. &#8216;No clinical study data&#8217; for variant-adapted formulations in pregnancy. Section 7.1.2: &#8216;No data are available yet regarding the use of COMIRNATY during breast-feeding.&#8217;</p><p>Fauci text messages (August 10, 2026)</p><p>January 25, 2021 text to Walensky: &#8216;this theoretically could be associated with miscarriage in the 1st trimester.&#8217; Source: ronjohnson.senate.gov. Confirmed by CBS News, The Hill, Newsweek.</p><p>Kayla Pollock</p><p>CBC News, April 2026. Transverse myelitis following Moderna booster, February 2022. MAiD offered twice during hospitalization.</p><p>Jamie Daniel</p><p>Public testimony, Allison Inquiry, September 11, 2026. Transverse myelitis following COVID-19 vaccination. MAiD offered while hospitalized with two young children at home.</p><p>The Old Guardian&#8217;s six-part series What They Knew examines Health Canada&#8217;s internal COVID-19 vaccine pharmacovigilance records. The series publishes in September 2026. ATI file: A-2025-001410.</p><p>If you or a family member experienced a serious adverse event following COVID-19 vaccination, contact The Old Guardian at tips@theoldguardian.ca. Source confidentiality is protected. Verification is required.</p><p>The Old Guardian  |  theoldguardian.ca  |  tips@theoldguardian.ca  |  ATI File: A-2025-001410</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-4-of-6/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/what-they-knew-part-4-of-6/comments"><span>Leave a comment</span></a></p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-4-of-6?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-4-of-6?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/what-they-knew-part-4-of-6?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Pharmacovigilance - WHAT THEY KNEW | PART 3 OF 6]]></title><description><![CDATA[The Negotiation]]></description><link>https://www.theoldguardian.ca/p/what-they-knew-part-3-of-6</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/what-they-knew-part-3-of-6</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Mon, 14 Sep 2026 09:45:44 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/a925c635-7671-4c5a-b1fd-3ac956130e93_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>THE OLD GUARDIAN</p><p>theoldguardian.ca  |  Independent Investigative Journalism</p><p>WHAT THEY KNEW  |  PART 3 OF 6</p><p>The Negotiation</p><p>Health Canada asked Pfizer for a pregnancy registry. Pfizer declined. Health Canada accepted. That exchange -- documented in internal records -- is one of four negotiated decisions that shaped what Canadians were and were not told about their COVID-19 vaccines.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/subscribe?"><span>Subscribe now</span></a></p><p>By Chris Allen  |  The Old Guardian  |  September 2026</p><p>Primary source: ATI Release A-2025-001410, Health Canada, July 15, 2026</p><p>On August 3, 2021, Health Canada sent a formal request to Pfizer-BioNTech.</p><p>The request was specific. Given that serious pregnancy outcomes were being reported to Canadian surveillance databases following Comirnaty vaccination -- 64 spontaneous abortion reports by that point, 290 pregnancy-related adverse events total -- Health Canada asked Pfizer to implement a pregnancy registry for Canada and reference it in the Canadian Product Monograph.</p><p>Pfizer declined. The company cited existing post-authorization studies already underway. It stated it had no plans to update the Canadian Product Monograph to include information on pregnancy registries.</p><p>Health Canada accepted this response. No further action was taken.</p><p>That exchange -- a regulator asking, a manufacturer declining, the regulator standing down -- is documented in 2,460 pages of internal Health Canada pharmacovigilance records obtained by The Old Guardian under federal Access to Information request A-2025-001410.</p><p>It is not the only exchange of its kind in those documents.</p><p>Post-market vaccine surveillance is not a passive monitoring system sitting quietly in the background recording what happens. It is an active negotiation between regulator and manufacturer -- over what gets studied, what gets labeled, what gets reported, and when. The ATI documents provide a granular record of that negotiation for Comirnaty across multiple formulations and age group extensions.</p><p>Several findings in that record are not consistent with the public description of rigorous independent oversight.</p><p>The Pregnancy Registry: A Request Declined</p><p>The August 3, 2021 pregnancy registry request did not emerge from nowhere. It was the product of months of internal monitoring that Health Canada had been conducting since early 2021.</p><p>By August 2021, Health Canada&#8217;s internal pharmacovigilance reviewers had already flagged pregnancy as a special monitoring category. The internal documents show that MHPD -- the Marketed Health Products Directorate -- had been tracking pregnancy outcomes since the earliest SMSR review periods.</p><p>The monitoring was warranted. The documents confirm that Canada was not tracking vaccination status by pregnancy at the population level. The internal review stated explicitly: &#8216;this information is not tracked in Canada.&#8217; The 64 spontaneous abortion reports in the Canadian database were from a passive surveillance system with acknowledged underreporting. The denominator -- how many pregnant Canadians were actually vaccinated -- was not known with precision.</p><p>Against that backdrop, Health Canada made a reasonable request. A pregnancy registry would have allowed prospective tracking of vaccinated pregnant Canadians and their outcomes -- filling the data gap the internal documents acknowledged existed.</p><p>Pfizer said no.</p><p>Health Canada&#8217;s internal BBRS Signal Tracking document records the exchange without editorial comment. The request was made. The response was received. No further action was taken. The data gap that prompted the request remained unfilled.</p><p>Canada was not tracking vaccination by pregnancy status at the population level. Health Canada asked Pfizer to help fill that gap. Pfizer declined. Health Canada accepted that answer.</p><p>The public communication during this same period continued to characterize COVID-19 vaccination as safe for pregnant people. The internal documents confirm that characterization was made in the absence of the registry data that would have actually supported it.</p><p>Source: ATI Release A-2025-001410, BBRS Signal Tracking document, August 3, 2021 entry. ATI p.271. ATI p.229.</p><p>Bell&#8217;s Palsy: A Label Negotiation on the Record</p><p>The pregnancy registry was not the only documented negotiation between Health Canada and Pfizer in this period.</p><p>Running parallel to the pregnancy monitoring thread was a signal Health Canada internally tracked across multiple Summary Monthly Safety Report review periods: Bell&#8217;s Palsy and facial paralysis cases following Comirnaty vaccination.</p><p>By the fifth and sixth SMSR review periods, 434 serious facial paralysis cases had been recorded in a single reporting interval. Health Canada formally disagreed with Pfizer&#8217;s assessment that this signal could be closed. The internal documents record Health Canada&#8217;s position in writing: the signal warranted product monograph -- label -- updates. Health Canada requested Pfizer make those updates.</p><p>Pfizer resisted including Bell&#8217;s Palsy in the clinical trial section of the product monograph. The internal BBRS Signal Tracking document records the disagreement explicitly. An advisement letter was issued to Pfizer on July 14, 2021. Pfizer&#8217;s response characterized the evidence as inconclusive.</p><p>Health Canada&#8217;s documented position: &#8216;Health Canada&#8217;s position remains the same and the need for further risk mitigation will be discussed with our pre-market colleagues.&#8217;</p><p>This is not a regulator passively accepting whatever a manufacturer provided. Health Canada pushed back. The disagreement is in writing. What is also in writing is that the resolution of that disagreement -- what ultimately appeared on the label, and when -- took place in a process that the public had no visibility into.</p><p>434 serious facial paralysis cases. A documented negotiation between regulator and manufacturer over whether and how to disclose them. The outcome of that negotiation determined what Canadian healthcare practitioners read on the product label when advising their patients.</p><p>Source: ATI Release A-2025-001410, SMSR review pages 62-63. BBRS Signal Tracking document, July 12-14, 2021 entries.</p><p>Children Six Months to Four Years: Authorized Before Terms Were Final</p><p>The authorization of Comirnaty for children six months to four years old is where the internal documents produce their most significant finding in this negotiation record.</p><p>Health Canada proposed Terms and Conditions to Pfizer governing post-market safety commitments for this age group. Pfizer&#8217;s response to those proposed terms was documented internally as &#8216;not acceptable.&#8217; The content of the Terms and Conditions was described as &#8216;under negotiation.&#8217;</p><p>A meeting was held September 8, 2022 to work through the disagreement.</p><p>The authorization for children six months to four years proceeded before the Terms and Conditions were finalized. Comirnaty was authorized for the youngest Canadians before the safety commitments governing post-market monitoring for that age group were fully agreed upon between the regulator and the manufacturer.</p><p>A separate internal memo makes a related finding explicit. For the Comirnaty Original and Omicron BA.4/BA.5 bivalent vaccine authorized as a primary series for children six months to under five years, the internal review states: &#8216;While clinical data for the use of Comirnaty Original and Omicron BA.4/BA.5 vaccine as a primary series is not yet available, based on extrapolation of clinical data from its use as a booster dose.&#8217;</p><p>The youngest Canadians eligible for Comirnaty were authorized on extrapolated data from booster dose studies in older populations. No primary series clinical trial data existed for this age group at the time of authorization. That is documented in Health Canada&#8217;s own internal review memo.</p><p>Comirnaty was authorized for children six months to four years before the Terms and Conditions governing their safety monitoring were finalized. The internal documents say so directly.</p><p>The public communication around pediatric authorization did not reflect this. Parents making decisions about vaccinating their youngest children were not told that the authorization preceded finalization of safety commitments, or that it rested on extrapolated rather than primary series data.</p><p>Source: ATI Release A-2025-001410, ATI p.296. ATI p.392. Internal RMP review memo, pediatric extension.</p><p>Product Monograph corroboration: The current authorized Comirnaty Product Monograph (August 10, 2026, Control Number 300388) independently confirms this finding. Section 8.1.3 states that the safety of the bivalent primary series for children 6 months to 4 years is &#8220;inferred primarily from the safety profile of COMIRNATY at 3 mcg&#8221; -- the same extrapolation language documented in ATI p.392. The product label itself uses the word &#8220;inferred&#8221; to describe the evidentiary basis for authorizing the youngest Canadians. That is now on the public record in two independent primary sources.</p><p>Fatal Reports Removed: The Bivalent Surveillance Reduction</p><p>As successive bivalent formulations were authorized -- BA.1, then BA.4/BA.5, then XBB.1.5 -- the surveillance architecture that had governed the original Comirnaty authorization progressively relaxed.</p><p>The most significant documented reduction involved fatal reports.</p><p>For the original Comirnaty formulation, monthly safety reports included observed versus expected analyses of fatal adverse events -- a systematic comparison of reported deaths against the statistical baseline that would be expected in a population of similar size and demographics. That analysis was the core tool for detecting whether vaccine-associated death rates exceeded background rates.</p><p>For the BA.4/BA.5 bivalent vaccine, Pfizer proposed removing the fatal reports observed versus expected analysis requirement from monthly reporting. The internal BBRS Signal Tracking document records what happened next: &#8216;Accepted as removed by MAH.&#8217;</p><p>Health Canada accepted Pfizer&#8217;s proposal. Fatal report tracking for the bivalent vaccines was moved from monthly reports to the less frequent six-monthly Periodic Safety Update Reports.</p><p>The frequency of fatal report monitoring was reduced at the manufacturer&#8217;s request, and the regulator agreed.</p><p>Health Canada&#8217;s internal documentation frames this as a risk-based approach: &#8216;adopting a risk-based approach in the post-market surveillance strategy by reducing the oversight on indications where the safety profile has been better characterized.&#8217;</p><p>Whether the bivalent vaccine&#8217;s safety profile had been sufficiently characterized to warrant reducing fatal report monitoring frequency is a question the public was never asked. The decision was made internally, documented in the BBRS tracking log, and not communicated as a change in surveillance intensity to Canadians who continued receiving bivalent doses.</p><p>Source: ATI Release A-2025-001410, BBRS Signal Tracking document, BA.4/BA.5 bivalent entries. ATI p.349. ATI p.329.</p><p>The Surveillance Wind-Down: A Documented Timeline</p><p>The four negotiations documented above did not occur in isolation. They occurred within a broader trajectory of declining surveillance intensity that the ATI documents allow reconstruction of with precision.</p><p>In December 2020, when Comirnaty was first authorized, the surveillance architecture was intensive. Daily Canada Vigilance database searches. Monthly summary safety reports. Active signal monitoring across all authorized DINs. Observed versus expected analyses for fatal reports.</p><p>By late 2021, the scope of required analyses was under active negotiation between Health Canada and Pfizer. By 2022, bivalent authorizations began proceeding with Terms and Conditions negotiated post-authorization. Fatal reports observed versus expected analysis was removed from monthly bivalent reporting.</p><p>By December 2022, the monthly reporting requirement was removed for most DINs and replaced with six-monthly Periodic Safety Update Reports.</p><p>By May 29, 2023, Health Canada issued a formal memo to BRDD closing the monthly safety report requirement entirely and amending Terms and Conditions across all Comirnaty DINs. The exact internal language: &#8216;Repeal/close the following Ts&amp;Cs: The requirement to submit monthly safety reports for all DINs within the authorized Comirnaty product line.&#8217;</p><p>By 2023, standard COVID-19 specific reporting was replaced with standard drug reporting requirements -- the same framework that governs routine medications that have been on the market for decades.</p><p>Comirnaty went from the most intensively monitored pharmaceutical product in Canadian regulatory history to a standard marketed drug in approximately three years. That transition was managed through a documented negotiation process. It was not publicly communicated as a reduction in oversight.</p><p>In three years, Comirnaty went from the most intensively monitored pharmaceutical in Canadian regulatory history to a standard marketed drug. The transition was negotiated. It was not announced.</p><p>Source: ATI Release A-2025-001410, BBRS Signal Tracking document, May 29, 2023 entry. ATI p.329. ATI p.365.</p><p>What This Means</p><p>The negotiation record documented in these ATI files does not describe a corrupt regulator or a dishonest manufacturer. It describes something more systemic and in some ways more difficult to address: a post-market surveillance architecture that operated as a bilateral negotiation between regulator and manufacturer, largely invisible to the public it was designed to protect.</p><p>Health Canada asked for a pregnancy registry. Pfizer said no. Health Canada accepted that.</p><p>Health Canada disagreed with Pfizer&#8217;s assessment of the Bell&#8217;s Palsy signal. The disagreement was documented. The resolution happened behind closed doors.</p><p>Pfizer&#8217;s response to proposed Terms and Conditions for the youngest Canadians was &#8216;not acceptable.&#8217; Authorization proceeded while the negotiation continued.</p><p>Pfizer proposed removing fatal report monitoring from monthly bivalent reporting. Health Canada accepted.</p><p>None of these decisions were communicated to Canadians as decisions. They were administrative determinations made within a regulatory process that operates without public visibility. Canadians receiving subsequent doses, making decisions for their children, asking their doctors whether the vaccines were still being monitored with the same rigour as when they were first authorized -- none of them had access to the negotiation record that would have answered that question.</p><p>The documents do not tell us what the right decisions were. Reasonable regulatory experts could disagree about whether each of these outcomes was appropriate given the evidence available at the time. What the documents tell us is that these decisions were made, that they were documented, and that the public was not told they had been made.</p><p>That gap -- between the documented internal negotiation and the public&#8217;s assumed understanding of rigorous independent oversight -- is the accountability record this series is building.</p><p>One further dimension of context is worth noting. The company Health Canada was negotiating with over safety monitoring requirements, label language, and surveillance obligations is the same company that, by 2026, had obtained a Belgian court judgment of approximately 1.9 billion euros against Poland and Romania for COVID-19 vaccine doses those governments refused to take delivery of in 2022 as pandemic demand collapsed -- and was enforcing that judgment by garnishing air traffic control funds through the Eurocontrol system. The Wall Street Journal reported on September 13, 2026 that Poland&#8217;s air navigation services agency had received notification from Eurocontrol about the freezing of route charge transfers as Pfizer enforced its court award. The EU-Pfizer contract -- negotiated through personal text messages between Commission President von der Leyen and Pfizer CEO Albert Bourla, subsequently the subject of transparency investigations -- was structured as a take-or-pay agreement heavily favorable to the manufacturer. Member states that did not successfully negotiate exits were held to their full purchase commitments regardless of whether doses were accepted or administered.</p><p>This is not a finding about Canada&#8217;s specific procurement arrangements, which had their own advance purchase agreements whose terms have not been fully disclosed publicly. It is context for understanding the institutional power asymmetry within which Health Canada&#8217;s documented negotiations over safety monitoring requirements, pregnancy registry requests, and surveillance obligations were taking place. The company that declined to build a Canadian pregnancy registry when Health Canada asked, and successfully negotiated the removal of fatal report monitoring from monthly bivalent reporting, operates within a commercial framework that its pandemic-era contracts with sovereign governments demonstrate in full.</p><p>Editor&#8217;s Notes and Primary Sources</p><p>All findings in this piece are drawn directly from ATI Release A-2025-001410, released by Health Canada to The Old Guardian on July 15, 2026. Specific documents cited:</p><p>ATI p.271</p><p>August 3, 2021 pregnancy registry request to Pfizer -- Pfizer declined, Health Canada accepted, no further action taken.</p><p>ATI p.229</p><p>Health Canada internal review confirming vaccination status by pregnancy not tracked at population level in Canada.</p><p>ATI p.62-63</p><p>Bell&#8217;s Palsy/facial paralysis -- 434 serious cases in one reporting interval, documented Health Canada / Pfizer disagreement on signal closure and label language.</p><p>ATI p.296</p><p>6-month to 4-year authorization -- Pfizer response to Terms and Conditions &#8216;not acceptable,&#8217; content &#8216;under negotiation,&#8217; authorization proceeded.</p><p>ATI p.392</p><p>Internal memo confirming bivalent authorized as primary series for 6-month to 4-year age group on extrapolated booster data -- no primary series clinical trial data available.</p><p>ATI p.349</p><p>BA.4/BA.5 bivalent -- fatal reports O/E analysis requirement removed from monthly reporting at Pfizer&#8217;s request, &#8216;Accepted as removed by MAH.&#8217;</p><p>ATI p.329</p><p>Health Canada formal documentation of reduced monitoring intensity -- &#8216;adopting a risk-based approach...reducing oversight on indications where safety profile has been better characterized.&#8217;</p><p>ATI p.365</p><p>By 2023 -- standard COVID-19 specific reporting framework replaced with standard drug reporting requirements.</p><p>BBRS Signal Tracking (ATI Excel file)</p><p>Internal project tracking log 2020-2023 -- complete chronological record of all advisement letters, memos, Terms and Conditions negotiations, and surveillance changes across the full Comirnaty authorization period. May 29, 2023 entry documents formal closure of monthly safety report requirements.</p><p>Comirnaty Product Monograph (August 10, 2026, Control Number 300388)</p><p>Section 8.1.3 -- Safety of bivalent primary series for children 6 months to 4 years is &#8220;inferred primarily from the safety profile of COMIRNATY at 3 mcg.&#8221; Independently corroborates ATI p.392 finding on extrapolated pediatric authorization. Section 7 Cardiovascular -- Myocarditis and pericarditis warning added, October 2024. Independently corroborates ATI p.62 myocarditis signal timeline.</p><p>The Old Guardian&#8217;s six-part series What They Knew examines Health Canada&#8217;s internal COVID-19 vaccine pharmacovigilance records. The series publishes in September 2026 in conjunction with the Allison Inquiry hearings at Parliament Hill. ATI file: A-2025-001410.</p><p>If you or a family member experienced a serious adverse event following COVID-19 vaccination, contact The Old Guardian at tips@theoldguardian.ca. Source confidentiality is protected. Verification is required.</p><p>The Old Guardian  |  theoldguardian.ca  |  tips@theoldguardian.ca  |  ATI File: A-2025-001410</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;97c046e9-23ea-4bb9-9661-1ffbfb71cc5c&quot;,&quot;caption&quot;:&quot;THE OLD GUARDIAN&quot;,&quot;cta&quot;:null,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;lg&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;WHAT THEY KNEW | PART 4 OF 6&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:315040924,&quot;name&quot;:&quot;Christopher Allen&quot;,&quot;bio&quot;:&quot;Welcome, Guardians. Success isn&#8217;t just money, it&#8217;s truth, community, and the journey. This space is for real talk, sharp thinking, and pushing back on the noise. I want your feedback. Speak up. Let&#8217;s build something that lasts.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/3461b478-c850-4d26-bc9c-672624b0cb55_1024x1024.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2026-09-15T09:45:43.344Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/612b74d9-6c87-4509-897e-ff05b55dadd3_1536x1024.png&quot;,&quot;cover_image_alt&quot;:null,&quot;canonical_url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-4-of-6&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:215758053,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:3999531,&quot;publication_name&quot;:&quot;The Old Guardian&#8217;s Substack&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!ChDO!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba010f10-0b41-4234-90ec-1c87c7233e20_1280x1280.png&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-3-of-6/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/what-they-knew-part-3-of-6/comments"><span>Leave a comment</span></a></p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-3-of-6?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-3-of-6?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/what-they-knew-part-3-of-6?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[TDSB - 1.49 Million Students. One Board. Not Enough Was Done.]]></title><description><![CDATA[The Old Guardian]]></description><link>https://www.theoldguardian.ca/p/149-million-students-one-board-not</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/149-million-students-one-board-not</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Sun, 13 Sep 2026 18:30:52 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/0cf08c9c-f189-47ac-a88f-d6fda56fa16d_1672x941.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The Old Guardian</p><p>Long before a provincial supervisor walked into TDSB headquarters, the board&#8217;s own systems were already failing the people they were supposed to protect. Ontario&#8217;s privacy watchdog has now said so directly.</p><p>What Happened</p><p>In December 2024, hackers breached PowerSchool, the vendor TDSB and thousands of other school districts across North America relied on to store student information. By January, TDSB confirmed the scope for its own students: roughly 1.49 million current and former students had addresses, health card numbers, emergency contacts, and in some cases medical information exposed. Some of the records dated back decades.</p><p>PowerSchool paid the hackers to delete the stolen data. It didn&#8217;t work. In May, the same attacker came back, this time demanding ransom directly from the affected school boards using data from the original breach.</p><p>This wasn&#8217;t TDSB&#8217;s only cybersecurity failure that year. A separate 2024 breach hit a test environment the board was using, one that, against basic security practice, contained real production data instead of synthetic test data. Roughly 280,000 students and staff had their information exposed through that incident alone. Then in 2025, a social engineering attack compromised a vice-principal&#8217;s login credentials, giving an outside actor access to systems across several schools.</p><p>The Regulator&#8217;s Verdict</p><p>Ontario&#8217;s Information and Privacy Commissioner investigated. In November 2025, the office found that TDSB and other GTA boards did not have &#8220;reasonable measures&#8221; in place to prevent the breach, pointing specifically to insufficient oversight of the vendor entrusted with the data in the first place.</p><p>That&#8217;s not a hacker outsmarting a well-defended system. That&#8217;s a regulator concluding the defence wasn&#8217;t adequate to begin with.</p><p>Why This Belongs in the Supervision Conversation</p><p>Every one of these incidents happened before the province placed TDSB under supervision. The board&#8217;s defenders, and this outlet has made the same point, have argued that supervision was justified by a real, documented pattern of governance failure: no long-term capital plan, the worst facility conditions in the province, safety incidents underreported to the Ministry. Add vendor oversight to that list. A board responsible for the personal information of 1.49 million students didn&#8217;t have the controls in place to protect it, and needed a regulator to say so before anything changed.</p><p>None of that means everything that has happened since supervision began is justified by it. Those are separate questions, and this outlet has been careful to keep them separate. But anyone arguing TDSB&#8217;s pre-supervision record was fine, or that the Ministry&#8217;s intervention had no real basis, has to explain this file too.</p><p>Where TDSB Actually Fell Short, and Where It Didn&#8217;t</p><p>TDSB&#8217;s own letters to families tell a different story than the one that might seem obvious here, and it&#8217;s worth getting the distinction right. PowerSchool notified the board on January 7, 2025. TDSB sent a preliminary letter to families the very next day. By January 20, a far more detailed follow-up, signed by then-Interim Director of Education Stacey Zucker, laid out exactly which categories of data were exposed, broken down by date range, down to the specific detail that Social Insurance Numbers and financial information were never stored in the system and were never at risk. In May, a third letter, this one signed by Clayton La Touche, informed families that the ransom PowerSchool paid to have the stolen data deleted had failed, and that a threat actor was now using the same data to demand payment directly from school boards.</p><p>That&#8217;s a fast, specific, repeatedly updated communication record. Whatever else TDSB got wrong here, keeping families informed once the breach was discovered isn&#8217;t it.</p><p>The failure the IPC identified sits earlier in the chain. Notifying people quickly after a breach is not the same as having the vendor oversight to prevent one. TDSB handled the aftermath of this incident about as well as an aftermath can be handled. The question that actually matters, the one the Commissioner answered, is why a board responsible for 1.49 million people&#8217;s personal information didn&#8217;t have controls in place strong enough to stop the breach from happening at all.</p><p>Sources: CBC News, Global News, CP24, the Office of the Information and Privacy Commissioner of Ontario, and TDSB&#8217;s public letters to families dated January 8, January 20, and May 7, 2025.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/149-million-students-one-board-not/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/149-million-students-one-board-not/comments"><span>Leave a comment</span></a></p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/149-million-students-one-board-not?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/149-million-students-one-board-not?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/149-million-students-one-board-not?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Pharmacovigilance - WHAT THEY KNEW | PART 2 OF 6]]></title><description><![CDATA[The Signal They Saw]]></description><link>https://www.theoldguardian.ca/p/what-they-knew-part-2-of-6</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/what-they-knew-part-2-of-6</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Thu, 10 Sep 2026 09:45:48 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/6024ac10-2f0f-4f7d-a065-d10af1781c8d_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>THE OLD GUARDIAN</p><p>theoldguardian.ca  |  Independent Investigative Journalism</p><p>WHAT THEY KNEW  |  PART 2 OF 6</p><p>The Signal They Saw</p><p>Health Canada&#8217;s internal documents show a myocarditis signal was detected in February 2021, confirmed as a probable link by May, and present in 657 Canadian cases by June 2022. The public was told something different.</p><p>By Chris Allen  |  The Old Guardian  |  September 2026</p><p>Primary source: ATI Release A-2025-001410, Health Canada, July 15, 2026</p><p>On February 15, 2021, Israel&#8217;s Ministry of Health flagged something to Pfizer. Eight weeks after the world&#8217;s most aggressive vaccine rollout began, Israeli health officials had noticed a pattern in young men. They called it myocarditis -- inflammation of the heart muscle. They believed the vaccine was connected. They wanted answers.</p><p>In Ottawa, Health Canada was listening.</p><p>What happened over the next four months -- what regulators concluded internally, what they told Pfizer, what they told each other, and what they told the Canadian public -- is now documented in 2,460 pages of internal Health Canada pharmacovigilance records obtained by The Old Guardian under federal Access to Information request A-2025-001410.</p><p>The documents reveal a gap. Not a conspiracy. Not a cover-up in the dramatic sense. Something more bureaucratic and in some ways more troubling: a documented difference between the strength of what regulators knew internally and the strength of what they communicated publicly, on a question that affected millions of Canadians who were rolling up their sleeves and trusting that the full picture was being shared with them.</p><p>It was not.</p><p>February to May 2021: What the Internal Record Shows</p><p>The myocarditis signal moved quickly through the regulatory system once Israel raised it. According to internal Health Canada documents, Pfizer was formally notified of the Israeli concern on February 15, 2021. Health Canada began its own internal review.</p><p>By May 15, 2021 -- three months after the Israeli flag -- Pfizer provided Health Canada with a cumulative global safety review of the myocarditis and pericarditis signal. The numbers in that review were significant. As of that date, 108 myocarditis cases and 92 pericarditis cases had been reported in the post-authorization database globally. Three deaths were recorded in the case series.</p><p>Seventy percent of the myocarditis cases occurred within seven days of the second dose. The pattern was consistent: young males, second dose, within a week.</p><p>Health Canada&#8217;s internal assessment concluded: &#8216;A possible link between the second vaccine dose and the onset of myocarditis among young men aged 16 to 30.&#8217;</p><p>That conclusion -- a possible link -- was dated May 2021. It was documented in Health Canada&#8217;s internal Summary Monthly Safety Report review. It was not a fringe concern from an anti-vaccine researcher. It was the working assessment of Canada&#8217;s federal drug regulator, derived from its own review of Pfizer&#8217;s global safety data.</p><p>Israel had already confirmed a rate higher than background in young males. Health Canada&#8217;s internal reviewers agreed the signal was real enough to characterize as a possible causal relationship with the second dose.</p><p>Source: ATI Release A-2025-001410, Health Canada internal SMSR review, May 2021. Page 62.</p><p>June 3, 2021: What the Public Was Told</p><p>On June 3, 2021 -- nineteen days after Health Canada&#8217;s internal reviewers had documented a possible link between the vaccine and myocarditis in young men -- the Public Health Agency of Canada and Health Canada issued a communique to health practitioners across Canada.</p><p>The communique stated that &#8216;no clear association has been established between myocarditis/pericarditis and mRNA vaccines, and to date, no regulatory action has been taken in Canada or internationally.&#8217;</p><p>That statement was technically accurate in a narrow regulatory sense. A possible link documented in an internal review is not the same as a formally established causal association. Health Canada had not yet issued a formal advisory. No regulatory action had been formally taken.</p><p>But consider what practitioners reading that communique on June 3 would have understood: that the relationship between myocarditis and mRNA vaccines was unclear, that it had not been established, that no action had been taken.</p><p>What they were not told: that Health Canada&#8217;s own internal reviewers had, nineteen days earlier, characterized the relationship as a possible link. That 108 myocarditis cases and 92 pericarditis cases had been recorded globally. That three deaths were in the case series. That 70 percent of cases occurred within seven days of the second dose in young males.</p><p>The public language and the internal language described the same signal in materially different terms.</p><p>Source: Health Canada / PHAC communique to health practitioners, June 3, 2021. ATI Release A-2025-001410, page 62.</p><p>June 25, 2021: The Advisement Letter</p><p>Ten days after the June 3 communique characterized the myocarditis relationship as unclear, Health Canada issued a formal Advisement Letter to Pfizer on June 25, 2021. The letter was triggered by what the internal BBRS Signal Tracking document describes as &#8216;local and international signal&#8217; on myocarditis and pericarditis.</p><p>The advisement letter is significant for two reasons. First, it confirms that Health Canada had moved from internal assessment to formal regulatory action within weeks of the May 15 cumulative review. Second, it establishes a precise institutional timeline: Health Canada knew enough to formally advise Pfizer on June 25, but the public communique on June 3 had characterized the signal as unclear.</p><p>The sequence matters. The internal clock was running faster than the public clock.</p><p>Source: ATI Release A-2025-001410, BBRS Signal Tracking document 2020-2023, June 25, 2021 entry.</p><p>The Bell&#8217;s Palsy Parallel: A Documented Negotiation</p><p>The myocarditis story does not stand alone in these documents. Running parallel to it is the Bell&#8217;s Palsy signal -- facial paralysis cases following vaccination -- which illustrates how the relationship between Health Canada and Pfizer operated in practice when a safety signal was contested.</p><p>By the fifth and sixth Summary Monthly Safety Report review periods, 434 serious facial paralysis cases had been recorded in a single reporting interval. Health Canada formally disagreed with Pfizer&#8217;s assessment that this signal could be closed. The internal documents show Health Canada requested that Pfizer update the product monograph -- the label -- to reflect the facial paralysis signal.</p><p>Pfizer resisted including it in the clinical trial section of the product monograph. The internal documents record this disagreement explicitly. Health Canada&#8217;s position, documented in writing: &#8216;Health Canada&#8217;s position remains the same and the need for further risk mitigation will be discussed with our pre-market colleagues.&#8217;</p><p>This is not a regulator passively accepting whatever a manufacturer provided. Health Canada pushed back. The negotiation is documented. What is also documented is that the resolution of that negotiation -- what ultimately appeared on the label, and when -- took place in a process that the public had no visibility into.</p><p>Source: ATI Release A-2025-001410, SMSR review pages 62-63. BBRS Signal Tracking document, July 12-14, 2021 entries.</p><p>By June 2022: 657 Canadian Cases</p><p>Health Canada&#8217;s internal pharmacovigilance review dated June 24, 2022 provides the most comprehensive Canadian-specific adverse event data in the entire ATI release.</p><p>As of that date, across 58,112,512 Comirnaty doses administered in Canada, Health Canada&#8217;s internal tracking recorded 657 confirmed myocarditis and pericarditis cases in Canada for the Pfizer vaccine specifically.</p><p>To put that number in context: this is not a VAERS-style passive surveillance figure where anyone can submit a report. This is Health Canada&#8217;s own internal count of confirmed cases from its pharmacovigilance monitoring -- the most rigorous counting methodology available in Canada&#8217;s regulatory system.</p><p>657 confirmed Canadian myocarditis and pericarditis cases. Three deaths in the global case series. A signal detected in February 2021, internally characterized as a possible link by May 2021, formally acted upon in June 2021.</p><p>The public communication during this same period consistently used language like &#8216;rare,&#8217; &#8216;mild,&#8217; and &#8216;resolves quickly.&#8217; Those characterizations may have been accurate on average. But &#8216;rare&#8217; for an individual case is not the same as 657 confirmed Canadian cases in a regulatory database that the public had no direct access to.</p><p>Source: ATI Release A-2025-001410, Health Canada internal pharmacovigilance review, June 24, 2022. Page 198.</p><p>The Ad-Hoc Review and the Benefits-Outweigh-Risks Conclusion</p><p>The ATI documents contain a dedicated ad-hoc myocarditis review memo produced by Health Canada&#8217;s internal reviewers. The memo&#8217;s conclusion is the one that became Health Canada&#8217;s public position: the benefits of vaccination outweigh the risks of myocarditis.</p><p>That conclusion may well be correct. The evidence on COVID severity, hospitalization rates, and vaccine effectiveness in reducing both -- particularly in the early pandemic waves -- supports the benefits side of that ledger for most age groups.</p><p>But the memo reaches that conclusion while simultaneously documenting three deaths in the myocarditis case series, a 70 percent rate of cases within seven days of second dose in young males, and an Israeli confirmation of a rate higher than background.</p><p>The question this document raises is not whether the conclusion was wrong. The question is whether Canadians who were being asked to receive a second dose -- particularly young males between 16 and 30 -- were given the same information that Health Canada&#8217;s internal reviewers were working from when they reached that conclusion.</p><p>The internal memo had the numbers. The public advisories had the conclusion.</p><p>Source: ATI Release A-2025-001410, ad-hoc myocarditis review memo. Page 97.</p><p>The Label That Took Three and a Half Years</p><p>The myocarditis signal documented in Health Canada&#8217;s internal records in May 2021 eventually made it onto the Comirnaty product monograph -- the official label that healthcare practitioners read when advising patients. It took three and a half years.</p><p>The Recent Major Label Changes section of the current authorized Comirnaty product monograph -- dated August 10, 2026 -- shows a single entry for the cardiovascular warnings section: October 2024. That is when Health Canada updated the label to reflect the myocarditis and pericarditis signal that internal documents show was characterized as a possible link in May 2021.</p><p>The current label now states that myocarditis and pericarditis cases &#8220;occurred more commonly after the second dose or first booster dose in adolescent and young adult males&#8221; and that &#8220;fatal events have been very rarely reported.&#8221; It acknowledges that &#8220;information on long-term sequelae is lacking.&#8221;</p><p>That language -- young adult males, second dose, fatal events very rarely reported -- mirrors precisely what Health Canada&#8217;s internal reviewers concluded in May 2021. The conclusion existed internally for three and a half years before it appeared on the label that Canadian healthcare practitioners and their patients were supposed to read.</p><p>Every Canadian who received a second dose between May 2021 and October 2024 did so without that information on the label. Every healthcare practitioner advising a young male patient during that period was working from a label that did not reflect what Health Canada&#8217;s own internal assessment had concluded.</p><p>Source: Comirnaty Product Monograph, Health Canada, authorized August 10, 2026. Control Number: 300388. Recent Major Label Changes section, page 2. Section 7 Warnings and Precautions -- Cardiovascular, page 13.</p><p>What This Means</p><p>The myocarditis signal was real. Health Canada knew it was real. Health Canada eventually said so publicly -- in language that came later and landed softer than the internal assessment.</p><p>The gap documented in these records is not fabricated, not inferred, and not speculative. It is a dateable sequence of internal documents and public communications that used materially different language to describe the same signal at the same time.</p><p>February 15, 2021: Israel flags the signal.</p><p>May 15, 2021: Health Canada&#8217;s internal reviewers conclude &#8216;possible link.&#8217;</p><p>June 3, 2021: Health Canada&#8217;s public communique says &#8216;no clear association established.&#8217;</p><p>June 25, 2021: Health Canada issues a formal advisement letter to Pfizer.</p><p>June 2022: 657 confirmed Canadian cases in the internal pharmacovigilance database.</p><p>This is not a story about malicious intent. It is a story about institutional communication standards -- what regulators owe the public they serve when the internal picture and the public picture diverge.</p><p>657 Canadians with confirmed myocarditis or pericarditis in Health Canada&#8217;s own database. Each of them made a decision about a second dose while the public language said no clear association had been established. Each of them deserved to know what Health Canada&#8217;s internal reviewers already knew.</p><p>The internal memo had the numbers. The public advisories had the conclusion. Canadians were given one but not the other.</p><p>Editor&#8217;s Notes and Primary Sources</p><p>All findings in this piece are drawn directly from ATI Release A-2025-001410, a 2,460-page PDF and 81 Excel files released by Health Canada to The Old Guardian on July 15, 2026, under the federal Access to Information Act. The release covers Health Canada&#8217;s internal COVID-19 vaccine pharmacovigilance records from 2020 through 2023.</p><p>Specific documents cited in this piece:</p><p>ATI p.62</p><p>Internal SMSR review documenting Israel signal (Feb 15, 2021), Pfizer cumulative review (May 15, 2021), Health Canada internal conclusion of &#8216;possible link,&#8217; 70% within 7 days of second dose, three deaths in case series.</p><p>ATI p.62-63</p><p>Bell&#8217;s Palsy/facial paralysis signal -- 434 serious cases in one reporting interval, documented disagreement between Health Canada and Pfizer on signal closure and label language.</p><p>ATI p.97</p><p>Ad-hoc myocarditis review memo concluding &#8216;benefits outweigh risks&#8217; -- reached while three deaths were in the case series.</p><p>ATI p.198</p><p>Health Canada internal pharmacovigilance review, June 24, 2022 -- 657 confirmed myocarditis/pericarditis cases in Canada for Comirnaty across 58.1 million doses.</p><p>BBRS Signal Tracking (ATI Excel file)</p><p>Internal project tracking log (2020-2023) -- June 25, 2021 advisement letter to Pfizer on myocarditis/pericarditis; July 12-14, 2021 Bell&#8217;s Palsy memo and advisement letter entries documented.</p><p>Public record</p><p>Health Canada / PHAC communique to health practitioners, June 3, 2021 -- &#8216;no clear association has been established between myocarditis/pericarditis and mRNA vaccines.&#8217;</p><p>Comirnaty Product Monograph (authorized August 10, 2026)</p><p>Recent Major Label Changes section confirms cardiovascular warning updated October 2024 -- three and a half years after the internal &#8216;possible link&#8217; conclusion. Section 7 cardiovascular language confirms myocarditis occurred more commonly after second dose in adolescent and young adult males. Fatal events acknowledged. Long-term sequelae data lacking. Control Number: 300388.</p><p>The Old Guardian&#8217;s full series What They Knew examines Health Canada&#8217;s internal COVID-19 vaccine pharmacovigilance records across six parts, publishing in September 2026 in conjunction with the Allison Inquiry hearings at Parliament Hill.</p><p>If you or a family member experienced a serious adverse event following COVID-19 vaccination, contact The Old Guardian at tips@theoldguardian.ca. Source confidentiality is protected. Verification is required.</p><p>The Old Guardian  |  theoldguardian.ca  |  tips@theoldguardian.ca  |  ATI File: A-2025-001410</p><p>Editor&#8217;s Note -- September 2026 Update</p><p>Since publication of this piece, The Old Guardian obtained and reviewed the current authorized Comirnaty Product Monograph, dated August 10, 2026 (Control Number 300388). That document independently corroborates the central finding of this piece.</p><p>The Recent Major Label Changes table in the product monograph records that Section 7 -- Warnings and Precautions, Cardiovascular -- was updated in October 2024. That update added explicit language acknowledging myocarditis and pericarditis occurring &#8220;more commonly after the second dose or first booster dose in adolescent and young adult males&#8221; and that &#8220;fatal events have been very rarely reported.&#8221;</p><p>Health Canada&#8217;s internal ATI documents show the &#8220;possible link&#8221; conclusion was reached in May 2021. The product label was not updated to reflect that language until October 2024. The gap between internal knowledge and label disclosure is now documented across two independent primary sources: ATI Release A-2025-001410 and the official Comirnaty Product Monograph.</p><p>Source: Comirnaty Product Monograph, Authorization Date 2026-08-10, Control Number 300388. Recent Major Label Changes p.2. Section 7 Cardiovascular p.13. Health Canada.</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;3e5dabd4-a49d-4fb4-a35c-3d7c62080f51&quot;,&quot;caption&quot;:&quot;THE OLD GUARDIAN&quot;,&quot;cta&quot;:null,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;lg&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;WHAT THEY KNEW | PART 3 OF 6&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:315040924,&quot;name&quot;:&quot;Christopher Allen&quot;,&quot;bio&quot;:&quot;Welcome, Guardians. Success isn&#8217;t just money, it&#8217;s truth, community, and the journey. This space is for real talk, sharp thinking, and pushing back on the noise. I want your feedback. Speak up. Let&#8217;s build something that lasts.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/3461b478-c850-4d26-bc9c-672624b0cb55_1024x1024.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2026-09-14T09:45:44.999Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/a925c635-7671-4c5a-b1fd-3ac956130e93_1536x1024.png&quot;,&quot;cover_image_alt&quot;:null,&quot;canonical_url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-3-of-6&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:215302273,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:3999531,&quot;publication_name&quot;:&quot;The Old Guardian&#8217;s Substack&quot;,&quot;publication_logo_url&quot;:&quot;https://substackcdn.com/image/fetch/$s_!ChDO!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fba010f10-0b41-4234-90ec-1c87c7233e20_1280x1280.png&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-2-of-6/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/what-they-knew-part-2-of-6/comments"><span>Leave a comment</span></a></p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-2-of-6?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/what-they-knew-part-2-of-6?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/what-they-knew-part-2-of-6?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Guy Paul Morin - THE SUSPECT WAS ALWAYS SOMEONE ELSE]]></title><description><![CDATA[Guy Paul Morin]]></description><link>https://www.theoldguardian.ca/p/the-suspect-was-always-someone-else</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/the-suspect-was-always-someone-else</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Thu, 03 Sep 2026 09:45:10 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/ad4c121b-aa71-421d-a349-4417c0313978_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>THE OLD GUARDIAN</p><p>Investigative Journalism for the Public Interest</p><p>Guy Paul Morin lost a decade of his life to a murder he didn&#8217;t commit. The man who did was in the case file the whole time. Nobody was ever made to answer for either fact.</p><p>By Christopher Allen</p><p>The Old Guardian  &#8226;  September 2026</p><p>I. The Weird Guy</p><p>Christine Jessop got off the school bus near her home in Queensville, Ontario, on October 3, 1984. When her parents got home that evening, her school bag was on the counter. Christine wasn&#8217;t. She turned up three months later in a farmer&#8217;s field fifty-five kilometres away, sexually assaulted and stabbed to death.</p><p>Within months, police had a suspect: Guy Paul Morin, the twenty-four-year-old who lived next door. Not because of anything he&#8217;d done. Christine&#8217;s mother, Janet Jessop, had described him to investigators as a &#8220;weird-type guy&#8221; who played the clarinet and kept bees. An FBI profile suggested an intelligent white male, nineteen to twenty-six, living locally &#8212; vague enough to fit half the young men in Queensville. It was Janet Jessop&#8217;s discomfort with her neighbour, not any actual evidence, that turned a wide net into a name.</p><p>From there, everything ambiguous got read as guilt. Morin stared blankly through a police interview, and that became a telling reaction. He skipped Christine&#8217;s funeral, and that became &#8220;consciousness of guilt&#8221; &#8212; a category of evidence a later inquiry would call close to worthless, since staying away from a funeral is just as consistent with innocence as showing up. The Jessops&#8217; own memory of what time they got home that day shifted between their first statement to police and Morin&#8217;s second trial, conveniently opening a window in the timeline the original account had closed. Two jailhouse informants, angling for shorter sentences of their own, testified that Morin had confessed to them behind bars. Hair and fibre analysis went in front of the jury sounding like a match, without anyone mentioning that the technique could only rule sources out &#8212; never actually identify one.</p><p>Morin was arrested April 22, 1985. A jury acquitted him less than a year later, on February 7, 1986.</p><p>II. The Verdict Nobody Believed</p><p>Acquittal didn&#8217;t end it. Not in the town, not in the press, not with the Jessops &#8212; all three denounced the verdict. A conviction had already taken hold, built heavily on psychiatric evidence introduced at trial, that Morin was guilty no matter what twelve jurors decided. The Crown did something unusual: it appealed a not-guilty verdict all the way to the Supreme Court of Canada, arguing the trial judge had botched his instructions to the jury. The Crown won. A new trial was ordered.</p><p>That trial, in 1992, delivered the conviction the first one hadn&#8217;t &#8212; first-degree murder. Morin went to prison, then was released eighteen months later on bail while his appeal made its way through the courts.</p><p>What actually ended it was a technology that hadn&#8217;t existed in usable form when any of this started. On January 23, 1995, DNA testing excluded Morin as the source of genetic material recovered from Christine&#8217;s clothing. The Court of Appeal entered an acquittal. The Crown apologized. Ontario struck a public inquiry under retired judge Fred Kaufman and eventually paid Morin&#8217;s family $1.25 million.</p><p>Kaufman&#8217;s report ran 1,380 pages and made 119 recommendations. Its finding wasn&#8217;t that anyone had acted in bad faith. It was that police and prosecutors had developed, in his words, tunnel vision &#8220;in the most staggering proportions&#8221; &#8212; the condition where every new piece of ambiguous evidence gets folded in as proof of a theory instead of tested against it.</p><p>It is truly remarkable the extent to which the memories of a number of Crown witnesses improved as the proceedings progressed.  &#8212; Commissioner Fred Kaufman, Report of the Commission on Proceedings Involving Guy Paul Morin, 1998</p><p>The real killer, when Kaufman wrote those words, was still unknown &#8212; and had been sitting in the file since 1984.</p><p>&#8212;&#8212;&#8212;</p><p>III. The Notebook Nobody Read</p><p>When Christine disappeared, the missing-persons file belonged to York Regional Police. Once her body turned up outside York&#8217;s territory, the homicide investigation passed to Durham Regional, under Inspector Robert Brown. Brown split his detectives into two competing teams and let them race for the strongest suspect. One team &#8212; Bernie Fitzpatrick and John Shephard, known around the file as Fitz and Shep &#8212; inherited York&#8217;s boxes of accumulated leads. Inside one notebook: the name and address of a family friend named Calvin Hoover.</p><p>They didn&#8217;t follow it up. By Fitzpatrick&#8217;s own account years later, he and Shephard wrote off York&#8217;s work as amateurish and not worth their time, and chased other leads instead &#8212; a family friend prone to dark remarks, a local teenager who carried a knife, even Janet Jessop herself. None of it held. Hoover, a cable installer who&#8217;d worked alongside Christine&#8217;s father and whose family had grown close with the Jessops, was never seriously looked at. Never asked for a DNA sample. His alibi for October 3, 1984, was never tested.</p><p>He took his own life in 2015 &#8212; five years before anyone connected him to what happened to Christine.</p><p>It took genetic genealogy &#8212; a technique that didn&#8217;t exist for any investigator working this case in 1984, or 1992, or even 1998 &#8212; for Toronto&#8217;s cold case unit to match semen recovered from Christine&#8217;s underwear to Calvin Hoover, in October 2020. Police said he would have been charged had he still been alive. He wasn&#8217;t. No trial. No cross-examination of that untested alibi. Nobody left to charge.</p><p>Morin&#8217;s wrongful conviction and the decades nobody looked twice at Hoover aren&#8217;t two failures that happen to share a case file. They&#8217;re one failure, showing up twice. The same tunnel vision that turned an odd neighbour into a murder suspect on the strength of a mother&#8217;s discomfort is what let two homicide detectives write off a notebook with the real killer&#8217;s name in it as amateurish. Once Morin was the theory, nobody was actually weighing leads on their merits anymore. They were just confirming what they&#8217;d already decided.</p><p>&#8212;&#8212;&#8212;</p><p>IV. The Review That Was Promised and Never Delivered</p><p>Within days of Hoover&#8217;s identification, Innocence Canada &#8212; the organization that grew directly out of the volunteer committee that had fought for Morin&#8217;s exoneration &#8212; publicly called for an independent review of how both Durham Regional Police and Toronto Police Service missed him for three decades. Janet and Kenneth Jessop joined that call themselves, describing the case in their own words as a double miscarriage of justice: an innocent man convicted, and an innocent family left without answers for thirty-six years.</p><p>Innocence Canada wasn&#8217;t asking for another Kaufman-scale public inquiry. No hearings. Just a scoped, targeted review of two specific police failures &#8212; nothing more.</p><p>Ontario&#8217;s Ministry of the Attorney General, through a spokesperson, called a review premature while the investigation into Hoover was still active. Innocence Canada&#8217;s answer was simple: commit now to a review once that investigation wraps up.</p><p>There wasn&#8217;t much investigation left to wrap up. Hoover was dead. No prosecution was possible. Within weeks, Toronto Police said publicly they were mostly just tracing his history and checking for other unsolved cases he might be tied to &#8212; due diligence, not an open question about charges.</p><p>This is where the public record goes quiet. No announcement that a review happened. No statement explaining why one didn&#8217;t. Innocence Canada raised it again publicly at least once more, years later. Janet Jessop died in March 2024 &#8212; six years after Hoover&#8217;s name became public, with nothing on record to say the review her family asked for was ever convened.</p><p>That silence is a finding, not a verdict. An absence in the searchable public record doesn&#8217;t prove Ontario, Durham Regional Police, and Toronto Police never did the review, or never will &#8212; internal reviews don&#8217;t always come with a press release, and a 2020 commitment can just as easily fade through a change or two in leadership without anyone formally killing it. What can be said plainly is narrower, and still worth saying: as of this writing, there&#8217;s no public confirmation that the condition Ontario itself set &#8212; a review once Hoover&#8217;s case concluded &#8212; has ever been met. It&#8217;s been roughly six years since that condition was satisfied.</p><p>&#8212;&#8212;&#8212;</p><p>V. What the File Doesn&#8217;t Measure</p><p>Morin is in his mid-sixties now. For three decades he&#8217;s done something almost nobody in his position manages: he&#8217;s stayed quiet. He married, built a family, worked as a private contractor. During his eighteen months locked up, he refused protective custody and stayed in general population &#8212; a detail his sister points to as proof of who he actually is, not what he was accused of. When police showed up at his home in October 2020 to tell him Hoover had finally been identified, Morin confirmed only that they&#8217;d apologized. He didn&#8217;t say much else. One brief statement went out through his lawyer &#8212; relief for Christine&#8217;s mother, gratitude that investigators had stayed on it.</p><p>He&#8217;s said one more thing publicly, at hearings on wrongful convictions, that outweighs everything else in this file:</p><p>I was proven innocent, but people still think of me as a killer.  &#8212; Guy Paul Morin, cited by Innocence Canada</p><p>There&#8217;s no inquiry finding for what that costs. Kaufman&#8217;s report catalogued tunnel vision, jailhouse informants, and forensic overreach across 1,380 exhaustive pages, because those are the kind of institutional failures you can document &#8212; they have a start, an end, eventually a correction. What Morin&#8217;s describing isn&#8217;t that kind of failure. No hearing covers it. No compensation formula reaches it. And because the original suspicion was never actually built on evidence, there&#8217;s no clean way to rebut it either &#8212; you can quash a wrongful conviction, but you can&#8217;t DNA-test your way out of a town&#8217;s settled opinion of you, formed before any evidence existed and hardened over a decade of headlines and two trials. Ontario&#8217;s apology and $1.25 million fixed the legal record. Neither one was built to reach whatever Morin still runs into on an ordinary day, walking through his own town.</p><p>&#8212;&#8212;&#8212;</p><p>VI. The Reckoning</p><p>Two institutions failed the same family, in the same case, twenty years apart, the same way &#8212; treating a theory as settled fact and never testing it against the one sitting in their own paperwork. The first failure at least has a name attached to it: 1,380 pages, 119 recommendations. The second doesn&#8217;t have any of that. Just a promise from 2020 that nobody can currently confirm was kept.</p><p>There&#8217;s a harder truth worth sitting with alongside that, not instead of it. Hoover&#8217;s death shut the door on the only reckoning that could have actually functioned as justice &#8212; a trial, a cross-examination, a moment where he&#8217;d have had to answer for what he did in front of the people he did it to. But it also shut the door on what getting there would have cost the Jessops: years more of motions and appeals, Christine&#8217;s death picked apart again in open court, a living man free to deny or minimize it under cross-examination. Janet Jessop never got a verdict. She got a name, and she got it while she was still alive to hear it. That isn&#8217;t justice. It might, in its own limited way, have been an ending &#8212; the only kind she was ever going to get by the time one finally arrived.</p><p>Christine Jessop has been dead forty-two years. Her mother died with that name, if not the accounting Innocence Canada asked for on her behalf. Calvin Hoover was never made to answer for what he did. Guy Paul Morin is alive, and by every account still says as little about any of it as he can get away with.</p><p>The walls only work if everyone agrees they exist.</p><p>Sources and Methodology</p><p>Report of the Kaufman Commission on Proceedings Involving Guy Paul Morin, The Honourable Fred Kaufman, C.M., Q.C., April 9, 1998 (Government of Ontario).</p><p>Innocence Canada, case file and public statements on Guy Paul Morin, including statements attributed to Mr. Morin at Canadian parliamentary hearings on wrongful conviction reform.</p><p>&#8220;Inside the Hunt for Christine Jessop&#8217;s Real Killer,&#8221; Toronto Life, published in expanded form circa January 2022, including on-record comment from retired Det. Bernie Fitzpatrick.</p><p>Innocence Canada / Newswire press releases, October 26 and October 28, 2020, including statements from Innocence Canada co-president Kirk Makin and from Janet and Kenneth Jessop.</p><p>CHCH News and Law Times News reporting on Innocence Canada&#8217;s call for an independent review and the Ontario Ministry of the Attorney General&#8217;s response, October 2020 and April 2024.</p><p>CBC News reporting on the identification of Calvin Hoover, October 2020, including comment from Morin&#8217;s sister Denise Kowalski and from Hoover&#8217;s former wife, Heather Hoover.</p><p>The Canadian Encyclopedia, &#8220;Guy Paul Morin Case&#8221; and &#8220;Morin Freed by DNA,&#8221; Kirk Makin.</p><p>Wrongful Convictions in Canada (wrongfulconvictions.ca), case summary and inquiry findings on hair and fibre evidence, jailhouse informants, and consciousness-of-guilt testimony.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/the-suspect-was-always-someone-else/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/the-suspect-was-always-someone-else/comments"><span>Leave a comment</span></a></p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/the-suspect-was-always-someone-else?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/the-suspect-was-always-someone-else?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/the-suspect-was-always-someone-else?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[TDSB - Nobody’s Bargaining. That Might Be the Point.]]></title><description><![CDATA[The Old Guardian]]></description><link>https://www.theoldguardian.ca/p/nobodys-bargaining-that-might-be</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/nobodys-bargaining-that-might-be</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Wed, 02 Sep 2026 09:45:28 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/e7b7aafa-8e1d-40aa-94d9-5bb774ce543d_1672x941.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The Old Guardian</p><p>Ontario&#8217;s teachers are back in their buildings this week, prepping classrooms before students return. Their contracts expire tomorrow. How they got here matters more than the deadline itself.</p><p>Contracts for every major education union, ETFO, OSSTF, OECTA, AEFO, and CUPE&#8217;s OSBCU, expire August 31. Education contracts have run on this cycle for at least a decade, under governments of both major parties, since the agreements cover the full employment year rather than just the months students spend in class. Nobody picked this date to make a point.</p><p>The fight so far has nothing to do with wages, class sizes, or any of the issues that normally define a round of education bargaining. All five unions are stuck arguing over which issues get negotiated centrally, at the provincial table, and which stay local, board by board. That question has gone to the Ontario Labour Relations Board, and nobody involved can say when a ruling will come. Talks on everything else sit frozen in the meantime.</p><p>A Tool That Sat Unused</p><p>Under the School Boards Collective Bargaining Act, the Minister of Education can open central bargaining up to 180 days before contracts expire. All five unions asked the government, publicly and months in advance, to use that window. They named the exact risk that&#8217;s now playing out at the start of the school year.</p><p>Nothing came of the request. Bargaining only started after unions formally served notice in June, well inside the stretch that would have given both sides real time to settle before September.</p><p>Decades of precedent set the August 31 deadline. Declining a six-month head start the unions asked for directly was a decision made this year, by this government, and nobody else.</p><p>Public Money, Private Firm, Attack Ads</p><p>While talks sat stalled, The Trillium obtained a leaked draft script for government-produced advertisements targeting teacher unions, built around actors playing &#8220;concerned parents.&#8221; One line reads: &#8220;I read that Ontario teachers are already the highest paid in Canada.&#8221; Another responds: &#8220;I hope that teacher unions don&#8217;t walk out on students over salaries.&#8221;</p><p>ETFO president David Mastin called the ads &#8220;a deliberate distraction&#8221; and said the government is spending public money, through a public relations firm, to produce them. A reporter asked Calandra directly why he chose ads over the bargaining table. His answer: &#8220;I will use every means at my disposal to ensure that students, parents and teachers understand what my position is.&#8221;</p><p>Read that quote again. A government with a strong hand at the table rarely needs to hire a PR firm to win the argument outside it.</p><p>The Union Response Has Escalated Sharply</p><p>OSSTF has now called for the outright repeal of the School Boards Collective Bargaining Act itself, the 2014 law that governs the entire central and local bargaining structure. Union president Martha Hradowy said members are &#8220;waiting for a legal process to tell us which table is even permitted&#8221; to discuss workload and class sizes, the issues that actually affect students day to day.</p><p>Unions rarely ask to tear down the framework itself. When they do, it usually means they&#8217;ve stopped believing the problem is just who&#8217;s sitting across the table this round.</p><p>Rallies were held in dozens of Ontario municipalities on August 29. At one, in Toronto&#8217;s east end, MPP Peter Tabuns summed up the mood: &#8220;The failure of the government to do that, to me is a sign that they&#8217;re not serious about actually trying to find a resolution.&#8221;</p><p>This Has a Precedent, and It&#8217;s Worth Knowing</p><p>In 2012, Ontario&#8217;s government imposed contracts directly on teachers through Bill 115, freezing wages and restricting the right to strike. Courts later ruled the law violated collective bargaining rights protected under the Charter. A separate strike by CUPE education workers ended only once the government promised to repeal a law that had imposed contracts on its members, banned them from striking, and invoked the notwithstanding clause to override those Charter rights.</p><p>Real standoffs put both sides at equal risk if neither one moves. This one hasn&#8217;t worked that way in the recent past. When bargaining stalled or a strike hit, Ontario&#8217;s government had an option unions never had: legislate a settlement into being, Charter objections included.</p><p>Maybe this round breaks that pattern. Maybe it doesn&#8217;t. Either way, judging who wins a drawn-out fight only makes sense once you account for the side that&#8217;s historically had a way to end it without losing.</p><p>What This Actually Is</p><p>Strip away the framing on both sides. A government with the legal tools to shorten this standoff chose not to use them, then spent public money on ads aimed at the people it wasn&#8217;t reaching through those tools. Where this lands, a real settlement, a strike, an imposed contract, is still open. &#8220;Nobody&#8217;s negotiating&#8221; and &#8220;the process is broken by design&#8221; sound similar but claim different things. Right now the evidence backs the first one solidly. Whether it backs the second is the question worth watching this fall.</p><p>Sources: The Trillium, CBC News, CP24, CTV News, Global News, and public statements from ETFO, OSSTF, and the Ministry of Education.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/nobodys-bargaining-that-might-be/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/nobodys-bargaining-that-might-be/comments"><span>Leave a comment</span></a></p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/nobodys-bargaining-that-might-be?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/nobodys-bargaining-that-might-be?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/nobodys-bargaining-that-might-be?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Investigative Series: The Charlotte Transit Failure

Part II of IV]]></title><description><![CDATA[The System That Stood Down]]></description><link>https://www.theoldguardian.ca/p/investigative-series-the-charlotte</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/investigative-series-the-charlotte</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Fri, 28 Aug 2026 09:45:17 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/a3d1043f-5396-421a-89ac-98d081cfd002_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>THE OLD GUARDIAN</p><p>Independent Investigative Journalism</p><p>How a decade of decisions left Iryna Zarutska with no one standing between her and Decarlos Brown.</p><p>By Chris Allen  |  The Old Guardian  |  August 2026</p><p>Decarlos Brown Jr. was on the Lynx Blue Line for more than an hour before he killed Iryna Zarutska.</p><p>He had no ticket. He was exhibiting visible behavioral disturbance captured on surveillance cameras. At 8:18 PM, two Charlotte Area Transit System security personnel passed him on the train. There was no interaction. No ticket check. No intervention. No removal.</p><p>At 9:46 PM, Iryna sat down in the row in front of him. Four minutes later she was stabbed three times from behind.</p><p>What happened in those four minutes was a crime committed by one man. What happened in the years, months, and hours before them was a policy outcome. This piece is about the policy.</p><p>Section 1: The Cuts</p><p>In 2018, the Charlotte Area Transit System contracted with G4S Secure Solutions to provide security across its network. Under that contract, CATS had between 68 and 88 armed security personnel on duty.</p><p>By August 22, 2025, that number was 39.</p><p>The reduction -- confirmed at a minimum of 40% by the North Carolina Office of the State Auditor -- did not happen in a single decision. It happened across a sequence of contract changes, procurement choices, and institutional priorities that stretched across seven years. Each step, in isolation, had a rationale. Taken together, they left a system of 48 light rail cars with fewer armed guards than it had when the network was smaller.</p><p>The math is straightforward. Thirty-nine armed personnel cannot cover 48 train cars simultaneously. The auditor said so explicitly. CATS acknowledged it publicly. And yet, as of August 22, 2025, no policy had been enacted to address it.</p><p>The security contract timeline tells the story with unusual clarity. In July 2022, as the city was working toward a new contractor, CATS split its security request for proposals into two separate tracks: one for armed services, open to any qualified vendor, and one for unarmed services restricted exclusively to firms certified under the Charlotte Business Inclusion program -- a city initiative for minority, women, and small business enterprises.</p><p>Professional Security Services, a CBI-certified firm, won the unarmed contract in 2023. In June 2024, CATS canceled its armed security contract with Strategic Security Corporation for failing to meet requirements. Rather than issuing a competitive bid for a new armed security provider, CATS expanded Professional Security Services&#8217; contract to cover both armed and unarmed services -- sole-sourcing the expansion without seeking other vendors.</p><p>The contract value tells a parallel story. CATS&#8217;s security spending tripled from $5.9 million in 2022 to $18.4 million by 2025. More money. Fewer armed guards. The auditor did not characterize this as a coincidence.</p><p>While the CATS&#8217;s security contract value has increased from $5.9 million in 2022 to $18.4 million in 2025, the number of armed security has decreased by at least 40% over that time.</p><p>NC Office of the State Auditor, Preliminary Special Report on CATS Security, September 30, 2025.</p><p>CATS defended the shift publicly, arguing that total security personnel had more than doubled -- from 108 under G4S to 219 under PSS -- though the majority of the new positions were unarmed. The city characterized the change as a move toward a more mobile and responsive security model.</p><p>The Federal Transit Administration characterized it differently. In a letter to Mayor Vi Lyles dated September 10, 2025 -- eighteen days after Iryna Zarutska&#8217;s murder -- FTA Administrator called the tragedy preventable and documented that the rate of crimes against CATS riders had reached three times the national average, and that assault on transit workers had jumped to five times the national average.</p><p>Preventable. That word appears in a federal letter, signed by the administrator of the Federal Transit Administration, sent to the mayor of Charlotte. It was written before any lawsuit was filed, before any legislative hearing was convened, and before any reform was enacted. It is a primary document and it says the system failed.</p><p>Section 2: The Night of August 22</p><p>The following timeline is drawn exclusively from the CMPD Computer-Aided Dispatch report obtained by The Old Guardian through Public Records Request PRR-6565-2025, and the CMPD Incident Report filed under Complaint #20250822-2155-02. These are primary documents on file with this publication.</p><p>At 8:18 PM, PSS security personnel passed Decarlos Brown Jr. on the Blue Line. He had no ticket. Surveillance footage showed him exhibiting erratic behavior. No action was taken.</p><p>At 9:46 PM, Iryna Zarutska boarded at Scaleybark station and sat in the row directly in front of Brown.</p><p>At approximately 9:50 PM, Brown stabbed her three times from behind, including at least once in the neck. Fellow passengers fled the car and attempted to help her. Iryna was conscious or semi-conscious for under a minute before she collapsed.</p><p>What follows is the CAD record, entry by entry.</p><p>21:55:06 -- First call received. A female has been stabbed. Just occurred.</p><p>21:56:01 -- Dispatch confirms: female is on the ground in the train.</p><p>21:56:21 -- Dispatch confirms: female does not appear to be responsive.</p><p>21:59:05 -- Caller advises: male subject is on scene, standing on the opposite platform.</p><p>22:00:07 -- Officers arrive.</p><p>22:02:25 -- Platform shutdown ordered.</p><p>22:04:26 -- Crime scene requested.</p><p>22:15:57 -- Tourniquet applied.</p><p>22:23:40 -- Medic transport to CMC Main.</p><p>Four minutes elapsed between the first call confirming a woman was stabbed and officers arriving on scene. By 21:56:21 -- seventy-five seconds into the call -- dispatch knew she was on the ground and unresponsive. Officers did not arrive until 22:00:07.</p><p>Brown&#8217;s location was known before officers arrived. At 21:59:05, eight seconds before officers reached the scene, a caller confirmed the subject was standing on the opposite platform. The system had his location. There was no one there to act on it.</p><p>The platform was not shut down until 22:02:25 -- seven minutes and nineteen seconds after the first call. A crime scene was not requested until 22:04:26. A tourniquet was not applied until 22:15:57, twenty minutes and fifty-one seconds after the first call reporting a stabbing.</p><p>There was no armed security on the car when Brown attacked Iryna. There was no security response to his presence during the hour he rode the train before she boarded. The platform was open. The system had no mechanism to stop what happened.</p><p>Section 3: The Enforcement Collapse</p><p>The failure on August 22 did not begin with Brown boarding without a ticket. It began with a system that had effectively abandoned fare enforcement as operational policy before anyone died.</p><p>The North Carolina State Auditor&#8217;s second comprehensive report, released August 17, 2026, documents the scale of what had become institutional tolerance for non-payment across the CATS network.</p><p>60% of light rail riders did not pay to ride in the period examined.</p><p>45% of total bus and light rail ridership did not pay -- roughly half the system.</p><p>Fare evasion citations dropped from 4,763 in 2023 to 2,018 in 2025.</p><p>Total fare evasion fines collected on the light rail in all of fiscal year 2025: $550.</p><p>Estimated annual revenue loss from fare evasion: $5 million to $6.5 million.</p><p>The citation drop was not accidental. CATS informed the auditor&#8217;s office that bus drivers had been instructed not to enforce fares in order to protect themselves from altercations with passengers. The agency made a deliberate operational decision to stop enforcing its own rules, and told its auditor so.</p><p>Five hundred and fifty dollars. In a full fiscal year. On a light rail network that CATS estimates loses between five and six and a half million dollars annually to non-payment. That number is not a rounding error. It is a policy outcome.</p><p>Brown did not have a ticket the night he killed Iryna Zarutska. He had not paid when he boarded earlier in the evening either. The system he was riding had collected $550 in fare enforcement fines across the entire preceding year. There was no functional barrier between him and that train.</p><p>Section 4: The Money</p><p>While CATS was collecting $550 in fare enforcement fines across fiscal year 2025, it was spending $3.4 million on a Washington, D.C. public relations firm contracted to enhance public perception of the transit system.</p><p>The second state auditor&#8217;s report also found that CATS had $1.7 million in unspent safety and security funding sitting idle at the time of the audit. The agency that could not fill its authorized security positions, that instructed drivers not to enforce fares, that reduced armed guards by 40% while tripling its security contract value -- that agency had safety money it did not spend.</p><p>These are not allegations. They are findings from the Office of the North Carolina State Auditor, published in two separate reports -- September 30, 2025 and August 17, 2026 -- both conducted in response to Iryna Zarutska&#8217;s death.</p><p>The pattern is not complicated. CATS spent more on managing its image than it collected enforcing its rules. It had safety funds it did not deploy. It cut armed security while increasing contract value. It sole-sourced an armed security contract without competitive bidding. And on the night of August 22, it had 186 of 219 authorized security positions filled -- a gap of 33 unfilled roles -- while a man with a documented psychiatric history rode its trains for over an hour without a ticket.</p><p>After the murder, in the three weeks that followed, PSS filled zero of those 33 open positions.</p><p>Section 5: What the FTA Said</p><p>On September 10, 2025 -- eighteen days after Iryna Zarutska was murdered -- the Federal Transit Administration sent a formal letter to Mayor Vi Lyles. It was not a suggestion. It was a demand.</p><p>This tragedy was preventable, and it reflects systemic failures in leadership and accountability that cannot be ignored.</p><p>FTA Administrator, Letter to Mayor Vi Lyles, September 10, 2025. transit.dot.gov. [Primary document -- publicly available.]</p><p>The letter identified the rate of crimes against CATS riders as three times the national average. It identified transit worker assault as five times the national average. It told the mayor of Charlotte in writing, on federal letterhead, that her transit system had failed and that the failure was foreseeable.</p><p>The FTA subsequently launched a full audit of CATS, identifying 18 areas of non-compliance and establishing a federally supervised corrective action process. That process is ongoing.</p><p>CATS has since increased its security contract from $5.8 million to $23.1 million. It reports that Part 1 offenses fell 61% in the first quarter of 2026 compared with the same period in 2025, and 73% in the second quarter. Off-duty law enforcement has provided more than 46,000 hours of coverage. A fare inspection team is scheduled to launch in late 2026.</p><p>These are real changes. They are also changes that were not made until after Iryna Zarutska was dead.</p><p>The question this series has not yet answered is not whether the system failed.</p><p>The FTA answered that in writing on September 10, 2025. The state auditor answered it twice. The family&#8217;s attorney is about to argue it in civil court.</p><p>The question this series will answer in Part III is who made the decisions that produced this outcome, when those decisions were made, and what they knew at the time they made them. Institutional failure does not happen in the abstract. It happens in meetings, in budget approvals, in contract awards, and in memos that someone signed.</p><p>Editor&#8217;s Notes and Source Documentation</p><p>All factual claims in this piece are sourced to primary documents, state auditor reports, or federal agency communications. Documents marked [ON FILE - TOG] are held by The Old Guardian.</p><p>1. CMPD Computer-Aided Dispatch (CAD) Report -- Event Z0822215502. PRR-6565-2025. [ON FILE - TOG] Primary source for all timeline entries in Section 2. Timestamps cited verbatim from redacted CAD log.</p><p>2. CMPD Incident Report -- Complaint #20250822-2155-02. PRR-6565-2025. [ON FILE - TOG] Primary source for classification, victim confirmation, weapon, and case status.</p><p>3. NC Office of the State Auditor, Preliminary Special Report on CATS Security Contracts, September 30, 2025. auditor.nc.gov. Primary source for: 40% armed security reduction, 68-88 armed guards under G4S vs. 39 under PSS, contract value tripling ($5.9M to $18.4M), sole-source contract expansion, 186 of 219 positions filled at time of murder, zero positions filled in three weeks post-murder, CBI program influence on procurement.</p><p>4. NC Office of the State Auditor, Rapid Response Special Report on CATS, August 17, 2026. auditor.nc.gov. Primary source for: $550 in fare fines collected in SFY 2025, 60% light rail non-payment rate, 45% total system non-payment, citation drop from 4,763 to 2,018, instruction to drivers not to enforce fares, $1.7M in unspent safety funding, $3.4M PR contract.</p><p>5. Federal Transit Administration, Letter to Mayor Vi Lyles, September 10, 2025. transit.dot.gov. [Publicly available primary document.] Source for: &#8216;preventable&#8217; characterization, 3x national average passenger crime rate, 5x national average transit worker assault rate, demand for immediate corrective action.</p><p>6. U.S. Department of Justice / Western District of North Carolina, Federal Grand Jury Indictment, October 22, 2025. justice.gov. Source for federal charge, surveillance footage description, attack sequence.</p><p>7. WBTV / WCNC / Carolina Journal / Axios, September-October 2025: Corroborating coverage of state audit findings, PSS contract history, CATS response statements. Used for corroboration only; all institutional claims traced to auditor primary documents.</p><p>8. CATS Integrated Security and Public Safety Plan, September 24, 2025. charlottenc.gov. Source for CATS&#8217;s own account of security changes made post-murder.</p><p>9. CATS official communications, 2025-2026. charlottenc.gov. Source for CATS&#8217;s stated security improvements: 61%/73% crime reduction figures, 46,000 off-duty officer hours, contract increase to $23.1M.</p>]]></content:encoded></item><item><title><![CDATA[This wasn’t an accident. Doug Ford has spent eight years dismantling every institution that could hold him accountable.]]></title><description><![CDATA[Each move looked like a policy decision. Together, they&#8217;re something else entirely.]]></description><link>https://www.theoldguardian.ca/p/this-wasnt-an-accident-doug-ford</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/this-wasnt-an-accident-doug-ford</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Thu, 20 Aug 2026 09:46:29 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/ff3c4a2a-4d7a-46c7-8b8b-14338fcd4eee_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>The Old Guardian &#8212; Special Report | August 19, 2026</strong></p><p>In September 2018, on the last day of candidate registration for Toronto&#8217;s municipal election, Premier Doug Ford introduced legislation cutting Toronto City Council nearly in half &#8212; from 47 seats to 25 &#8212; mid-campaign, without warning, without public consultation.</p><p>It went to court. Ford invoked the notwithstanding clause to override the ruling. The cuts stood.</p><p>Most people filed it as a political fight about Toronto. A power grab, sure &#8212; but a local one. Move on.</p><p>That was 2018. It is now August 2026. And when you lay out everything that has happened since, the Toronto council cuts don&#8217;t look like a one-off anymore. They look like the opening move.</p><div><hr></div><h2>The full list. Read it slowly.</h2><p><strong>2018 &#8212; Municipal democracy</strong> Toronto City Council cut from 47 to 25 seats mid-election, without public input. Regional municipality chairs in Peel, York, Niagara, and Muskoka converted from elected to appointed &#8212; by the province. Democratic representation at the local level, reduced by provincial decree.</p><p><strong>2022&#8211;2023 &#8212; The Greenbelt</strong> 7,400 acres of protected Greenbelt land quietly removed from environmental protection &#8212; in ways the Auditor General found would increase connected developers&#8217; land values by $8.3 billion. The Auditor General also found government officials used code words in communications about the Greenbelt plan, violating legal record-keeping obligations. Ethics violations found. Two cabinet ministers resigned. Ford reversed under public pressure. The RCMP opened a criminal investigation in October 2023 that remains active. The mandatory decade review of the Greenbelt, required by law, is now more than a year overdue. Asked for an update at Queen&#8217;s Park in March 2026, the responsible minister said &#8220;No, thanks&#8221; and walked away.</p><p><strong>2022 &#8212; Strong mayor powers</strong> Ford granted strong mayor powers to Toronto and designated municipalities &#8212; allowing mayors to pass bylaws with one-third of council support and override local planning decisions. Local democratic councils weakened further by provincial legislation.</p><p><strong>2025 &#8212; Fixed election dates eliminated</strong> Ontario repealed its fixed election date legislation on November 27, 2025. Elections must now be held within the constitutional five-year maximum &#8212; but the Premier controls the timing. The mechanism introduced specifically to remove political considerations from election timing was removed by the politician who benefits most from controlling it.</p><p><strong>November 2025 &#8212; Public water</strong> The Water and Wastewater Public Corporations Act, buried in omnibus Bill 60, was rushed through the legislature without public consultation &#8212; debate held at night, committee comment bypassed. The legislation authorizes the Minister of Municipal Affairs and Housing to remove water and wastewater services from local governments and transfer them to arm&#8217;s-length corporations structured under the Business Corporations Act &#8212; the same legal framework as private, for-profit companies. The government insists private ownership is prohibited. A UBC law professor commissioned to review the legislation called it &#8220;stealth privatization,&#8221; noting the &#8220;agent&#8221; loophole could enable private investment through entities like the Canada Infrastructure Bank. The financial structure is the tell: infrastructure built over decades with public funds transfers to the new corporation. The municipal debt stays behind. Assets move. Liabilities don&#8217;t. Ontarians have seen this before. In 2000, the privatization of water testing in Walkerton killed seven people and left over 2,300 ill. Many survivors still live with permanent health consequences.</p><p><strong>2025&#8211;2026 &#8212; School boards: phase one</strong> Provincial supervisors appointed to take over eight Ontario school boards. Bill 33 expanded ministry power over boards directly. Follow-up legislation reduced the number of elected trustees, changed their responsibilities, and created a new CEO position appointed above the elected board. The most grassroots form of democratic representation in Ontario subordinated to a provincial appointee. Supervisors &#8212; with no educational background required &#8212; earn up to $350,000 a year. Surprise cuts made by supervisors that would normally have been debated in open school board meetings began happening without public notice.</p><p><strong>April 2026 &#8212; Freedom of information, retroactively eliminated</strong> Bill 97 passed April 23, 2026 &#8212; 57 to 33, no public hearings, buried in an omnibus budget bill. The Premier, all cabinet ministers, parliamentary assistants, and their staff are permanently exempt from FOI requests &#8212; retroactively to 1988. Dozens of active requests wiped out. Multiple court orders voided &#8212; including the order for Ford&#8217;s November 2022 phone records, the month his government announced the Greenbelt removals. Ontario&#8217;s Information and Privacy Commissioner urged the government not to pass it. She was ignored. Google Docs used for government business were simultaneously declared outside the law entirely. The doubling of FOI processing times for all other requests was buried in the same bill.</p><p><strong>May 19, 2026 &#8212; Three courts. One IPC order. Zero records.</strong> The Ontario Court of Appeal dismissed the government&#8217;s final appeal on Ford&#8217;s personal phone records &#8212; records a court had ordered produced, records the IPC had ordered released, records three levels of court had now upheld. Ford&#8217;s office said it was &#8220;reviewing next steps.&#8221; The records have not been produced. Bill 97&#8217;s retroactive shield is still in effect. The sequence: IPC orders records released. Ford refuses. Court sides with IPC. Ford appeals. Court dismisses. Ford appeals again. Court dismisses again. Ford passes Bill 97 retroactively shielding records. Court orders records again. Ford&#8217;s office says &#8220;reviewing next steps.&#8221; Three courts. One IPC order. One retroactive law. Zero records. That is not a legal strategy. That is a documented, sequential dismantling of judicial accountability in real time.</p><p><strong>2026 &#8212; Regional governments</strong> The Better Regional Governance Act 2026 gives the province power to appoint chairs and wardens in Peel Region, Durham, Waterloo, and York. More elected regional leadership positions converted to provincial appointments.</p><p><strong>May 14, 2026 &#8212; The TTC</strong> Bill 98 passed May 14, 2026. The Fare Alignment and Seamless Transit Act gives the Minister of Transportation total control over TTC fares, service levels, route designations, and revenue distribution by regulation &#8212; with no input required from Toronto residents or the elected TTC board. For the first time in over a century, TTC riders may be required to pay to transfer within the system. TTC fare revenue can now be redirected to subsidize transit systems elsewhere in the province. Distance and zone-based fares &#8212; which would fall hardest on riders in Scarborough, Etobicoke, North York, and Rexdale who take the longest trips because they cannot afford to live beside work &#8212; are now legally available to the minister by regulation, with no vote required. The TTC Board, the City of Toronto, transit unions, and rider advocacy groups all opposed the bill. It passed anyway.</p><p><strong>2026 &#8212; Billy Bishop and the Toronto Islands</strong> Legislation passed to expropriate the City of Toronto&#8217;s 20% stake in Billy Bishop Airport and override the tripartite agreement banning jet traffic. Ford declared the area a special economic zone where provincial and municipal laws can be suspended. The legislation&#8217;s property identification numbers cover not just the airport &#8212; but almost all city-owned land on the Toronto Islands, including beaches and parkland. The terminal is owned by Nieuport Aviation, controlled by J.P. Morgan Asset Management since 2019. Nieuport&#8217;s registered Ontario lobbyist is Mark Lawson of Anthem Advisory &#8212; a former PC government chief of staff who also lobbied for the Therme Ontario Place spa. No business case, no environmental assessment, and no capital cost estimate has been made public. The Toronto Port Authority estimates expansion costs at up to $5 billion. Ford said &#8220;one way or another, jets are coming.&#8221; The city has no legal recourse. The federal government launched a public consultation on June 8, 2026 &#8212; deadline July 24.</p><p><strong>August 2026 &#8212; School boards: phase two</strong> At the Association of Municipalities of Ontario conference on August 19, 2026, Education Minister Paul Calandra told hundreds of municipal politicians that elected school trustees are &#8220;outdated&#8221; and confirmed he is open to eliminating them entirely. &#8220;If the province determines they can deliver a better product without trustees, they will,&#8221; he said. Public school trustees have no constitutional protection &#8212; Calandra has confirmed this explicitly. Catholic and French trustees have limited protection. English public school trustees have none. Municipal elections are scheduled for October 2026. Ford has refused to say whether trustee elections will be on the ballot. Municipal clerks responsible for running those elections have formally written to Calandra asking whether to include trustees. He has not answered. Calandra has disabled public comments on his Facebook page. He cannot be FOI&#8217;d. His AMO delegation meeting notes are not public record.</p><div><hr></div><h2>The privatization receipt</h2><p>This pattern has been tested before at smaller scale &#8212; and the results are documented.</p><p>In 2011, the Rob Ford administration privatized garbage collection west of Yonge Street. Projected savings: $10 million annually. The savings were real &#8212; initially. Toronto&#8217;s own Auditor General eventually found that in-house collection east of Yonge is now roughly the same cost per household as the privatized west-end service. The promised savings evaporated over time as the private operator &#8212; GFL &#8212; became too embedded to replace without significant disruption, and competition disappeared.</p><p>In January 2026, GFL &#8212; the same company, now with the province-wide recycling contract &#8212; failed to collect post-holiday recycling across two entire Toronto districts within days of the new privatized system launching. Days. Not months.</p><p>This is the documented cycle: initial savings produced by wage suppression and underbidding, followed by embedded monopoly, eroding service, rising costs at renewal, and no viable path back to public delivery because the institutional capacity to do it has been dismantled. The evidence existed before the water legislation. Before Bill 98. Before the school board supervisors. The decision-makers had access to it. They proceeded anyway.</p><p>The savings argument is the packaging. Revenue access and embedded private operators are the product.</p><div><hr></div><h2>What this pattern actually means</h2><p>Each item on that list was reported as a separate story. A budget bill here. A transit policy there. A school board supervisor nobody noticed. Water corporations buried on page 47 of an omnibus bill debated at night.</p><p>Look at the full list and ask one question: what do all of these have in common?</p><p>Every single one transfers power away from an elected, accountable body &#8212; and toward the Premier&#8217;s office or a corporate structure insulated from public accountability. Every single one removes or weakens a mechanism that existed to check what the provincial government does with your money, your land, your transit, your children&#8217;s schools, your water, and your right to ask questions.</p><p>Municipal councillors. Regional chairs. School trustees. TTC boards. Conservation authorities. The Information and Privacy Commissioner. The courts. Fixed election dates. The Freedom of Information system that exposed the Greenbelt. And now the pipes that bring water to your tap, and potentially the last elected school trustees in Ontario&#8217;s English public system. All of it. Systematically. Over eight years.</p><div><hr></div><h2>This is not what conservatism means</h2><p>There is a version of conservatism with a coherent philosophical core. Reagan and Thatcher didn&#8217;t agree on everything, but they shared a foundational conviction: that concentrated state power is the enemy of individual freedom, that markets distribute decision-making better than governments do, and that the role of the executive is to govern within constraints &#8212; not to dismantle them.</p><p>Edmund Burke, the father of modern conservatism, built his entire political philosophy around one idea: that institutions, traditions, and distributed power structures protect ordinary people from the overreach of any single authority. Classical conservatism is, at its root, a doctrine of restraint. Restraint of government. Restraint of executive power. Restraint of the state&#8217;s reach into local communities.</p><p>A genuine fiscal conservative would be downloading power to municipalities, not uploading it to Queen&#8217;s Park. A genuine conservative would be strengthening accountability mechanisms, not retroactively legislating them away. A genuine conservative would not run Ontario&#8217;s debt from $337 billion to $485 billion, spend $112 million on taxpayer-funded government advertising, appoint provincial loyalists above every elected local body in the province, or buy a $28.9 million private jet and refuse to release the procurement documents.</p><p>What Ford practices is not conservatism. It is populist nationalism with clientelist economics. He uses conservative cultural signalling &#8212; the common man, cutting red tape, stopping the gravy train &#8212; while practicing the structural opposite. Power flows up, not down. Money flows to connected interests, not taxpayers. Accountability mechanisms are removed, not strengthened.</p><p>A genuine Thatcherite looking at Ford&#8217;s Ontario would see exactly what Thatcher spent her career fighting: an overreaching executive using state power to pick winners, eliminate institutional competition, and insulate itself from accountability.</p><div><hr></div><h2>You don&#8217;t have to rig an election to make one matter less</h2><p>Let&#8217;s be precise, because precision matters here. Ontario is not a one-party state. Elections still happen. Opposition parties still win seats. Doug Ford does not have 80% of the vote.</p><p>What he has is 43% of the vote &#8212; and 80 of 124 seats. That&#8217;s not a supermajority of Ontarians. That&#8217;s a supermajority of seats produced by a first-past-the-post system splitting the opposition vote between two parties that collectively outpoll him but can&#8217;t coordinate.</p><p>But here is what he has built around that electoral system. He controls when elections happen. He has shielded his government&#8217;s records so opponents can&#8217;t build a paper-trail case against him between elections. He has weakened every layer of local democratic accountability that might generate alternative power centres. He has moved to control Toronto&#8217;s transit system, restructure public water delivery, and seize an airport through a special economic zone that can suspend the law itself. He raised the personal donation cap to political parties. He has placed loyalists on the judicial appointments committee. And he governs a province where the opposition has been structurally divided for nearly a decade.</p><p>You don&#8217;t need to rig an election if you control when it&#8217;s called, what records your opponents can access, and which institutions are capable of challenging you in the years between votes.</p><p>Political scientists have a name for this. It&#8217;s called executive aggrandizement &#8212; a documented global phenomenon where democratically elected leaders use legal mechanisms to concentrate power in the executive while leaving the formal architecture of democracy superficially intact. Hungary under Orb&#225;n is the textbook case. Ontario is not Hungary. But the pattern of behaviour belongs to the same documented category. That is not an accusation. It is a classification.</p><p>Ford told the Star the Greenbelt is something people don&#8217;t give two hoots about. He may be right that most people aren&#8217;t following the details. That&#8217;s exactly how this works. The details are boring. The pattern is not.</p><div><hr></div><h2>Could a future government undo this?</h2><p>Some of it, yes. Fixed election dates, donation limits, strong mayor powers, regional chair appointments &#8212; all reversible by legislation. A new government could restore them in a single term with sufficient political will.</p><p>Some of it is harder. Water infrastructure transferred to new corporate structures before a reversal would require unwinding corporate transactions, not just repealing laws. TTC revenue redistributed under the new framework leaves gaps that need filling. School board governance restructured around provincial appointees takes time to restore through election cycles &#8212; assuming trustee elections happen at all in October 2026.</p><p>And some of it is effectively permanent. The FOI retroactivity is the most consequential. A new government could re-extend FIPPA coverage going forward. But the records that were never produced under existing court orders are gone. Ford&#8217;s November 2022 phone records &#8212; the ones three courts ordered him to produce, the ones Bill 97 retroactively shielded &#8212; are almost certainly lost as an evidentiary matter regardless of what any future legislature does. The Greenbelt-era communications conducted on personal devices and deleted or wiped are gone. The legal proceedings those records would have supported don&#8217;t automatically revive.</p><p>The most important permanent damage isn&#8217;t any single law. It&#8217;s the evidentiary record that was suppressed while those laws were being passed. A future government trying to hold Ford accountable would find the doors already locked and the keys already destroyed.</p><p>That&#8217;s not an accident either.</p><div><hr></div><h2>The one accountability mechanism left</h2><p>The Provincial Auditor General retains independent authority to access government records &#8212; including ministerial records &#8212; for audit purposes under the Auditor General Act. Bill 97 didn&#8217;t touch it. The Opposition has already filed an audit request on the jet procurement. That mandate needs to be protected in every future budget &#8212; and expanded to cover what is documented above.</p><p>The next election must be held by March 2030. Ford controls when it happens. He has eliminated fixed dates, shielded his records, placed loyalists above elected bodies at every level of government, and may eliminate the last directly elected education representatives in Ontario&#8217;s English public school system before October&#8217;s municipal vote. The template for what comes next is already written in the bills already passed. The only question is whether enough Ontarians are paying attention before the next window closes.</p><div><hr></div><h2>What you can do right now</h2><p>Contact your MPP &#8212; government and opposition alike. Demand the Auditor General&#8217;s mandate be protected in the next budget. Demand the Greenbelt review that is legally overdue be completed and made public. Demand an answer on whether trustee elections will be on the October ballot &#8212; before it&#8217;s too late to run. Ask your MPP where they stand on public water, on TTC accountability, and on restoring FOI coverage to ministerial offices.</p><p>Find your MPP at <strong>ola.org/en/members</strong></p><p>These institutions belong to you. They are being taken, one bill at a time, in language designed to make you look away. Don&#8217;t.</p><div><hr></div><p><em>The Old Guardian is an independent accountability journalism outlet covering Ontario provincial and municipal governance. We follow money, power, and the public record &#8212; not party lines. If this piece matters to you, share it.</em></p>]]></content:encoded></item><item><title><![CDATA[Queen’s Park Set the Table Part 1 of 2]]></title><description><![CDATA[What became law, what Scarborough walked into, and what the ward councillor said too late]]></description><link>https://www.theoldguardian.ca/p/queens-park-set-the-table-part-1</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/queens-park-set-the-table-part-1</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Wed, 19 Aug 2026 09:45:32 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/f6a8ff34-3dcc-4998-86c9-1c3e084b3162_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The Old Guardian | Housing &amp; Planning</p><p>Chris Allen | The Old Guardian | August 2026</p><p>On June 24 and 25, 2026, Toronto City Council adopted By-law 650-2026. It passed without amendment. It incorporated 201 low-rise residential properties across all six Scarborough wards into the city-wide zoning framework &#8212; extending parking minimum removal to each of them in the process.</p><p>The residents on those streets were not in the room. Most had no idea the vote was happening. The ward councillor for Scarborough Centre had written a letter asking for deferral two weeks earlier. It was logged, filed, and ignored.</p><p>Everything that led to that vote &#8212; the provincial legislation, the two-year planning process, the community motions, the unanswered questions &#8212; is what this piece is about.</p><p>What Bill 98 Actually Does</p><p>Bill 98 &#8212; the Building Homes and Improving Transportation Infrastructure Act, 2026 &#8212; received Royal Assent on June 2, 2026. It is nine schedules of amendments to Ontario&#8217;s Planning Act, City of Toronto Act, Building Code Act, Municipal Act, and Development Charges Act, passed as a single omnibus bill in under three months from introduction to law.</p><p>For Toronto, the direct legislative hits are documented in the bill itself:</p><p>&#8226;  Removal of &#8220;sustainable design&#8221; as a basis for site plan control &#8212; effectively ending the Toronto Green Standard as an enforceable planning tool.</p><p>&#8226;  Prohibition on the City requiring EV charging equipment in connection with parking facilities.</p><p>&#8226;  Municipalities can no longer address climate change or greenhouse gas reduction in their official plans.</p><p>&#8226;  The province will impose a standardized official plan template &#8212; replacing locally-developed plans built through years of public process with a prescribed 12-designation structure.</p><p>Toronto&#8217;s official plan was built through public process over decades. Bill 98 requires it to be replaced by a provincial template. The ERO consultation window closed May 14th. Royal Assent came June 2nd.</p><p>These are specific, enumerated legal changes &#8212; now in force &#8212; that reduce the scope of what Toronto&#8217;s planners are legally permitted to do, regardless of what city councillors vote for.</p><p>Environmental Defence described Bill 98 as stripping municipalities of the power to use site plan control to promote sustainable design. The Canadian Environmental Law Association noted it would fundamentally undermine Ontario&#8217;s ability to address the impacts of climate change. The Pembina Institute called it the latest attempt to curtail the authority of municipalities to set requirements for new developments that reflect the needs of the community.</p><p>None of these organizations are fringe. All three submitted formal public comments during the ERO consultation window. Their concerns did not change the outcome.</p><p>Toronto&#8217;s own planning staff confirmed the damage in their June 11 report to PHC on Bill 98&#8217;s implications. The scale and pace of the reforms, staff wrote, &#8220;have created a degree of uncertainty regarding how the various stages of planning review and approvals function as an integrated system in practice.&#8221; That is staff language for: we no longer know the full scope of what we can do. Several Toronto Green Standard requirements &#8212; including GHG emissions limits, building energy performance, green roofs, and EV charging infrastructure &#8212; were shifted from mandatory to voluntary as a direct result.</p><p>Scarborough Is the Test Case</p><p>Scarborough&#8217;s councillors saw the parking problem coming. On April 30th, Scarborough Community Council unanimously adopted motion SC31.19. City Council adopted it on May 20-21, 2026, passing 19 to 3. Ron Parkinson and SUN submitted a support letter on the record. Marina Tadenc and the CSVSWRA did the same.</p><p>The motion asked three things: review the feasibility of pausing the elimination of minimum parking requirements for new developments in Scarborough until transit infrastructure is in place; review a bylaw framework to prohibit new condo and multiplex developments from petitioning for on-street residential parking permits in Scarborough; and review options to restore and expand public parking at Scarborough TTC stations.</p><p>Scarborough councillors passed a motion asking city staff to study whether parking minimums could be paused. Then Queen&#8217;s Park passed a law that constrains what city staff can legally recommend. The study is now being written inside constraints that didn&#8217;t exist when the motion passed.</p><p>But PH31.3 &#8212; the Scarborough zoning item that moved through PHC on June 11 and City Council on June 24-25 &#8212; tells the longer story. The January 2024 preliminary staff report that launched this process stated explicitly that bringing these lands into the city-wide by-law would &#8220;ensure the consistent and equitable application of important city-building initiatives such as recent housing regulations for missing middle housing and the removal of parking minimums.&#8221; That language is in the summary. Page one. The parking minimum removal was a stated purpose from the beginning, not an incidental outcome of administrative housekeeping.</p><p>City staff reviewed approximately 379 properties in the Scarborough district. The final report recommended incorporating 201 of them into Zoning By-law 569-2013. The affected addresses span Asterfield Drive, Birchmount Road, Dale Avenue, Jeremiah Lane, Kingston Road, Pidgeon Street, Pin Lane, Scarborough Golf Club Road, Sheppard Avenue East, and more than a dozen other streets across all six Scarborough wards. Scarborough was the last of four city districts to go through this process &#8212; staged behind Toronto East York, North York, and Etobicoke York, with the parking minimum removal framework already locked in from the earlier phases before Scarborough residents had their turn.</p><p>What the Ward Councillor Said &#8212; and What Happened Next</p><p>On June 10, 2026 &#8212; the day before the PHC hearing &#8212; Councillor Michael Thompson submitted a letter to the Planning and Housing Committee requesting deferral of PH31.3.</p><p>The letter is worth reading in full. Thompson wrote that the proposal &#8220;moves too quickly without adequately considering the unique circumstances of Scarborough&#8217;s residential neighbourhoods, particularly those within Ward 21.&#8221; He raised transportation, noting that many low-rise communities in Scarborough &#8220;do not have the same level of transit service available in other parts of Toronto&#8221; and that residents &#8220;often depend on personal vehicles to access employment, education, healthcare, recreation, and shopping.&#8221; He raised infrastructure capacity, noting that &#8220;Ward 21 is already experiencing substantial development activity&#8221; and that residents deserve confidence that infrastructure planning is keeping pace. He raised neighbourhood character. And he raised the one-size-fits-all critique directly: &#8220;planning policies should be responsive to local context rather than applying a one-size-fits-all framework across communities with very different needs and challenges.&#8221;</p><p>Growth should be accompanied by infrastructure improvements, not implemented in anticipation of improvements that have yet to materialize. &#8212; Councillor Michael Thompson, June 10, 2026</p><p>Thompson asked PHC to defer approval and direct staff to undertake further review of transportation impacts, parking implications, infrastructure capacity, neighbourhood compatibility, and Ward 21-specific considerations.</p><p>PHC adopted PH31.3 without amendments on June 11. City Council adopted it without amendments on June 24-25. By-law 650-2026 is now in force. The deferral request was not granted. No additional review was directed.</p><p>The arguments in Thompson&#8217;s letter are substantively identical to the arguments in SC31.19 &#8212; the motion Thompson voted against at City Council in May. That vote is on the public record. So is this letter. Residents of Ward 21 are entitled to weigh both.</p><p>The Question Still Waiting for an Answer</p><p>The SC31.19 feasibility report &#8212; directed by a 19-3 City Council vote &#8212; has not been delivered. The Chief Planner was asked to review the feasibility of pausing parking minimum elimination in Scarborough and report back. That report is being written inside a Bill 98 legislative framework that did not exist when the motion passed.</p><p>Does Bill 98, as now enacted, prevent the City of Toronto from acting on the parking pause requested in SC31.19? And if so, which specific provisions prevent it?</p><p>That question has not been answered publicly. When the SC31.19 feasibility report arrives, it will either confirm that the pause is legally viable, confirm that Bill 98 has foreclosed it, or dodge the question entirely. Each of those outcomes tells Scarborough residents something important about where the real fight has to happen.</p><p>Residents who showed up to speak at PHC on June 11 &#8212; or who intended to &#8212; deserved to know whether the decision-making body in front of them had the legal authority to give them what they were asking for. That answer was not provided. By-law 650-2026 passed anyway.</p><p>What Comes Next</p><p>Part 2 of this piece will be published when the SC31.19 feasibility report lands. It will assess what staff say about the parking pause&#8217;s legal viability under Bill 98, what Scarborough&#8217;s councillors do with that answer, and what residents and community organizations can actually do next &#8212; including the provincial track.</p><p>The Etobicoke parking parallel is already on the record &#8212; Councillor Holyday moved a mirror motion for his district at consecutive council meetings. The suburban coalition is wider than Scarborough. That matters heading into October.</p><p>The honest answer to &#8220;what can we do?&#8221; may require looking past City Hall entirely. That&#8217;s not defeat. That&#8217;s map-reading.</p><p>The Old Guardian applies a structured evidentiary standard to all claims. The legislative provisions cited are drawn from Bill 98 (Chapter 8, Statutes of Ontario 2026). The PH31.3 record, SC31.19 adoption, By-law 650-2026, the June 3 PH31.12 staff report, and the Thompson letter (June 10, 2026) are all public documents on the Toronto City Clerk&#8217;s record. The tension between SC31.19&#8217;s parking pause request and Bill 98&#8217;s planning constraints remains at Evidence level pending the SC31.19 feasibility report. The contradiction between Thompson&#8217;s May vote against SC31.19 and his June letter opposing PH31.3 is documented at Evidence level pending any explanation on the public record. No claim in this piece has been advanced beyond its verified source.</p><p>Chris Allen is a Ward 21 Scarborough resident and investigative journalist. The Old Guardian covers civic accountability in Scarborough and at Queen&#8217;s Park.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/queens-park-set-the-table-part-1/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/queens-park-set-the-table-part-1/comments"><span>Leave a comment</span></a></p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/queens-park-set-the-table-part-1?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/queens-park-set-the-table-part-1?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/queens-park-set-the-table-part-1?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[The Machine - Peter Nygard]]></title><description><![CDATA[Part One of a TOG investigation into Peter Nyg&#229;rd]]></description><link>https://www.theoldguardian.ca/p/the-machine</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/the-machine</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Fri, 14 Aug 2026 09:45:48 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/6419442d-4df0-4cea-8e51-f2f6bedd742a_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>By Chris Allen | The Old Guardian</p><p>In November 1993, a twenty year old woman flew from Vancouver to Winnipeg. Peter Nyg&#229;rd had told her it was a modelling opportunity. Instead, she was held against her will at his Notre Dame Avenue warehouse and sexually assaulted.</p><p>She got out. She called a friend, who came and drove her away. She stayed there for about a week, working out what to do next.</p><p>Two Winnipeg police officers came to check on her, along with a social worker. Whatever she was carrying privately, what she told them out loud was careful. &#8220;I am safe. I am fine. I will be fine.&#8221;</p><p>When she got home to Vancouver, an RCMP officer followed up. He would later say he suspected there was more to it than what she was telling him. He took no formal statement.</p><p>Nothing happened. Somewhere in the years that followed, the file was cleared out. Twenty seven years passed.</p><p>In 2020, she came forward again, and Winnipeg police reopened the case. Investigators went looking for the 1993 file. It was gone. When they went back to the two officers who had been there in person, neither one had kept anything. Two different police forces, two different retention rules, and nobody left who could fully explain why either set of records no longer existed.</p><p>In October 2025, a Manitoba judge stayed the charges. Destroyed records, she found, do not meet the standard a fair trial requires. The case that came closest to holding Nyg&#229;rd accountable in the province where he built his empire ended not on the facts, but on paperwork that no longer existed.</p><p>The woman asked, afterward, that the publication ban protecting her identity be lifted. She wanted her name attached to what she had survived. Her name is April Telek.</p><p>That much of the story you have likely already heard, in pieces, across three years of headlines. What is harder to see, because it is scattered across five decades and three cities, is that 1993 was not the beginning.</p><p>The Pattern Before Her</p><p>In 1968, a young Winnipeg police detective named Des Depourcq took a report from a teenager who worked in Nyg&#229;rd&#8217;s factory. He arrested Nyg&#229;rd and laid a charge. The young woman later declined to testify, and the charge was withdrawn. Nyg&#229;rd was in his twenties. Depourcq had never told the story publicly until a CBC investigation found him decades later.</p><p>In 1980, it happened again. Another rape charge in Winnipeg. The outcome was the same: the woman would not testify, and the case died before it reached a courtroom.</p><p>By 1984, the pattern already had a paper trail, and at least one Winnipeg police officer knew it. An eighteen year old Nyg&#229;rd employee, being sexually harassed at work, went to an officer she knew to ask about pressing charges. He told her he had looked into Nyg&#229;rd&#8217;s file. It ran about ten inches thick, he said. &#8220;Nothing sticks to this man,&#8221; she remembers him telling her, and that she should get out while she could. She gave her notice. Before her last day, she says Nyg&#229;rd raped her at his apartment, and one of his employees handed her two weeks pay in an envelope and told her to collect her things and go. She never told police any of it. CBC is protecting her identity.</p><p>Sometime in the 1990s, a fourteen year old girl told her family Nyg&#229;rd had raped her. They turned to Joy Smith, then a schoolteacher working with trafficking victims and later a member of Parliament, for help deciding what to do. According to Smith, Nyg&#229;rd offered the family money to stay quiet and eventually paid them 250,000 dollars. The family never went to police. That case does not appear in any court file, because it was never allowed to become one.</p><p>That same year, 1993, a different fourteen year old girl named Nadine Moostoos was living on the street in Winnipeg when she says Nyg&#229;rd picked her up and assaulted her. Unlike the others, her case eventually reached the system, just decades late. In 2020, Winnipeg police reopened their investigation into Nyg&#229;rd and took her statement along with seven others, Telek&#8217;s among them. Police referred all eight cases to Manitoba prosecutors, who declined to charge in every one except Telek&#8217;s. &#8220;It&#8217;s like a slap in the face,&#8221; Moostoos said of how it ended. Her case and Telek&#8217;s ran through the exact same investigation, reviewed by the exact same prosecutors, referred to the exact same outside province, and came out the other side with two different results.</p><p>That is a lot of different women, hitting a lot of different points where the system could have stopped him, and watching it fail every time in a different way. A witness recanting. A witness recanting again. A family paid to stay silent before police ever got involved. An officer waving a woman away from her own complaint. A fully investigated case that still didn&#8217;t survive contact with prosecutors. Different mechanisms. Same result, for twenty-five years, before Telek ever got on a plane to Winnipeg.</p><p>A note on sourcing, because this series holds itself to the same standard it applies to everyone else: everything before 2020 in this section traces back to one investigative source, a Fifth Estate documentary broadcast in December 2021. That reporting checks out against everything obtained independently for this series so far. Moostoos&#8217;s case sits inside the same eight file review as Telek&#8217;s, a detail confirmed separately through the Manitoba court record. It has not yet been corroborated by a second outlet or a surviving police file, which for events this old may simply no longer exist to find.</p><p>None of that changes the argument. It just means you should hold the 1968, 1980, and 1990s accounts as strongly sourced but not yet doubly confirmed, while the 1993 through 2025 record, everything from Telek&#8217;s case forward, rests on primary court documents this series has in hand.</p><p>That is the argument the rest of this series is going to make in detail: that what protected Peter Nyg&#229;rd for half a century was not the absence of complaints. It was a system, corporate and institutional at once, reliable enough that complaints kept failing to become convictions.</p><p>Built For It</p><p>The pattern in the last section was a pattern across time. This one has an address.</p><p>At 1 Niagara Street in Toronto, the headquarters of his fashion company, Nyg&#229;rd kept a private suite on an upper floor. Employees had their own name for it: the Finland Suite. Two of the women who later testified against him said pornography was playing there. The building itself was never zoned for residential use. Whatever Nyg&#229;rd treated that room as, on paper it was something else entirely.</p><p>The same arrangement shows up again in Winnipeg, at the same address where Telek says she was held in 1993. A court examining the Nyg&#229;rd companies&#8217; finances years later looked for any record connecting him to 1340 Notre Dame Avenue as a residence and found nothing: no lease, no rent paid, no renewal terms, nothing in writing at all. The court&#8217;s own description was blunt. Whatever existed there was a temporary accommodation, not a tenancy. Two cities, two private rooms inside two commercial buildings, and in neither case does anything on paper say either room was ever meant to be lived in.</p><p>When prosecutors in Toronto later asked a court for permission to let one complainant&#8217;s account support another&#8217;s at trial, part of what persuaded the judge wasn&#8217;t just that the stories sounded alike. It was that getting into that private space followed the same design each time: a meeting, a tour of the building, then a room built so that who could get in, and who could get out, was never really up to the person who&#8217;d just walked through the door.</p><p>There was a second structure running alongside the physical one, and it was built out of money. A family was paid 250,000 dollars to keep a fourteen year old&#8217;s assault away from police entirely, according to Joy Smith. In 1968 and again in 1980, cases collapsed when the women involved chose not to testify. And years later, in his own police interview, Nyg&#229;rd confirmed a version of the same mechanism himself: he had paid 20,000 dollars to each woman who filed a human rights complaint against him in Manitoba. That&#8217;s not an allegation. It&#8217;s an admission, on the record, to the people investigating him.</p><p>None of this was the work of one man improvising. At its peak the company employed roughly 1,550 people across an operation that spanned continents. A room with no lease. A payment ready before anyone had to ask twice. Set those two structures beside the twenty five years of pattern from the last section, and &#8220;machine&#8221; stops sounding like a figure of speech. It starts sounding like a description of an actual design: get someone into the room, and two separate systems were already standing by to make sure whatever happened there never became anyone&#8217;s problem but hers.</p><p>Part Two of this series goes inside a different system: the police, the prosecutors, and the records that kept disappearing at the exact moments they mattered most.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/the-machine?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/the-machine?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/the-machine?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/the-machine/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/the-machine/comments"><span>Leave a comment</span></a></p><p></p>]]></content:encoded></item><item><title><![CDATA[“Trust Us, We Got It Right”]]></title><description><![CDATA[A COMPANION TO THE SHIELD | THE OLD GUARDIAN INVESTIGATION]]></description><link>https://www.theoldguardian.ca/p/trust-us-we-got-it-right</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/trust-us-we-got-it-right</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Wed, 12 Aug 2026 09:45:30 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/1b5771e5-3775-4909-aca0-8b56a20c81fb_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A federal court rejected that phrase as a basis for regulatory decision-making in Canada. Here is what Health Canada did next.</p><p>This piece is a companion to The Shield, The Reviewer, and Not Your Mother&#8217;s Roundup -- The Old Guardian&#8217;s ongoing investigation into glyphosate, Roundup, and the regulatory architecture surrounding both. All pieces are available at theoldguardian.ca. This piece stands on its own and focuses entirely on the Canadian regulatory record.</p><p>One Sentence</p><p>On August 8, 2025, Jason Flint, Director General and Chief Registrar of Health Canada&#8217;s Pest Management Regulatory Agency, sent an email. A federal court had ordered his agency to reassess its approval of a glyphosate-containing pesticide product called Mad Dog Plus, taking into account 61 new scientific studies identifying new or elevated risks. The court gave PMRA six months to deliver a scientifically justified response. The email was the response.</p><p>It contained one sentence.</p><p>&#8220;Overall, for the reasons articulated in Table 1, and taking into account global research findings from the additional studies referred to in Table 2, the existing reference values for glyphosate do not need to be revised, and the current risk assessment on file for the active ingredient glyphosate is valid.&#8221;</p><p>Two tables were attached. One addressed a single forest study. The other referenced the Global Glyphosate Study published by the Ramazzini Institute on June 10, 2025 -- a study that Safe Food Matters, one of the applicants who brought the original court case, believes demonstrates that glyphosate causes cancer. That study, published after Justice Zinn&#8217;s court order and before PMRA&#8217;s deadline, was handed to PMRA as new evidence requiring genuine consideration. It appears in Table 2. The current risk assessment remains valid.</p><p>This piece is about how Canada arrived at a moment where that sentence was considered an adequate response to a court order. It is a story that begins not in 2025, but in 2017. And it has been building, court case by court case, rejection by rejection, for eight years.</p><p>What the Court Actually Said</p><p>On February 18, 2025, Justice Russell Zinn of the Federal Court of Canada ruled in Friends of the Earth Canada et al. v. Attorney General of Canada et al., 2025 FC 300. The applicants -- Friends of the Earth Canada, the David Suzuki Foundation, Safe Food Matters, and Environmental Defence Canada -- had argued that PMRA was rubber-stamping renewals of glyphosate products without examining new science. Justice Zinn agreed, in part.</p><p>The ruling confirmed that product renewals, which occur every five years, are not mere formalities. They are, in Zinn&#8217;s words, &#8220;streamlined yet still substantive pulse checks that use newly available information to reassess the risk level of registered products up for renewal.&#8221; They are checkpoints. Not rubber stamps.</p><p>The problem was that PMRA could not demonstrate it had actually used those checkpoints. The court found no meaningful insight in the record into how Health Canada considered the 61 new scientific studies the applicants had submitted, if it gave them any consideration at all. The Minister of Health did not submit an affidavit. No explanation was provided for the absence of documented analysis. The agency&#8217;s position amounted to what Justice Zinn identified explicitly as a &#8220;trust us, we got it right&#8221; approach. The court rejected it.</p><p>The court sent the matter back to PMRA with a six-month deadline: by August 18, 2025, the agency had to redetermine the renewal of Mad Dog Plus in accordance with the court&#8217;s reasons. That meant genuine engagement with the new science. It meant showing its work.</p><p>Ten days before the deadline, Jason Flint sent his email. The current risk assessment is valid.</p><p>Canadian readers who followed the American glyphosate story through The Shield and The Reviewer will recognize the institutional posture immediately. In June 2022, the United States Ninth Circuit Court of Appeals found EPA&#8217;s glyphosate cancer methodology internally contradictory and legally unsupportable, and sent it back for a methodologically sound explanation. EPA&#8217;s withdrawal notice stated that its underlying scientific findings remained the same. Four years later, no corrected determination was finalized. The US Supreme Court used the unrevised conclusion as the foundation for a seven-to-two ruling closing the courthouse door on 100,000 plaintiffs. The posture is the same. The geography is different.</p><p>What PMRA&#8217;s Review Was Built On</p><p>To understand why the one-sentence response is insufficient, it helps to understand what PMRA&#8217;s 2017 re-evaluation -- the foundational document the current risk assessment rests on -- was actually built from.</p><p>The 2017 re-evaluation drew on six animal studies. Five were in PMRA&#8217;s own database. One was external. Three of the six were part of a review article published in the journal Regulatory Toxicology and Pharmacology in April 2000 by Gary Williams, Robert Kroes, and Ian Munro. That paper concluded glyphosate does not pose a health risk to humans at typical exposure levels. It quickly became a cornerstone reference for regulators worldwide, cited by the EPA, Health Canada, and the European Food Safety Authority across multiple assessments spanning two decades.</p><p>In late November 2025, the journal retracted it.</p><p>Co-editor-in-chief Martin van den Berg issued the retraction notice after an investigation into longstanding concerns about the paper&#8217;s authorship, data sources, and undisclosed conflicts of interest. The notice documented that Monsanto employees substantially ghostwrote the manuscript, that the paper was based almost exclusively on unpublished studies from Monsanto, that multiple other long-term chronic toxicity and carcinogenicity studies available at the time were ignored, and that the named authors may have received undisclosed financial compensation from Monsanto. Van den Berg stated the journal had lost confidence in the results and conclusions of the article.</p><p>Alexander Kaurov of Victoria University of Wellington and Naomi Oreskes, a historian of science at Harvard University, had documented the paper&#8217;s extraordinary influence in a September 2025 analysis published in Environmental Science and Policy. The Williams paper ranked in the top 0.1 percent of glyphosate-related studies by citation count, appeared in more than 700 academic papers, EPA filings, and AI training datasets, and was referenced uncritically across the vast majority of policy and governance documents that cited it. A ghostwritten paper funded by Monsanto shaped two decades of global regulatory science.</p><p>Health Canada&#8217;s response to the retraction was immediate and direct. The retraction of this review, the agency stated, does not affect our previous review conclusions because the department also independently evaluated the primary data sources used in the 2000 review paper.</p><p>That claim of independent evaluation sits alongside a finding from PMRA&#8217;s own 2015 proposed re-evaluation decision document. In reviewing the six animal studies, PMRA found equivocal, meaning uncertain, evidence of oncogenicity in the Atkinson mouse study. PMRA decided not to conduct a substantive cancer risk assessment. Uncertain evidence of cancer was found and set aside. Three of the remaining six studies were part of the now-retracted Williams review. That leaves two studies supporting the Canadian conclusion without a direct ghostwriting concern. Two studies and a dismissed cancer finding are the evidentiary foundation that Health Canada says does not need revision.</p><p>There is a further dimension to the independence question. In November 2022, Safe Food Matters obtained through an Access to Information request documentation showing that PMRA and the EPA worked together very closely on their glyphosate assessments under a joint Re-evaluation Work Plan. The two agencies coordinated their reviews. The EPA&#8217;s assessment was found arbitrary and unsupportable by a federal appeals court. PMRA&#8217;s assessment mirrored it. The ATI record confirms the coordination was structural, not coincidental.</p><p>And then there are the 229 blank pages. When civil society group Vigilance OGM filed an Access to Information request asking for the studies supporting PMRA&#8217;s claim that glyphosate residues pose no unacceptable risk, PMRA sent, after one year, 229 totally blank pages. The studies that underpin the Canadian regulatory conclusion are, by the agency&#8217;s own production, invisible.</p><p>The Counter-Narrative and Its Authors</p><p>The retraction of the Williams paper has not gone uncontested. A paper published in EXCLI Journal in 2026, organized by pharmacologist and consultant Christopher Borgert and signed by more than 60 co-authors, argues the retraction was editorial overreach and should be reversed. The paper contends the ghostwriting evidence is not definitive, that the alleged omissions stemmed from proprietary data access limitations disclosed in the original paper, and that subsequent reviews by independent expert panels reached similar conclusions. It is a substantive argument that deserves engagement.</p><p>The conflict of interest profile of those making that argument is equally part of the record and belongs here.</p><p>Christopher Borgert is a self-employed consultant whose clients since 2018 have included Monsanto, CropLife America, and the American Chemistry Council. He organized the response to the retraction and told Undark he paid the $6,400 open-access publication fee himself and is hoping Bayer or another entity will reimburse him. Among the co-authors: Robert Budinsky, retired from Dow Chemical. Christopher Bates, employed at H.B. Fuller. Gio B. Gori, a former tobacco industry consultant who served as editor-in-chief of Regulatory Toxicology and Pharmacology -- the journal that published the Williams paper -- during whose tenure 45 scientists wrote an open letter raising concerns about the journal receiving tobacco industry funding. Hans Marquardt, a member of Philip Morris&#8217;s external research programme in the early 2000s.</p><p>Reckoning Science, which analyzed the Borgert editorial in detail, found that it defends the ghostwritten Williams paper by citing additional papers that are themselves alleged to involve ghostwriting or undisclosed industry involvement. The editorial defending a compromised paper relies partly on other papers facing similar integrity questions.</p><p>The argument that the retraction was unjustified is a legitimate scientific position. The conflict of interest profile of those organizing that argument is a documented fact. Both are on the record. Readers can weigh them accordingly.</p><p>Eight Years of the Same Answer</p><p>The one-sentence August 2025 response did not emerge from nowhere. It is the latest entry in a documented pattern that stretches back eight years and has survived two federal court orders.</p><p>2019: Safe Food Matters sues PMRA over the 2017 re-registration of glyphosate, arguing the agency failed to properly consider objections. The Federal Court dismisses the case.</p><p>February 2022: The Federal Court of Appeal overturns that dismissal and orders PMRA to reconsider the objections, following the Court&#8217;s guidance on how to do so properly.</p><p>September 29, 2022: PMRA sends a 23-page response rejecting the objections again. Safe Food Matters says the agency ignored the Court&#8217;s guidance and produced new reasons and rehashed old ones rather than genuine reconsideration. Notably, PMRA&#8217;s response arrives just days after the US EPA withdrew its own glyphosate assessment -- the same assessment a US federal court had found arbitrary and unsupportable -- and PMRA and EPA had been working from a joint Re-evaluation Work Plan.</p><p>October 2022: Safe Food Matters sues PMRA again over the September rejection. January 2023: A second lawsuit is filed over the renewal of glyphosate products without consideration of new science.</p><p>February 18, 2025: Justice Zinn rules the Mad Dog Plus renewal unreasonable. The trust us, we got it right approach is explicitly named and rejected. Six months to show the work.</p><p>June 10, 2025: The Global Glyphosate Study from the Ramazzini Institute is published, finding that glyphosate causes cancer. PMRA receives it as new evidence.</p><p>August 8, 2025: Jason Flint emails one sentence. The current risk assessment is valid.</p><p>Late November 2025: The Williams paper is retracted.</p><p>December 2025: Health Canada says the retraction does not affect its previous review conclusions.</p><p>December 2025: Civil society groups formally request a special review of glyphosate including the Ramazzini study. As of mid-2026, PMRA has not responded.</p><p>There is also the matter of Bruce Lanphear. In July 2023, Lanphear resigned as co-president of Health Canada&#8217;s newly formed Science Advisory Committee on Pest Control Products. He resigned because the committee was unable to access product safety data and because he believed industry had too strong an influence over the regulatory process. This is not an outside critic making that assessment. This is the co-president of Health Canada&#8217;s own independent scientific advisory body, appointed to provide the independent check the system is supposed to contain, walking out because the system would not let him do his job.</p><p>The structural conditions are the same ones The Reviewer documented in the United States. Industry-submitted studies as the evidentiary foundation. Independent scientific review that is advisory and non-binding. No enforcement mechanism when timelines are missed. No consequence for institutional resistance to court orders beyond being sent back to produce another inadequate response. The system that produced the Williams paper as a cornerstone of regulatory science is the same system that produced the one-sentence response to a federal court order requiring genuine engagement with 61 new studies.</p><p>What Comes Next</p><p>The one-sentence response has not been accepted by the applicant coalition. Safe Food Matters&#8217; main glyphosate registration case -- challenging the 2017 re-registration itself rather than a single product renewal -- remains before the courts. That case asks for something the Mad Dog Plus case did not: the establishment of a review panel independent of PMRA to formally examine whether the 2017 registration decision should be struck down or amended. If that panel is ever convened, it will examine the same evidentiary foundation -- the same six animal studies, the same equivocal oncogenicity finding that was set aside, the same retracted Williams review -- that the one-sentence response declared valid.</p><p>The Ramazzini study published in June 2025 has been formally submitted to PMRA as new evidence requiring special review. As of mid-2026, PMRA has not responded to that submission. The Government of Canada has also been moving to eliminate re-evaluations altogether, removing the procedural mechanism through which public comments on registered pesticides are currently possible. If that change proceeds, the courtroom door that remained open in Canada -- the one that produced Justice Zinn&#8217;s ruling -- may narrow significantly.</p><p>The Old Guardian has identified three ATI targets for this investigation. First: the Jason Flint email tables in full -- Table 1 and Table 2 -- and any internal PMRA analysis conducted between the court order and the August 8 response. Second: PMRA&#8217;s diquat dibromide registration file, specifically whether the agency conducted an independent assessment or relied on EPA&#8217;s approval, given that diquat is banned in the European Union and is now the primary active ingredient in new Roundup formulations. Third: any correspondence between PMRA and EPA under the joint Re-evaluation Work Plan documented in the 2022 ATI release, specifically correspondence related to the timing of their respective glyphosate assessment conclusions.</p><p>The global thread that runs through this entire investigation closes here. The United States, Canada, and the European Union all relied on the same ghostwritten, Monsanto-funded study retracted 25 years after publication for serious ethical concerns. Three of the world&#8217;s largest regulatory jurisdictions built their safety determinations on the same compromised foundation. In the United States, a Supreme Court ruling has now made that foundation legally unreviewable by state courts. In Canada, a federal court found the foundation inadequate and ordered reassessment. The reassessment arrived in one sentence.</p><p>Trust us, we got it right.</p><p>A federal court already told Health Canada that was not good enough. The investigation into whether it ever becomes good enough continues.</p><p>Editor&#8217;s Notes</p><p>Companion series: This piece is a companion to The Shield (four parts), The Reviewer, and Not Your Mother&#8217;s Roundup. All pieces are available at theoldguardian.ca.</p><p>Primary sources: Friends of the Earth Canada et al. v. Attorney General of Canada et al., 2025 FC 300 (Justice Russell Zinn, February 18, 2025); Jason Flint email and attached Tables 1 and 2, August 8, 2025 (published by Safe Food Matters at safefoodmatters.org/filings); Williams, Kroes and Munro, &#8220;Safety Evaluation and Risk Assessment of the Herbicide Roundup and Its Active Ingredient, Glyphosate, for Humans,&#8221; Regulatory Toxicology and Pharmacology, April 2000 (retracted November/December 2025, retraction notice by co-editor-in-chief Martin van den Berg); Health Canada statement on retraction, December 2025 (as reported by The Canadian Press); PMRA Proposed Re-evaluation Decision PRVD2015-01 and Re-evaluation Decision RVD2017-01 (published PMRA documents); Safe Food Matters ATI disclosure on PMRA-EPA Re-evaluation Work Plan coordination, November 2022; Vigilance OGM ATI result, 229 blank pages (as reported in CMAJ and by Safe Food Matters); Bruce Lanphear resignation statement, July 2023 (as reported in CMAJ); Kaurov and Oreskes, &#8220;The afterlife of a ghost-written paper: How corporate authorship shaped two decades of glyphosate safety discourse,&#8221; Environmental Science and Policy, September 2025; Borgert et al., EXCLI Journal, 2026; Environmental Health News, Borgert conflict of interest documentation; Retraction Watch, December 2025 (retraction notice and van den Berg statement); C&amp;EN, December 2025 (retraction reporting); Safe Food Matters, &#8220;Mad Dog Case on Glyphosate: PMRA Refuses Action on New Science,&#8221; August 18, 2025; Natural Resources Defense Council v. U.S. Environmental Protection Agency, 38 F.4th 34 (9th Cir. 2022) (referenced for American parallel).</p><p>Confidence tier: All findings attributed to Justice Zinn&#8217;s ruling are drawn from the published decision at 2025 FC 300. The Jason Flint one-sentence response is quoted verbatim from the Safe Food Matters published email. Health Canada&#8217;s statement on the retraction is quoted as reported by The Canadian Press and confirmed consistent across multiple outlets. The PMRA-EPA coordination finding is drawn from the Safe Food Matters ATI disclosure, not from inference. The Borgert conflict of interest profile is drawn from Environmental Health News and confirmed by Borgert&#8217;s own statements to Undark regarding the publication fee. The counter-narrative paper is addressed with its full conflict of interest context stated. No claim in this piece asserts definitively that glyphosate causes cancer. The piece reports what primary documents show about PMRA&#8217;s methodology, the court&#8217;s findings, the retracted study, the coordination record, and the institutional pattern across eight years.</p><p>ATI targets identified: Jason Flint email tables in full and any internal PMRA analysis August 2025; PMRA diquat dibromide registration file; PMRA-EPA Re-evaluation Work Plan correspondence. The Old Guardian will file these requests and report on what is returned.</p><p>The Old Guardian | theoldguardian.ca</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/trust-us-we-got-it-right?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/trust-us-we-got-it-right?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/trust-us-we-got-it-right?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/trust-us-we-got-it-right/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/trust-us-we-got-it-right/comments"><span>Leave a comment</span></a></p><p></p>]]></content:encoded></item><item><title><![CDATA[Not Your Mother’s Roundup]]></title><description><![CDATA[A COMPANION TO THE SHIELD | THE OLD GUARDIAN INVESTIGATION]]></description><link>https://www.theoldguardian.ca/p/not-your-mothers-roundup</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/not-your-mothers-roundup</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Mon, 10 Aug 2026 09:45:28 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/4ff74892-12a6-4156-9668-75f2551880c1_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Bayer removed glyphosate from residential Roundup to manage litigation risk. What replaced it is, on average, 45 times more toxic. The label doesn&#8217;t say that either.</p><p>This piece is a companion to The Shield, a four-part Old Guardian investigation into the legal, regulatory, and corporate architecture surrounding Roundup litigation, and to The Reviewer, which examines the EPA&#8217;s glyphosate cancer determination and what a federal court found when it looked closely at the methodology. Both are available at theoldguardian.ca. This piece stands on its own.</p><p>The Exit</p><p>On July 29, 2021, Bayer CEO Werner Baumann told investors why the company was removing glyphosate from its residential Roundup line. He did not reach for corporate euphemism. He was direct.</p><p>&#8220;More than 90% of the Roundup litigation claims Bayer has faced in recent years have come from the U.S. residential lawn and garden market business segment and is what led to the company deciding to abandon it. Let me be very clear that this decision is exclusively geared at managing litigation risk and not because of any safety concerns.&#8221;</p><p>Parse that statement carefully. More than 90 percent of tens of thousands of cancer claims came from residential users. Not the farmer with documented occupational exposure records. Not the licensed commercial applicator. The homeowner. The person who bought a bottle at a hardware store and sprayed their driveway or garden path on a spring weekend without a second thought. That person generated nine out of ten of Bayer&#8217;s cancer lawsuit claims.</p><p>Baumann&#8217;s stated reason for exiting that market was not that Roundup had been found unsafe for residential use. It was that continuing to sell it to residential users was generating too much litigation. The product, in Bayer&#8217;s own framing, was fine. The lawsuits were the problem.</p><p>The residential user was not informed of any of this. No letter. No recall. No shelf notice. No label change explaining why the product was being reformulated. The bottle that had sat on hardware store shelves for decades simply began appearing in a new version, distinguished from the old one by a small red bar reading &#8220;Exclusive Formula.&#8221;</p><p>What was inside the new bottle is the story this piece tells.</p><p>What Replaced It</p><p>In October 2024, Friends of the Earth reviewed Roundup products for sale at Home Depot and Lowe&#8217;s, the two largest home and garden retailers in the United States. The analysis found seven Roundup products still containing glyphosate on shelves alongside eight new reformulated products. The new products contained combinations of four replacement chemicals: diquat dibromide, fluazifop-P-butyl, triclopyr, and imazapic.</p><p>All four chemicals pose greater risk of long-term and reproductive health problems than glyphosate, based on the EPA&#8217;s own evaluation of safety studies -- not on Friends of the Earth&#8217;s independent assessment. The underlying data is the agency&#8217;s. The analysis is FOE&#8217;s. That distinction matters for sourcing purposes and is stated explicitly here.</p><p>The replacement chemicals have been linked to kidney and liver damage, reproductive and developmental abnormalities, birth defects, and allergic reactions affecting the eyes, skin, and respiratory system. Two of the four -- diquat dibromide and imazapic -- are banned in the European Union.</p><p>The worst of the four is diquat dibromide.</p><p>Diquat dibromide is present in every single new Roundup formulation. It is classified as a highly hazardous pesticide. It is 200 times more chronically toxic than glyphosate. The European Union banned it under Commission Implementing Regulation EU 2018/1532, effective June 30, 2019, following findings by the European Food Safety Authority of high risk to workers, bystanders, and residents. The UK, China, and several other countries followed with their own bans or severe restrictions.</p><p>The United States did not ban it. The EPA continues to approve it for residential consumer use. It is now the primary active ingredient in the product sold to the consumer who was, in Bayer&#8217;s own calculation, the source of nine out of ten cancer litigation claims under the previous formulation.</p><p>On average, the new Roundup formulations are 45.6 times more chronically toxic to human health than the glyphosate-based products they replaced, and 3.9 times more acutely toxic. Those figures come from the FOE analysis drawing on EPA safety study evaluations. Bayer disputed the analysis, calling it deeply flawed. The company did not identify which specific toxicity comparisons it contested, nor did it dispute that the underlying data source is the EPA&#8217;s own safety study evaluations.</p><p>The packaging is nearly identical to the old Roundup. The same green bottle. The same brand name. The same shelf position at the same retailers. A small red bar reading &#8220;Exclusive Formula&#8221; is the only visual signal that the product has changed. There is no requirement under FIFRA or any other federal law that Bayer inform consumers their product has been reformulated with chemicals the EPA rates as significantly more dangerous than what they previously bought. No label change was required. No consumer notification was mandated. The EPA approved the new labels. The new labels do not mention any of this.</p><p>The Shelf Problem</p><p>As of October 2024 -- the last verified shelf review -- seven glyphosate-containing Roundup products remained for sale at Home Depot and Lowe&#8217;s. Old stock is legally sellable until it&#8217;s gone. Bayer stopped producing glyphosate residential Roundup in 2023, but existing inventory has no mandated sell-by date and no pull date requirement. A consumer buying a Roundup product today may be buying old glyphosate stock, new diquat dibromide stock, or a product containing both -- and there is no reliable way to know which without reading the active ingredient list in fine print on the back label.</p><p>The garage shed compounds this problem significantly. Concentrated Roundup loses herbicidal effectiveness over time -- typically seven to eight years under optimal storage conditions, significantly less in the temperature fluctuations and partial seals of a typical residential shed. But herbicidal degradation and carcinogenic potential are two entirely separate biological mechanisms.</p><p>The surfactants and adjuvants that make glyphosate kill weeds quickly break down with age and poor storage conditions. The glyphosate molecule itself is chemically stable, non-volatile, and does not degrade in the presence of light or air. A bottle that has lost 40 percent of its weed-killing speed has not lost 40 percent of its glyphosate concentration. The consumer who compensates for reduced visible efficacy by using more product is not reducing their exposure to the compound of concern. They may be increasing it.</p><p>No label communicates this distinction. The &#8220;safe when used as directed&#8221; instruction assumes a fresh, properly formulated product applied under controlled conditions by a person following label directions precisely. It does not describe a three-year-old backyard shed bottle used by someone in shorts and sandals who applies extra product because the weeds aren&#8217;t dying fast enough.</p><p>And now the same problem applies to the replacement chemicals. The new diquat dibromide formulations are on shelves today. In three years they will be in sheds. In five years they will be the old stock that consumers compensate for with higher application volumes. The label will still not explain the difference between a product losing weed-killing speed and a product maintaining its full chronic toxicity profile. Because no label is required to say that. Because the EPA approved these labels. Because that approval, as The Reviewer documented, functions as the legal ceiling on what anyone can claim about what the label should have said.</p><p>What Was Always Available</p><p>The residential weed control problem that Roundup was marketed to solve has never required a synthetic chemical herbicide. The alternatives have always existed. They have simply not had a $500 million annual marketing budget.</p><p>Boiling water poured directly onto weeds in driveway cracks and patio joints kills on contact through cell membrane disruption, penetrates to the root system on shallow-rooted weeds, leaves zero chemical residue, and has been documented effective since before Roundup existed. No PPE required. No label. No exposure window. No degradation question. No litigation history. Cost: the energy to boil a kettle.</p><p>Horticultural vinegar at 20 percent acetic acid concentration -- significantly stronger than household vinegar -- kills broadleaf weeds on contact through the same mechanism. Available at garden centres. Not systemic, so deep-rooted perennial weeds may regrow from established root systems, but for the driveway crack and patio joint application that was Roundup&#8217;s primary residential use case it is functionally equivalent. The legitimate safety concern is eye and skin irritation from the acidity. That concern is addressed by gloves and eyewear -- the same PPE the Roundup label recommends and that almost nobody actually wears.</p><p>Iron-based herbicides -- like the Scotts product using FeHEDTA as its active ingredient -- are selective, meaning they target broadleaf weeds without harming grass, and are derived from a naturally occurring soil mineral. The isothiazolinone preservatives they contain warrant the same scrutiny as any chemical product. But the active ingredient mechanism is fundamentally different from systemic herbicides, and the regulatory history is substantially cleaner.</p><p>Corn gluten meal applied in early spring prevents weed seeds from germinating without any post-emergent chemical exposure. Zero toxicity concern for humans or pets. Applied once per season before germination, it dramatically reduces weed establishment in treated areas.</p><p>Flame weeding with a propane torch applied briefly to weed foliage causes cell rupture through rapid heating and is standard practice in certified organic agriculture. Effective for driveways, patios, and gravel paths. Zero chemical exposure. The legitimate concern -- fire risk in dry conditions -- is addressable in two label sentences.</p><p>None of these alternatives generate the recurring revenue that a branded chemical product sold at scale through national retail chains produces. Boiling water is free. Horticultural vinegar is a one-time low-margin purchase. Corn gluten meal is seasonal and inexpensive. A hori hori weeding knife lasts twenty years. Roundup, in either its original or reformulated version, generates reliable reorder revenue every season from a consumer base that has been trained by decades of marketing to reach for the bottle rather than the kettle.</p><p>The residential weed killer market was never built around what worked best for the homeowner. It was built around what generated the most reliable recurring revenue for the manufacturer. The reformulation to diquat dibromide did not change that logic. It updated it. Same shelf. Same brand. Same revenue model. Different chemical. And a fresh thirty-year clock on the litigation history.</p><p>Who Is Reviewing Diquat Dibromide</p><p>The question that ends this piece is the same question that runs through the entire investigation.</p><p>Glyphosate&#8217;s cancer litigation record spans thirty years. It generated more than 100,000 lawsuits, billions in settlements, and a Supreme Court ruling. The science linking it to non-Hodgkin&#8217;s lymphoma has been accumulating since the 1990s and was formally assessed by IARC in 2015. The EPA&#8217;s own Cancer Paper found effect estimates ranging from 1.3 to 1.5 increased NHL risk across the meta-analyses it reviewed. A federal appeals court found EPA&#8217;s methodology for dismissing that signal internally contradictory and legally unsupportable.</p><p>Diquat dibromide has been in consumer Roundup products since 2023. Its residential use history in the United States is three years old. There is no thirty-year litigation record. There is no IARC review. There is no epidemiological cohort study following residential users of diquat dibromide formulations for non-Hodgkin&#8217;s lymphoma or Parkinson&#8217;s disease or any other long-latency disease outcome. The science that would surface a problem, if a problem exists, has not had time to accumulate.</p><p>What exists right now is an EPA registration approval for diquat dibromide in consumer products. That approval was issued through the same registration review process The Reviewer documented in detail -- industry-submitted studies, a non-binding Scientific Advisory Panel, no enforcement timeline, no consequence for delay. The same process that produced the glyphosate cancer determination a federal court found defective is the process that produced the diquat dibromide approval the consumer is now buying at Home Depot.</p><p>The European Union found diquat dibromide posed high risk to workers, bystanders, and residents and banned it in 2019. The EU banned it seven years ago. It is now the primary active ingredient in every new residential Roundup formulation sold in the United States, in a product marketed to the population Bayer&#8217;s CEO identified as the source of nine out of ten cancer lawsuit claims under the previous formulation.</p><p>There is no requirement from the EPA that labels alert consumers to new chemicals or warn of increased risks when a product is reformulated. Drug companies cannot replace the aspirin in a brand-name pain reliever with a different compound and sell it in the same packaging without disclosure. Pesticide manufacturers can. And did.</p><p>Bayer did not solve the residential user&#8217;s problem. It solved Bayer&#8217;s problem. The residential user&#8217;s exposure continues, now with a chemical the EU banned seven years ago, through the same inadequate label framework, under the same regulatory approval process, with the same absence of consumer notification, and with the courthouse door now closed by a Supreme Court ruling that used that regulatory process&#8217;s output as its legal foundation.</p><p>The next question is whether Canada&#8217;s Pest Management Regulatory Agency reviewed diquat dibromide independently or mirrored EPA&#8217;s approval through the same procedural alignment that has historically governed its glyphosate conclusions. The Old Guardian intends to find out.</p><p>Editor&#8217;s Notes</p><p>Companion series: This piece is a companion to The Shield (four parts) and The Reviewer. All five pieces are available at theoldguardian.ca.</p><p>Primary sources: Bayer CEO Werner Baumann, investor call statement, July 29, 2021 (as reported by C&amp;EN, AgWeb, and Modern Farmer, and consistent with Bayer&#8217;s published Five-Point Plan documentation); Friends of the Earth, &#8220;New Roundup, New Risks,&#8221; October 2024, drawing on EPA safety study evaluations for all toxicity comparisons (foe.org/resources/new-roundup-new-risks); Commission Implementing Regulation (EU) 2018/1532 of 12 October 2018, concerning the non-renewal of approval of diquat (EUR-Lex, effective 30 June 2019); European Food Safety Authority, Statement on non-dietary exposure on diquat, EFSA Journal 2018;16(4):5260; Friends of the Earth shelf review, Home Depot and Lowe&#8217;s, June through October 2024 (seven glyphosate products confirmed, eight reformulated products identified); Kendra Klein, Deputy Director of Science, Friends of the Earth, public statement October 2024.</p><p>Confidence tier: The Baumann quote is drawn from contemporaneous reporting across multiple outlets and consistent with Bayer&#8217;s own published documentation. The 45 times more toxic figure and the 200 times diquat dibromide figure are drawn from the Friends of the Earth analysis, which explicitly bases its toxicity comparisons on EPA&#8217;s own safety study evaluations, not on FOE&#8217;s independent scientific assessment -- this distinction is stated in the piece. The EU ban is confirmed through the primary EU regulation at EUR-Lex. The shelf review data reflects October 2024 findings; current shelf status may differ. The herbicidal degradation versus carcinogenic potential distinction reflects established chemical stability data for glyphosate and is not an assertion about human health outcomes. Bayer disputed the FOE analysis as deeply flawed but did not specify which toxicity comparisons it contested -- that response is noted in the piece. No claim in this piece asserts definitively that diquat dibromide causes cancer or that the new Roundup formulations will generate the same health outcomes as the old ones. The piece reports what is documented about the regulatory approval, the toxicity comparisons, the EU ban, and the absence of consumer notification requirements.</p><p>Ongoing monitoring: The Old Guardian will continue to monitor EPA&#8217;s diquat dibromide registration review, PMRA&#8217;s parallel approval status, and any emerging epidemiological research on residential diquat dibromide exposure outcomes.</p><p>The Old Guardian | theoldguardian.ca</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/not-your-mothers-roundup?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/not-your-mothers-roundup?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/not-your-mothers-roundup?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/not-your-mothers-roundup/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/not-your-mothers-roundup/comments"><span>Leave a comment</span></a></p><p></p>]]></content:encoded></item><item><title><![CDATA[The Reviewer]]></title><description><![CDATA[When the courthouse door closes, the regulator becomes the only institution left standing between the public and the product. So who reviewed the reviewer?]]></description><link>https://www.theoldguardian.ca/p/the-reviewer</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/the-reviewer</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Thu, 06 Aug 2026 09:45:31 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/9dca04da-8e67-4259-bc96-68b7250c9567_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A COMPANION TO THE SHIELD | THE OLD GUARDIAN INVESTIGATION</p><p>The Shield documented what EPA&#8217;s glyphosate determination did to 100,000 plaintiffs. This piece examines how that determination was made, why a federal court found it defective, and what happened when nobody fixed it.</p><p>This piece is a companion to The Shield, a four-part Old Guardian series examining the legal, regulatory, and corporate architecture surrounding Roundup litigation. The Shield is available in full at theoldguardian.ca. Familiarity with the series is useful but not required. This piece stands on its own.</p><p>Fourteen Words</p><p>On June 25, 2026, the United States Supreme Court closed the courthouse door on more than 100,000 plaintiffs who alleged that exposure to Roundup caused their cancer. The ruling was seven to two. It was written by Justice Brett Kavanaugh. And it rested, in its entirety, on fourteen words.</p><p>The EPA has determined that glyphosate is not likely to be carcinogenic to humans.</p><p>Because the EPA reached that conclusion, the agency never required a cancer warning on Roundup&#8217;s label. Because no cancer warning was required, Monsanto had no federal obligation to include one. Because Monsanto had no federal obligation to include one, state tort claims demanding it are preempted by federal law. The logic is a chain. Remove any link and the chain breaks. The fourteen words are the first link. Everything that followed depended on them holding.</p><p>This piece is about those fourteen words. Where they came from. How they were produced. What a federal appeals court found when it examined the methodology behind them. And what the EPA did when that court sent them back for correction.</p><p>Before going further, one thing needs to be stated plainly. Monsanto&#8217;s record in this dispute is not a matter of serious debate. Internal documents revealed coordinated strategies to influence research and public messaging. Ghostwriting. Conflicts of interest. A landmark study retracted due to ethical concerns and reliance on unpublished Monsanto data. Juries across the country, hearing the evidence directly, found for plaintiffs repeatedly. Billions of dollars paid in settlements. That record stands and is not in dispute here.</p><p>But this piece is not about Monsanto. It is about the other institution in the room. The one whose job was to stand between Monsanto&#8217;s conduct and the public. The one with the authority, the mandate, and the methodology to reach a conclusion independent of what Monsanto wanted that conclusion to be. The EPA is not a passive actor in this story. It is the regulator. And its record, examined closely, raises questions that the Supreme Court ruling made more urgent, not less.</p><p>How the Process Works</p><p>Under the Federal Insecticide, Fungicide, and Rodenticide Act, every pesticide sold in the United States must be registered with the EPA. Registration requires the manufacturer to demonstrate that the pesticide, when used as directed, will not cause unreasonable adverse effects on human health or the environment. The EPA evaluates that demonstration and either grants or denies registration.</p><p>The evidentiary foundation of that evaluation is primarily built from studies submitted by the manufacturer. The company seeking registration bears the cost of producing the safety data the agency reviews. This is not a hidden arrangement. It is the explicit structure of the regulatory system. The EPA does not independently commission its own toxicology studies. It reviews what industry provides, supplemented by published scientific literature.</p><p>The obvious structural tension in that arrangement -- that the party with the most to gain from a favourable conclusion is also the primary supplier of the evidence the agency uses to reach it -- has been noted by scientists, regulators, and courts for decades. The scientists who gathered in Seattle in March 2026 to review the glyphosate evidence proposed an overhaul requiring data from independent laboratories free from conflicts of interest, with the costs borne by industry but the research conducted outside its control. That proposal has not been adopted.</p><p>Registration is not permanent. The EPA conducts periodic registration reviews to assess whether pesticides already on the market continue to meet current safety standards. For glyphosate, that review process has been running, in various forms, for decades. The relevant modern chapter begins with the EPA&#8217;s 2017 and 2019 reviews, which reaffirmed the not likely to be carcinogenic conclusion, and the 2020 interim registration decision that a federal court later vacated.</p><p>Built into the registration review process is a check: the Scientific Advisory Panel. The SAP is an independent body of external scientific experts convened to review EPA&#8217;s methodology and conclusions. It can identify problems, flag inconsistencies, and recommend corrections. What it cannot do is compel the agency to act on its recommendations. The SAP&#8217;s findings are advisory. The EPA is not required to follow them. In the glyphosate review, the SAP identified specific methodological problems with EPA&#8217;s approach. The agency proceeded anyway.</p><p>What the Cancer Paper Said</p><p>At the centre of EPA&#8217;s glyphosate cancer assessment is a document known internally as the Cancer Paper. It is the agency&#8217;s systematic review of available evidence on glyphosate&#8217;s potential carcinogenicity, produced as part of the registration review process. It reviewed epidemiological studies, animal carcinogenicity data, and mechanistic evidence. It arrived at a bottom-line hazard descriptor: not likely to be carcinogenic to humans.</p><p>What the Cancer Paper said on the way to that conclusion is the problem.</p><p>The epidemiological data the paper reviewed did not point clearly toward safety. Effect estimates across the case-control studies and meta-analyses the agency examined were greater than 1, meaning most studies indicated glyphosate exposure was associated with an increased risk of non-Hodgkin&#8217;s lymphoma. The meta-analyses showed effect estimates ranging from 1.3 to 1.5, indicating people exposed to glyphosate were between 30 and 50 percent more likely to develop NHL than those who were not. The paper reviewed that signal and attributed it to chance, bias, or confounding factors.</p><p>The specificity of that signal matters scientifically. Non-Hodgkin&#8217;s lymphoma is not cancer generally. It is a defined category of more than 60 distinct lymphoma subtypes affecting the lymphatic system. A chemical showing a consistent epidemiological signal for a specific cancer type is a more focused and harder-to-dismiss finding than one correlating with cancer broadly. Confounding factors and lifestyle variables are harder to invoke against a specific biological target. The NHL signal is not a vague association. It is a documented pattern across multiple independent research groups pointing at the same disease.</p><p>That is a legitimate scientific judgment. Discounting effect estimates for methodological reasons is standard practice in epidemiological review. What is not standard is what the Cancer Paper said next.</p><p>The paper explicitly stated that a conclusion regarding the association between glyphosate exposure and risk of NHL cannot be determined based on the available evidence. Those are the agency&#8217;s own words. The evidence was, by EPA&#8217;s own assessment, insufficient to reach a conclusion on the central question.</p><p>The EPA then selected not likely to be carcinogenic to humans as its final hazard descriptor.</p><p>Under EPA&#8217;s own Cancer Guidelines, that descriptor is appropriate only when the available data are considered robust for deciding that there is no basis for human hazard concern. The agency said in one paragraph that it could not determine the NHL risk. It said in effect in the next that the data were robust enough to conclude there was no meaningful concern. Those two statements cannot both be true. The Cancer Paper contained them both, and the EPA signed off on the document.</p><p>What the Court Found</p><p>In June 2022, the Ninth Circuit Court of Appeals examined EPA&#8217;s glyphosate cancer determination in Natural Resources Defense Council v. EPA, 38 F.4th 34. The court&#8217;s findings were not a matter of contested scientific interpretation. They were a documented accounting of specific methodological failures, each traceable to EPA&#8217;s own guidelines and its own Scientific Advisory Panel&#8217;s contemporaneous objections.</p><p>The first failure was the one already visible in the Cancer Paper. The court found EPA could not reasonably treat its inability to reach a conclusion about NHL risk as consistent with a conclusion that glyphosate is not likely to cause cancer. The internal contradiction was not subtle. It was the difference between &#8220;we cannot determine the risk&#8221; and &#8220;there is no meaningful risk.&#8221; The agency published both in the same document.</p><p>The second failure concerned animal carcinogenicity data. The EPA used historical control data selectively, invoking it only to undermine tumor results, never to support them. EPA&#8217;s own Scientific Advisory Panel had flagged this practice during the review. The panel warned that to subjectively choose to use historical control incidence data only in situations where it undermines tumor results is to potentially introduce bias into the assessment. The agency was told this by its own advisory body. It proceeded anyway.</p><p>The third failure is the most striking because it involved something the EPA appears to have invented. The agency discarded tumor results occurring at or above what it called a 1,000 milligrams per kilogram per day limit dose, treating those results as uninformative. The Ninth Circuit found that EPA&#8217;s own Health Effects Test Guidelines establish no such limit. The guidelines state only that the highest tested dose need not exceed that figure. They do not say results above it should be discarded. EPA created a threshold that does not exist in its own methodology and used it to eliminate data that pointed toward cancer risk. The Scientific Advisory Panel called it an ad hoc decision that is not well-justified and is not justified on the basis of the Cancer Guidelines.</p><p>The court&#8217;s conclusion was precise. Inconsistent reasoning is, absent explanation, the hallmark of arbitrary action. EPA&#8217;s glyphosate cancer determination did not survive substantial evidence review. The Ninth Circuit vacated the relevant portion of EPA&#8217;s 2020 interim registration decision and remanded it for a methodologically sound explanation.</p><p>Note what the court did not say. It did not say glyphosate causes cancer. It did not say EPA&#8217;s ultimate conclusion was wrong. It said EPA&#8217;s reasoning was internally contradictory, that it relied on data selectively in ways its own panel flagged as biased, and that it invented a methodological threshold to discard unfavourable results. It sent the determination back for a do-over conducted honestly.</p><p>What EPA Did About It</p><p>The Ninth Circuit issued its ruling in June 2022. EPA withdrew its interim registration decision in response. The withdrawal notice, filed by the agency itself, stated: EPA&#8217;s underlying scientific findings regarding glyphosate, including its finding that glyphosate is not likely to be carcinogenic to humans, remain the same.</p><p>That sentence deserves to sit alone for a moment. A federal appeals court found EPA&#8217;s reasoning internally contradictory, its data use selectively biased, and its invented limit dose methodologically unjustifiable. EPA&#8217;s response, in the document withdrawing the vacated decision, was to announce that its underlying finding was not changing.</p><p>Not: we are reviewing the specific methodology the court identified as defective. Not: we are examining whether the limit dose threshold we applied is supported by our own guidelines. Not: we are reconsidering how we used historical control data after our own Scientific Advisory Panel warned us against it. The finding remains the same.</p><p>Four years passed. As of 2026, EPA had not finalized a revised, methodologically corrected cancer determination. Glyphosate products remained on the market under existing labels. The registration review the agency described as anticipated to be completed in 2026 was a timeline that had been anticipated and missed before.</p><p>In March 2026, with Supreme Court oral arguments weeks away, EPA made a public commitment. Responding to questions from The New Lede following a scientific symposium at which CDC, National Cancer Institute, and university researchers called for urgent regulatory action, the agency stated: &#8220;This year, EPA will undertake a comprehensive, transparent, and rigorous scientific review of glyphosate to evaluate its use and ensure decisions are fully aligned with the best available science as well as human health and environmental protections. That review will include expanded public access to underlying data and science, analysis of independent peer-reviewed research on potential cancer and developmental risks, evaluation of opportunities to reduce exposure, and coordination with USDA, HHS, and states.&#8221;</p><p>Three months later, the Supreme Court ruled seven to two in Bayer&#8217;s favour, using EPA&#8217;s existing not likely to be carcinogenic determination as the controlling federal science. The promised rigorous review had not been completed. The vacated methodology had not been corrected. The finding a federal court found legally unsupportable was treated by the Supreme Court as dispositive.</p><p>And now the legal pressure that might have compelled the review to actually happen has been eliminated by the ruling the unrevised determination made possible.</p><p>The Structural Question</p><p>The Ninth Circuit identified not one methodological failure but three, each documented, each flagged in advance by EPA&#8217;s own Scientific Advisory Panel, and each working in the same direction. Every failure discounted data pointing toward cancer risk. None of the failures discounted data pointing away from it.</p><p>When a regulatory process produces a consistent pattern of errors that consistently benefit one party, the question that follows is not simply whether mistakes were made. It is why the mistakes always pointed the same way.</p><p>This piece will not answer that question definitively. The primary documents do not support a definitive answer, and this series does not make claims the evidence does not support. What the primary documents do support is a precise accounting of the structural conditions under which those directional errors became possible.</p><p>The evidentiary foundation of EPA&#8217;s review was primarily built from industry-submitted studies. The manufacturer with the most to gain from a favourable conclusion was the primary supplier of the data the agency reviewed. The independent check on that process, the Scientific Advisory Panel, issued specific objections to specific methodological choices. Those objections were advisory and non-binding. The agency was not required to address them. It did not.</p><p>The registration review timeline has no enforcement mechanism. When EPA misses anticipated completion dates, there is no consequence. The agency anticipated completing the glyphosate review multiple times before 2026 and did not complete it. Glyphosate products remained registered and on the market throughout. The manufacturer faced no regulatory consequence from the delay. Plaintiffs attempting to litigate in the interim faced a SCOTUS ruling that used the incomplete, court-vacated review as its scientific foundation.</p><p>The manufacturer&#8217;s own statements confirm the directional pattern the structural conditions made possible. In July 2021, Bayer CEO Werner Baumann told investors that more than 90 percent of Roundup litigation claims had come from the residential lawn and garden market. His explanation for removing glyphosate from consumer products was unambiguous: &#8220;This decision is exclusively geared at managing litigation risk and not because of any safety concerns.&#8221; The residential user -- the casual applicator who trusted the label, skipped the PPE, did not shower immediately after use, and wore work clothes the next day -- generated nine of every ten cancer claims. The manufacturer&#8217;s response was not to fix the label. It was to exit the market segment.</p><p>One further structural assumption embedded in the regulatory model deserves naming. The &#8220;safe when used as directed&#8221; conclusion was built on studies using fresh, properly formulated product applied under controlled conditions. Glyphosate products degrade over time in storage. The surfactants and adjuvants that drive herbicidal efficacy -- the speed at which a product kills weeds visibly -- break down with age, temperature fluctuation, and exposure. But herbicidal degradation and carcinogenic potential are two separate biological mechanisms. The glyphosate molecule itself is chemically stable, non-volatile, and does not degrade in the presence of light or air. A bottle that has lost weed-killing speed has not lost glyphosate concentration. The consumer who uses more of an older product to compensate for reduced visible efficacy may be increasing their exposure to the compound of concern, not decreasing it. No label communicates this distinction. No regulatory model accounts for it.</p><p>The Tracey Woodruff observation, made at the March 2026 Seattle symposium, is worth returning to here. Woodruff is a professor at Stanford University and a former senior scientist for EPA&#8217;s own Office of Policy. She said: &#8220;It&#8217;s hard to get the government to change, particularly because the industry spends a lot of money lobbying Congress to make sure the laws favor their point of view.&#8221; That is not an activist claim. That is a former EPA scientist describing from the inside the structural dynamic the outside record confirms.</p><p>The structural conditions that allowed three directional methodological failures to survive EPA&#8217;s internal review process, survive the Scientific Advisory Panel&#8217;s contemporaneous objections, survive a federal court vacatur, and ultimately survive intact into a Supreme Court ruling are not accidental features of the system. They are the system. Industry-submitted evidence. Non-binding independent review. No enforcement timeline. No consequence for delay. And a legal architecture, now confirmed by the Supreme Court, that treats the output of that system as the controlling ceiling on what any American court can find.</p><p>What Comes Next, and a Note on Canada</p><p>The EPA committed in March 2026 to a comprehensive, transparent, and rigorous scientific review of glyphosate. That commitment is now the primary accountability lever remaining after the Supreme Court ruling eliminated the legal pressure to deliver it. Whether the review happens, whether it honestly addresses the three specific methodological failures the Ninth Circuit identified, and whether its conclusions are reached through independent evidence rather than industry-submitted data are the live questions this investigation will continue to monitor.</p><p>Congressional oversight of EPA&#8217;s registration review process is a second lever. The specific failures documented here -- the invented limit dose, the selective historical-control use, the internal contradiction between inconclusiveness and the not likely descriptor -- are on the public record in a published federal appellate decision. They are subjects that fall within congressional oversight authority. Whether any committee pursues them is a political question. The record exists regardless.</p><p>A note on Canada. EPA&#8217;s glyphosate determination does not exist in isolation. Canada&#8217;s Pest Management Regulatory Agency conducts its own registration reviews and has historically arrived at conclusions that mirror EPA&#8217;s on glyphosate, including its own not likely to be carcinogenic finding. That parallel raises a question the PMRA has not been required to answer publicly: did Canada&#8217;s review reach its conclusion independently, through its own methodological assessment of the available evidence, or did it proceed substantially from EPA&#8217;s prior determination? If Canada&#8217;s regulatory independence on glyphosate is procedural rather than substantive, the structural questions this piece raises about EPA apply with equal force north of the border. That question deserves its own investigation, and The Old Guardian intends to pursue it.</p><p>For now, the American record stands on its own. An agency whose methodology a federal court found internally contradictory and legally unsupportable. A withdrawn decision whose underlying finding the agency immediately announced was not changing. Four years without a corrected determination. A Supreme Court ruling built on the uncorrected foundation. And a promise of rigorous review made three months before the ruling that eliminated the pressure to keep it.</p><p>The fourteen words that closed the courthouse door on 100,000 plaintiffs came from somewhere. This piece has followed them back to their source. What was found there is not reassuring. And the institution responsible for those words has, so far, given no indication it intends to revisit them.</p><p>Editor&#8217;s Notes</p><p>Companion series: This piece is a companion to The Shield, a four-part Old Guardian series. Part One: &#8220;From Trust the Science to Shield Us from the Lawsuits&#8221; (published prior to the Durnell ruling). Part Two: &#8220;Seven to Two&#8221; (the ruling and the dissent). Part Three: &#8220;Trust the Regulators&#8221; (the EPA determination and the Ninth Circuit findings). Part Four: &#8220;The Architecture&#8221; (the full containment map). All four parts are available at theoldguardian.ca.</p><p>Primary sources: Natural Resources Defense Council v. U.S. Environmental Protection Agency, 38 F.4th 34 (9th Cir. 2022) (full opinion); Monsanto Co. v. Durnell, U.S. Supreme Court, decided June 25, 2026 (majority opinion by Kavanaugh, J.); EPA withdrawal notice following Ninth Circuit vacatur, 2022; EPA public statement on glyphosate registration review, March 2026, as reported by The New Lede (Carey Gillam, March 27, 2026) and verified against the original statement; EPA Cancer Paper, glyphosate registration review (internal language quoted via Ninth Circuit opinion at 38 F.4th 34); Scientific Advisory Panel findings on glyphosate methodology (cited within the Ninth Circuit opinion); International Agency for Research on Cancer, glyphosate classification as probable human carcinogen, 2015; Tracey Woodruff, Stanford University and former EPA Office of Policy senior scientist, statement at Seattle Glyphosate Symposium, March 2026, as reported by The New Lede; Bayer CEO Werner Baumann, investor call statement, July 29, 2021 (as reported by C&amp;EN, AgWeb, and Modern Farmer); Bayer AG, Five-Point Plan to Close the Roundup Litigation, May 2021.</p><p>Confidence tier: All findings attributed to the Ninth Circuit are drawn from the published decision at 38 F.4th 34. EPA&#8217;s withdrawal notice language is drawn from agency records as cited in court filings. The EPA March 2026 statement is quoted verbatim as verified against The New Lede&#8217;s March 27, 2026 report. The Baumann investor call quote is drawn from contemporaneous reporting across multiple outlets and from Bayer&#8217;s own published Five-Point Plan documentation. The herbicidal degradation versus carcinogenic potential distinction reflects established chemical stability data for glyphosate and is not an assertion about human health outcomes. No claim in this piece asserts definitively that glyphosate causes cancer in humans. The Canada/PMRA paragraph identifies a question for future investigation and does not assert a conclusion.</p><p>Ongoing monitoring: The Old Guardian will continue to monitor the EPA glyphosate registration review, the PMRA parallel review question, paraquat and chlorpyrifos preemption proceedings, and the $7.25 billion Roundup settlement fairness proceedings.</p><p>The Old Guardian | theoldguardian.ca</p>]]></content:encoded></item><item><title><![CDATA[Monsanto - The Shield Part 4 of 4]]></title><description><![CDATA[The Architecture]]></description><link>https://www.theoldguardian.ca/p/the-shield-part-four-of-four</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/the-shield-part-four-of-four</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Wed, 05 Aug 2026 09:45:24 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/241b4dbb-7f60-42ac-b7e4-dba275f25577_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The ruling did not happen on June 25, 2026. It was finished on June 25, 2026. Here is how it was built.</p><p>In Part Three of this series, we examined what the EPA determination at the centre of the Supreme Court ruling is actually worth, and what a federal appeals court already found when it looked closely at how the agency arrived at it. The answer was not reassuring. And nobody fixed it before it became the foundation of a seven-to-two Supreme Court decision that closed the courthouse door on more than 100,000 plaintiffs.</p><p>Part Three ended with a question: what does accountability look like when the courtroom is no longer an option?</p><p>Before answering that, it is worth understanding precisely how the courtroom was closed. Because it did not happen in a single Supreme Court ruling. It was constructed, track by track, over years. And the construction tells you something important about what it will take to build accountability in the other direction.</p><p>The Map</p><p>Six tracks. Each one a separate move. Each one pointing the same direction.</p><p>Track One: The Supreme Court argument.</p><p>Bayer&#8217;s preemption argument did not emerge fully formed. It was developed and refined through years of lower court litigation, tested in appellate courts, and finally carried to the Supreme Court in the Durnell case. The legal theory -- that FIFRA&#8217;s uniformity clause shields manufacturers from state failure-to-warn claims when the EPA has approved their label -- was Bayer&#8217;s highest-risk, highest-reward play. A loss would have meant the scientific debate continuing in trial courts indefinitely. A win, as the seven-to-two ruling demonstrated, meant the debate ending as a practical matter of law regardless of what the science eventually showed.</p><p>Track Two: The settlement as deadline pressure.</p><p>The $7.25 billion class settlement proposed in February 2026 was not simply a compensation mechanism. It was a timing instrument. With SCOTUS oral arguments set for April 27 and the opt-out deadline set for June 4, plaintiffs had to decide whether to accept the settlement before the Supreme Court ruled. Bayer needed that uncertainty hanging over claimants through the entire decision window. A SCOTUS win would dramatically reduce future liability; accepting the settlement before that win meant accepting less. Bayer structured the timeline to exploit that gap. Fourteen law firms representing nearly 20,000 claimants called the 600-page settlement agreement negotiated behind closed doors, handed to opposing counsel on announcement day, with fifteen days before Bayer sought preliminary approval. That is not how fair settlements are built. That is how you manufacture consent under a deadline.</p><p>Track Three: State shield laws.</p><p>While the federal legal strategy moved through the courts, Bayer was simultaneously running a state legislative campaign through a coalition called the Modern Ag Alliance. The alliance backed bills in multiple states declaring that a federally approved pesticide label satisfies any state-level duty to warn. North Dakota and Georgia passed such laws in 2025. In early 2026, Kentucky&#8217;s Republican-led legislature overrode Democratic Governor Andy Beshear&#8217;s veto to enact a version of the same law. Beshear, a former state attorney general, pointed out that cosmetics, personal hygiene products, and household cleaners all carry warning labels. Kentucky&#8217;s law would allow dangerous pesticides to be sold without any equivalent risk warnings. The legislature overrode him anyway. Three states with legislative shields in place before the SCOTUS ruling even landed.</p><p>Track Four: The executive order.</p><p>In early 2026, the Trump administration issued an executive order expanding domestic glyphosate production while offering liability protection to manufacturers. The order was framed as a national security and food independence measure. Most glyphosate is produced by Bayer in Germany and Syngenta in China; bringing production onshore, the administration argued, required legal protection because companies would otherwise face billions in potential lawsuits. Robert F. Kennedy Jr., HHS Secretary, defended the order. This is the same Robert F. Kennedy Jr. who represented Dewayne Johnson, the California groundskeeper who won $289 million from Monsanto in 2018 after a jury found the company failed to warn him about cancer risk. Kennedy was one of Johnson&#8217;s attorneys. He has stated publicly, as recently as early 2026, that he believes glyphosate causes cancer. He defended the liability protection order anyway. The fractures this created within the MAHA movement are real and ongoing.</p><p>Track Five: The Ruveon spinoff.</p><p>Days after the June 25 ruling, Bayer announced the separation of its glyphosate business into a new standalone entity called Ruveon. The timing was not coincidental. By ring-fencing the Roundup brand and all associated products into a separate subsidiary, Bayer insulates its core pharmaceutical and crop science divisions from whatever residual litigation survives the SCOTUS ruling. The claims that are not preempted, the types of suits the 2005 precedent left open, now land on Ruveon&#8217;s balance sheet rather than Bayer AG&#8217;s. Win the legal battle, spin off the remaining liability. The SCOTUS ruling and the spinoff are one sequenced strategy, not two separate corporate decisions.</p><p>Track Six: The Chinese glyphosate tariff petition.</p><p>Within days of the ruling, Bayer filed a trade petition seeking US duties on Chinese-made glyphosate. The petition was framed as protection against unfair competition. The effect, if granted, would be to hand Bayer dominant market position in the US glyphosate supply at precisely the moment its legal liability exposure has been minimized. The farmers who filed amicus briefs in Bayer&#8217;s favour during the Durnell case -- arguing glyphosate was essential to American agriculture -- are now the ones being squeezed by Bayer&#8217;s market protection play. The Amplification Principle question is worth asking directly: who actually benefited from the SCOTUS ruling? Not the farmers who defended the product in court. Not the 100,000 plaintiffs who lost their day in court. Bayer benefited. And Bayer moved immediately to consolidate that benefit into market dominance.</p><p>The Track That Failed</p><p>Not every track in the containment strategy succeeded. The pesticide industry had been pushing to include language in the 2026 Farm Bill giving the EPA sole regulatory oversight over pesticide labelling, a legislative codification of what the Durnell ruling accomplished judicially. The Republican-controlled House voted to strip it. The opposition came from an unexpected coalition: MAHA movement activists and progressive environmental groups finding themselves on the same side of a floor vote for entirely different reasons.</p><p>That failure matters for what it reveals. The six-track containment strategy is not invulnerable. When public attention coalesces around a specific legislative vehicle, in a specific window, with an unusual coalition, one track can be stopped. The Farm Bill provision was stopped. The lesson is not that the strategy failed. Five of six tracks succeeded, and the one that mattered most, the SCOTUS preemption argument, succeeded decisively. The lesson is that the strategy has seams, and those seams are where accountability efforts need to focus.</p><p>Beyond Roundup</p><p>The Durnell ruling does not apply only to glyphosate. It applies to any pesticide whose label has been approved under FIFRA. That means the preemption logic Kavanaugh established is now available to every manufacturer of every EPA-approved pesticide facing state failure-to-warn litigation.</p><p>Paraquat is the most immediate example. More than 6,000 plaintiffs have filed claims alleging paraquat exposure caused Parkinson&#8217;s disease. Syngenta, paraquat&#8217;s primary manufacturer, had already filed preemption motions in the paraquat MDL before Durnell was decided, anticipating the ruling. Those motions now have a seven-to-two Supreme Court decision behind them. Both plaintiff and defence attorneys in the paraquat litigation have told courts that the Durnell ruling could determine whether those 6,000 Parkinson&#8217;s claims survive.</p><p>Chlorpyrifos is a third pesticide now facing the identical preemption argument. Plaintiff firms are already recruiting Parkinson&#8217;s disease claimants for chlorpyrifos cases. The first lawsuit was filed in Pennsylvania days before the Durnell decision landed.</p><p>But the implications reach further than pesticides. In his majority opinion, Justice Kavanaugh referenced the preemption logic potentially applying to over-the-counter drugs, cosmetics, meat, poultry, eggs, and packaged foods, depending on how lower courts interpret the ruling. Each of those product categories has a federal regulatory approval process. Each of those processes could now function as a ceiling on state tort liability rather than a floor on safety requirements. The Durnell ruling is not a pesticide decision. It is a product liability restructuring event with implications across the consumer economy.</p><p>What Accountability Looks Like Now</p><p>The courthouse door is closed for failure-to-warn claims against Roundup. It is not the only door.</p><p>The most direct lever is the EPA review EPA promised in March 2026. The agency committed publicly to a comprehensive, transparent, and rigorous scientific review of glyphosate, including analysis of independent peer-reviewed research on potential cancer and developmental risks and expanded public access to underlying data. That commitment was made before the ruling that eliminated the legal pressure to deliver it. Whether EPA follows through, and whether the review honestly addresses the specific methodological failures the Ninth Circuit identified in 2022, is the live accountability question this series will continue to monitor. If EPA conducts a genuine review and reaches a different conclusion, the label changes. If the label changes, the preemption argument collapses for future plaintiffs. The ruling is not permanent. It is contingent on the EPA determination that underlies it.</p><p>Congressional oversight is a second lever. The EPA&#8217;s registration review process, its reliance on industry-submitted studies, its handling of the Ninth Circuit remand, and the specific methodological failures documented in the NRDC ruling are all subjects that fall within congressional oversight authority. Whether any committee pursues that oversight is a political question. The Farm Bill vote demonstrated that the unusual coalition capable of moving it exists. Whether it can be sustained and directed toward regulatory accountability is a different challenge.</p><p>State attorneys general retain authority the Durnell ruling did not touch. The preemption ruling bars state failure-to-warn tort claims. It does not bar state consumer protection enforcement, state public health regulation, state environmental monitoring, or state legislative action on pesticide use restrictions. Several states already ban or restrict glyphosate uses that federal law permits. That divergence can widen. It will require political will that the Modern Ag Alliance will continue to oppose, track by track, state by state.</p><p>International regulatory divergence is a fourth pressure point. The European Union has been moving toward tighter glyphosate restrictions for years. Canada&#8217;s Pest Management Regulatory Agency operates independently of EPA and has historically conducted its own reviews. If international regulatory bodies reach conclusions that diverge from EPA&#8217;s not likely determination, the scientific and political pressure on EPA to revisit its methodology increases. Bayer sells glyphosate products globally. A world in which the EU restricts glyphosate while the US shields manufacturers from liability is not a stable equilibrium.</p><p>And there is a fifth lever that is the most basic of all, and the one this series began with. The label.</p><p>If a product&#8217;s safety is genuinely unquestioned, manufacturers do not spend years and billions of dollars building legal, legislative, executive, and judicial shields against the consequences of that safety being examined. They compete on the evidence. The six-track containment strategy documented in this series is not the behaviour of a company confident in its science. It is the behaviour of a company managing a liability exposure it cannot resolve through science alone.</p><p>Consumers retain the right to ask questions the label does not answer. Farmers retain the right to choose inputs. Municipalities retain the right to restrict applications on public land. Journalists retain the right to publish what the primary documents show. None of those rights were closed by the Durnell ruling. The courtroom was the arena where evidence was tested, witness by witness, in front of twelve citizens. Losing that arena is not a small thing. But it is not the only arena.</p><p>Edwin Durnell</p><p>Edwin Durnell is still a Missouri man. He was still diagnosed with non-Hodgkin&#8217;s lymphoma. A Missouri jury still heard his evidence and still believed him. That did not change on June 25, 2026.</p><p>What changed is that the question his case raised -- did Monsanto have an obligation to warn him -- has been removed from the arena where it could be answered. Not because the answer is clear. Because the architecture built around the question made the question unanswerable in court.</p><p>This series began with a simple observation: the public was asked for decades to trust the science. The argument has shifted. It is no longer about the science. It is about whether the science can be litigated at all.</p><p>The question underneath that one has always been simpler. When a product causes harm, and a person is harmed, and a jury of that person&#8217;s peers finds the manufacturer failed in its duty to warn -- who decides whether that finding counts?</p><p>For now, the answer is: not a jury. Not a state court. A federal regulatory agency whose methodology a federal appeals court already found internally contradictory and legally unsupportable, and which restated its conclusion without correcting its methodology, and whose determination now functions as the permanent legal ceiling on what any American court can find about who was warned, and when, and whether it was enough.</p><p>That is the shield.</p><p>And that is what it was built to do.</p><p>Editor&#8217;s Notes</p><p>Primary sources for this series: Monsanto Co. v. Durnell, U.S. Supreme Court, decided June 25, 2026 (majority opinion by Kavanaugh, J.; concurrence by Thomas, J.; dissent by Jackson, J., joined by Gorsuch, J.); Natural Resources Defense Council v. U.S. Environmental Protection Agency, 38 F.4th 34 (9th Cir. 2022); EPA notification record for LARVIN Technical, EPA Reg. No. 264-343, Bayer CropScience, 2012; EPA public statement on glyphosate registration review, March 2026, as reported by The New Lede (Carey Gillam, March 27, 2026); Annals of Global Health, pesticide genotoxicity study, July 2026; International Agency for Research on Cancer, glyphosate classification as probable human carcinogen, 2015; Missouri circuit court settlement filings, February through July 2026; Kentucky General Assembly override record, 2026; Bayer AG corporate announcements on Ruveon spinoff, July 2026; US International Trade Commission petition filings, Bayer glyphosate antidumping case, June 2026.</p><p>Series note: The four parts of The Shield were developed sequentially as the legal proceedings unfolded. Part One was published before the Durnell ruling. Parts Two, Three, and Four were developed after the June 25, 2026 decision, using primary documents including the full Supreme Court opinion, the Ninth Circuit decision, and EPA regulatory filings. No claim in this series asserts definitively that glyphosate causes cancer in humans. The series reports what primary documents show about the legal, regulatory, and corporate architecture surrounding that question, accurately and at the correct epistemic level.</p><p>Ongoing monitoring: The Old Guardian will continue to monitor the EPA glyphosate registration review, paraquat and chlorpyrifos preemption proceedings, the Ruveon liability structure, and the $7.25 billion settlement fairness hearing scheduled for July 9, 2026.</p><p>The Old Guardian | theoldguardian.ca</p>]]></content:encoded></item><item><title><![CDATA[Monsanto - The Shield Part 3 of 4]]></title><description><![CDATA[Trust the Regulators]]></description><link>https://www.theoldguardian.ca/p/the-shield-part-three-monsanto</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/the-shield-part-three-monsanto</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Tue, 04 Aug 2026 09:45:33 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/a9c159ca-f6ec-4bc6-b681-f5aa409e8e14_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The Supreme Court&#8217;s ruling rests entirely on one EPA determination. Here is what that determination is actually worth.</p><p>In Part Two of this series, we examined what the Supreme Court actually held in Monsanto v. Durnell and what the dissent documented that the majority chose not to address. The ruling closed the courthouse door on more than 100,000 plaintiffs. It did not declare glyphosate safe. It rested entirely on a single factual predicate: the EPA has determined that glyphosate is not likely to be carcinogenic to humans, and therefore has never required a cancer warning on Roundup&#8217;s label.</p><p>When a new study published in the Annals of Global Health found this past week that glyphosate causes DNA damage in human cells at the lowest exposure levels tested, Bayer&#8217;s response was immediate. The study, the company told The New Lede, was not conducted with the same rigor as studies submitted to regulatory agencies. Assessments by regulatory authorities, Bayer said, do not support the conclusions of this study.</p><p>In other words: trust the regulators.</p><p>That is a reasonable ask. It is also an invitation to look closely at what the regulators actually did. When you do, the picture is not reassuring.</p><p>What the EPA&#8217;s Own Paper Said</p><p>The EPA&#8217;s determination that glyphosate is not likely to be carcinogenic to humans is not a simple finding. It is the headline conclusion of a Cancer Paper the agency produced as part of its registration review of glyphosate. That paper reviewed the available epidemiological studies, animal carcinogenicity data, and mechanistic evidence, and arrived at a bottom-line hazard descriptor: not likely to be carcinogenic to humans.</p><p>What the paper said along the way to that conclusion is a different matter.</p><p>The epidemiological data the EPA reviewed did not point clearly in one direction. Effect estimates across the case-control studies and meta-analyses the agency examined were greater than 1, meaning most of the studies indicated that glyphosate exposure was associated with an increased risk of non-Hodgkin&#8217;s lymphoma. The meta-analyses showed effect estimates ranging from 1.3 to 1.5, indicating that people exposed to glyphosate were between 30 and 50 percent more likely to develop NHL than those who were not.</p><p>The EPA reviewed that data and discounted it, attributing the elevated estimates to chance, bias, or confounding factors. That is a legitimate scientific judgment call. What is not legitimate is what the Cancer Paper said next.</p><p>The paper explicitly stated that a conclusion regarding the association between glyphosate exposure and risk of NHL cannot be determined based on the available evidence. That sentence, written by the EPA&#8217;s own reviewers, means the agency could not reach a conclusion on the central question. The evidence was, in the agency&#8217;s own words, insufficient to decide.</p><p>The EPA then selected not likely to be carcinogenic to humans as its final hazard descriptor.</p><p>Under the EPA&#8217;s own Cancer Guidelines, that descriptor is appropriate only when the available data are considered robust for deciding that there is no basis for human hazard concern. The EPA said in one paragraph that it could not determine the cancer risk. It said in the next, in effect, that the data were robust enough to conclude there was no meaningful risk. Those two statements cannot both be true.</p><p>That internal contradiction sat inside EPA&#8217;s Cancer Paper for years. The scientific debate continued. The lawsuits multiplied. The agency did not revisit its conclusion.</p><p>What a Federal Court Found</p><p>In 2022, the Ninth Circuit Court of Appeals examined EPA&#8217;s glyphosate cancer determination in Natural Resources Defense Council v. EPA. What the court found was not a close scientific disagreement between regulators and critics. It was a documented series of methodological failures that rendered the agency&#8217;s conclusion legally unsupportable.</p><p>The first problem was the one already visible in the Cancer Paper itself. The court found that EPA could not reasonably treat its inability to reach a conclusion about NHL risk as consistent with a conclusion that glyphosate is not likely to cause cancer. The agency said it could not determine the risk and then issued a determination. The court said that is not how science or law works.</p><p>The second problem was the way the EPA handled its animal carcinogenicity data. The agency used historical control data selectively, invoking it only when it undermined tumor results, never when it might support them. EPA&#8217;s own Scientific Advisory Panel flagged the practice during the review process, warning that to subjectively choose to use historical control data only in situations where it undermines tumor results is to potentially introduce bias. The agency proceeded anyway.</p><p>The third problem is the most striking. The EPA discarded tumor results occurring at or above what it called a 1,000 milligrams per kilogram per day limit dose, treating those results as uninformative for cancer assessment purposes. The Ninth Circuit found that EPA&#8217;s own Health Effects Test Guidelines establish no such limit. The guidelines state only that the highest tested dose need not exceed that figure. They do not say results above it should be discarded. The EPA invented a threshold that does not exist in its own methodology and used it to eliminate unfavorable data. The Scientific Advisory Panel called it an ad hoc decision that is not well-justified and is not justified on the basis of the Cancer Guidelines.</p><p>The court&#8217;s verdict was unambiguous. Inconsistent reasoning is, absent explanation, the hallmark of arbitrary action. EPA&#8217;s glyphosate cancer determination did not survive substantial evidence review. The court vacated the relevant portion of EPA&#8217;s 2020 interim registration decision and sent it back to the agency for a methodologically sound explanation.</p><p>The court acknowledged it was possible EPA could reach the same conclusion on remand. But it would need to get there honestly, through reasoning that did not contradict itself and did not rely on thresholds the agency invented for the occasion.</p><p>What EPA Did About It</p><p>The Ninth Circuit issued its ruling in June 2022. What happened next is the accountability story at the centre of this series.</p><p>EPA withdrew its interim registration decision in response to the ruling. The withdrawal notice, filed by the agency itself, stated explicitly: EPA&#8217;s underlying scientific findings regarding glyphosate, including its finding that glyphosate is not likely to be carcinogenic to humans, remain the same.</p><p>Read that again. The agency whose methodology a federal appeals court found internally contradictory and legally unsupportable announced, in the very document withdrawing the vacated decision, that its underlying finding was not changing. Not: we are reviewing our methodology. Not: we are examining the specific failures the court identified. The finding remains the same.</p><p>Four years passed. As of 2026, EPA had not finalized a revised cancer determination. Glyphosate products remained on the market under existing labels. The agency described its final registration review as anticipated to be completed in 2026, a timeline that had been anticipated and missed before.</p><p>In March 2026, with the Supreme Court case already accepted and oral arguments months away, EPA made a public commitment. The agency announced it would undertake a comprehensive, transparent, and rigorous scientific review of glyphosate, including analysis of independent peer-reviewed research on potential cancer and developmental risks and expanded public access to underlying data. The statement was detailed and specific. It named coordination with USDA, HHS, and state agencies. It mentioned strengthened monitoring of residues in food and water.</p><p>Three months later, the Supreme Court ruled seven to two in Bayer&#8217;s favour, using EPA&#8217;s existing not likely to be carcinogenic determination as the load-bearing foundation of the entire decision. The promised rigorous review had not been completed. The vacated methodology had not been corrected. The finding the Ninth Circuit found legally unsupportable was treated by the Supreme Court as controlling federal science.</p><p>More than 100,000 plaintiffs lost their clearest path to court on the basis of a determination that a federal appeals court had already found did not hold up to scrutiny.</p><p>What the Science Outside the Agency Found</p><p>While EPA ran out the clock on its registration review, the independent scientific literature was not standing still.</p><p>In 2015, the International Agency for Research on Cancer, the cancer research arm of the World Health Organization, classified glyphosate as a probable human carcinogen. That classification was based on a systematic review of the published scientific literature, conducted by an independent panel of scientists with no industry funding. It has not been retracted.</p><p>In March 2026, a group of experts gathered in Seattle to evaluate the scientific evidence on glyphosate health impacts. Luoping Zhang, adjunct professor of toxicology at the University of California Berkeley, told The New Lede that the science is pretty clear on glyphosate&#8217;s ability to cause genetic damage in exposed humans and in human cells.</p><p>This past week, the Annals of Global Health published the study Bayer dismissed in its statement. Researchers tested ten pesticides and found eight caused DNA damage in human cells. Glyphosate produced cell damage at the lowest exposure levels tested. The researchers concluded there may be almost no safe threshold of human exposure. It was the first study to confirm that pesticide mixtures were also toxic to cells, a finding with implications beyond glyphosate alone.</p><p>None of this proves definitively that glyphosate causes cancer in humans at real-world exposure levels. Scientific consensus on complex risk questions rarely arrives in a single study. But the accumulating independent literature points in a consistent direction, and that direction is not toward the EPA&#8217;s not likely conclusion.</p><p>Bayer&#8217;s instruction to trust the regulators over independent peer-reviewed science is therefore not a neutral appeal to authority. It is an appeal to the specific regulatory determination that shields Bayer from liability, produced through a methodology a federal court found arbitrary, restated unchanged after that court&#8217;s ruling, and now enshrined as controlling federal law by the Supreme Court.</p><p>The Question Now</p><p>EPA promised in March 2026 a comprehensive, transparent, and rigorous scientific review of glyphosate. That promise was made before the Supreme Court ruling that eliminated the legal pressure to deliver it. The question of whether that review now happens, and whether it honestly addresses the specific methodological failures the Ninth Circuit identified, is the live accountability thread this series will continue to monitor.</p><p>There is a second question, less comfortable but necessary. The EPA does not conduct its pesticide registration reviews in isolation. The process involves industry-submitted studies, agency reviewers, scientific advisory panels, and decades of accumulated regulatory decisions that create institutional inertia. The Ninth Circuit identified not one methodological failure but a pattern of them, each working in the same direction, each discounting data that pointed toward cancer risk.</p><p>When a regulatory process produces a consistent pattern of errors that consistently benefit one party, the question that follows is not simply: did the agency make mistakes? It is: why did the mistakes always point the same way?</p><p>That question does not have a simple answer, and this series will not pretend it does. What can be said, on the basis of primary documents alone, is this: a federal appeals court found EPA&#8217;s glyphosate cancer methodology internally contradictory and legally unsupportable. The agency restated its conclusion without fixing the methodology. The Supreme Court used that unrevised conclusion to close the courthouse door on 100,000 plaintiffs. And Bayer responded to new independent science by telling the public to trust the regulators.</p><p>In Part Four of this series, we map the full architecture of how that outcome was built, track by track, and ask what accountability looks like when the courtroom is no longer an option.</p><p>Editor&#8217;s Notes</p><p>Primary sources for this piece: Natural Resources Defense Council v. U.S. Environmental Protection Agency, 38 F.4th 34 (9th Cir. 2022); EPA withdrawal notice following Ninth Circuit vacatur, 2022; EPA public statement on glyphosate registration review, March 2026; Annals of Global Health, pesticide genotoxicity study, July 2026 (as reported by The New Lede); International Agency for Research on Cancer, glyphosate classification as probable human carcinogen, 2015; EPA Cancer Paper, glyphosate registration review (internal language quoted via Ninth Circuit opinion); Bayer AG statement to The New Lede, July 2026.</p><p>Confidence tier: All findings attributed to the Ninth Circuit opinion are drawn from the published decision at 38 F.4th 34. EPA&#8217;s withdrawal notice language is quoted as reported in court filings and agency records. The Annals of Global Health study is peer-reviewed; the finding that glyphosate showed cell damage at the lowest tested exposure level is reported directly from The New Lede&#8217;s coverage of the study. No claims in this piece assert definitively that glyphosate causes cancer in humans; the piece reports what the scientific literature, the EPA&#8217;s own Cancer Paper, and the Ninth Circuit found, accurately and at the correct epistemic level.</p><p>The Old Guardian | theoldguardian.ca</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/the-shield-part-three-monsanto?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/the-shield-part-three-monsanto?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/the-shield-part-three-monsanto?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/the-shield-part-three-monsanto/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/the-shield-part-three-monsanto/comments"><span>Leave a comment</span></a></p><p></p>]]></content:encoded></item><item><title><![CDATA[TDSB - The Case for Supervision]]></title><description><![CDATA[A good faith Argument.]]></description><link>https://www.theoldguardian.ca/p/the-case-for-supervision</link><guid isPermaLink="false">https://www.theoldguardian.ca/p/the-case-for-supervision</guid><dc:creator><![CDATA[Christopher Allen]]></dc:creator><pubDate>Mon, 03 Aug 2026 09:46:16 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/0f68455d-f595-47e1-bd10-c1e707bd7461_1672x941.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h2>A note before you read this:</h2><p>Everything I publish here starts from a position I&#8217;ve built through two years of reporting. That&#8217;s normal, and it&#8217;s how it should work. But it also means I owe it to you, and to the work itself, to occasionally test that position against its strongest opposition rather than its weakest.</p><p>So this piece is an exercise. I assigned myself the other side, arguing for supervision as persuasively as the actual evidence allows, not as a strawman, not cherry-picked to fail. The goal wasn&#8217;t to convince you supervision was right. It was to find out whether my own conclusions could survive contact with the best version of the argument against them. You learn more about what you actually believe, and why, by seriously trying on the other position than by only ever defending your own.</p><p>What follows is that argument, built honestly from real sources, some of which I&#8217;ve already reported on myself. At the end, I come back as myself and tell you where it held up and where it didn&#8217;t.</p><h2>The Case for Supervision</h2><p>For two years, critics of provincial supervision have treated it as self-evidently a power grab, a pretext, an ideological project dressed up as fiscal responsibility. That framing has to work hard to ignore what was actually sitting in these boards&#8217; own records before the Ministry ever stepped in.</p><p>Start with what an independent auditor found, not a Ministry press release, the Auditor General of Ontario, examining TDSB&#8217;s own conduct from 2017 to 2023, entirely before any supervisor arrived. No long-term capital plan existed for a board with the worst Facility Condition Index in the province. Six completed capital projects ran an average of 39 months over the board&#8217;s own estimates, at $146 million against $102 million approved. Violent incidents in schools hit a six-year high, up 67 percent since 2017, and the board underreported them to the Ministry by 9 percent. Fifty-three of sixty-six administrators were placed on paid leave during investigations, some for over 1,200 days, costing $4.3 million, with no documentation justifying the leave in the majority of sampled cases. An Expert Reference Panel on school safety was disbanded the same month it delivered its recommendations.</p><p>None of that is Calandra&#8217;s characterization. That&#8217;s the province&#8217;s own independent auditor, and it describes a board that had lost the basic administrative competence to run itself, years before supervision existed as an option on the table.</p><p>Critics point to PwC&#8217;s investigation finding no evidence of deliberate wrongdoing or recklessness, as though that settles the matter. It doesn&#8217;t. A forensic investigation not finding fraud is not the same as finding the institution was being run well. The deficits were real and compounding across TDSB, TCDSB, Peel, and Dufferin-Peel simultaneously, an unusual clustering that suggests a systemic problem with how Ontario&#8217;s largest boards were governing themselves under a structure of 22 or more trustees with limited financial expertise, not four unrelated coincidences. When Peel&#8217;s own chair disputes &#8220;mismanagement&#8221; and calls it underfunding, that&#8217;s the institution being investigated defending itself. It would be surprising if he said anything else.</p><p>Bill 101&#8217;s consolidation of trustees from 22 to 12, defenders would argue, is not democratic erosion, it&#8217;s an acknowledgment that a board this size had become too large to govern effectively, exactly the diagnosis the Auditor General&#8217;s own findings support. Toronto is the only board of 72 in the province over the new cap. That&#8217;s not an arbitrary target, it&#8217;s the biggest instance of the exact problem being addressed.</p><p>On responsiveness, critics have built a narrative that supervision means nobody is accountable. The record doesn&#8217;t support that as a blanket claim. When Rosedale Heights parents and students organized against Barrie Sketchley&#8217;s transfer, the supervisor reversed it within two months, a faster and more direct response than the elected board had ever offered on a comparable community dispute. Whatever else is true about how that reversal came about, it demonstrates a supervisor capable of responding to public pressure, not one insulated from it by design.</p><p>And on land, the harder case for skeptics, the province would argue there&#8217;s a coherent, defensible logic that has nothing to do with a hidden agenda. A board losing tens of millions of dollars a year while sitting on a $15 to 20 billion property portfolio is not a board that has optimized its own assets. Pursuing higher-value zoning designations on underused sites isn&#8217;t proof of a plan to sell schools out from under students, both boards remain on record stating they aren&#8217;t, it&#8217;s what any competently run institution with a real estate arm this size would be expected to do with property it isn&#8217;t using to capacity.</p><p>The honest version of this case is not &#8220;everything critics have found is wrong.&#8221; It&#8217;s narrower and more defensible than that: a demonstrably dysfunctional governance structure, documented independently and before supervision existed, justified an intervention that has been applied unevenly, sometimes responsive, sometimes not, but whose original premise holds up better than the &#8220;manufactured crisis&#8221; framing gives it credit for.</p><p>Post-exercise note: Where this argument is strongest is exactly where it leans on the Auditor General&#8217;s findings, those are independently corroborated and genuinely damning on their own terms. Where it&#8217;s weakest is where it has to explain away the parts that don&#8217;t fit, Calandra&#8217;s own &#8220;no constitutional cover&#8221; quote, the TLC transparency narrowing that postdates the audit and can&#8217;t be explained by pre-supervision dysfunction, and the uneven pattern where responsiveness tracks with how much political noise a community can generate rather than with any consistent standard. The steelman survives as an argument that intervention was justified. It does not survive as an argument that everything done since has been in good faith or free of the centralization the series has documented. Those are two separate claims, and conflating them is the rhetorical move worth watching for the next time this argument shows up in a National Post column.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Old Guardian&#8217;s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/the-case-for-supervision?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Old Guardian&#8217;s Substack! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/the-case-for-supervision?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/the-case-for-supervision?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.theoldguardian.ca/p/the-case-for-supervision/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.theoldguardian.ca/p/the-case-for-supervision/comments"><span>Leave a comment</span></a></p>]]></content:encoded></item></channel></rss>