Build1 distinct publisher3 min readUpdated
A University of Toronto team read the whole inventory. It documents adoption, back-office use and vendor dependence, but not who exercises judgment when a system gets something wrong.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
A University of Toronto research team read every entry in Canada's federal AI register, all 409 systems in its snapshot, and published the analysis for the 2026 ACM Conference on Fairness, Accountability, and Transparency [1][2]. The useful result is not the headcount but the omission: according to the authors, the register establishes that AI has been adopted while obscuring who exercises judgment, what training or staffing a system needs, and how uncertainty gets handled [11].
The team combined quantitative mapping with qualitative coding against the ADMAPS public-sector framework [3]. Eighty-six percent of listed systems were intended for internal operations [4], which works out to roughly 352 of the 409 [1]. This is back-office software: the register is largely a record of administrative plumbing, not of systems making decisions about citizens at the counter. Forty-four percent were in development and 39% in production [5], leaving about 17%, or roughly 70 systems, in neither of those two states [2]. Agencies are building and running at the same time.
Vendor dependence is where the register gets interesting and where it stops being comparable across institutions. The Ottawa Citizen reported on Aug. 14 that some agencies listed only internally developed tools while others leaned heavily on outside suppliers [6]. Lead author Dipto Das told the newspaper that Microsoft, OpenAI and Google appeared among those third parties [7]. Three of the four systems listed for the Canadian Radio-television and Telecommunications Commission were developed by Microsoft [8], which is 75% of that regulator's disclosed inventory [5]. One agency's profile is not the federal profile, and the study's own emphasis is on uneven reporting [16].
Coverage is the other limit. The register spans 42 organizations while the federal government has more than 200 departments and agencies [9], so at most about one in five federal bodies is represented, and probably fewer [3]. The Citizen also noted the register had grown to 412 entries since the 409-system snapshot [10], a net addition of three [4]. A separate March review by Evidence for Democracy covered the same register and recorded more than 400 uses across 42 agencies, and is not the study behind the August coverage [15].
The authors' warning is worth restating plainly: technical descriptions can make a system look like dependable tooling when the outcome actually depends on organizational choices and human review [12]. The fix is documentation depth, not more rows. An inventory that could be audited would name the responsible organization, vendor and hosting dependencies, lifecycle stage, data categories, human decision points, the validation process, and a route for contesting an outcome [13]. Counts establish how widely AI has spread; they say nothing about whether any given system is safe, effective or accountable [14].
Watch whether the register's schema gains human-decision and contestability fields rather than just more entries, and whether coverage moves past 42 organizations toward the 200-plus that exist [9][13]. Watch the CRTC specifically: a telecom regulator whose disclosed AI stack is three-quarters supplied by one vendor is a procurement question before it is an AI question [8][5].
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
A University of Toronto research team analyzed all 409 systems in the Canadian federal AI register.
The paper was published for the 2026 ACM Conference on Fairness, Accountability, and Transparency.
The study used quantitative mapping and qualitative coding based on the ADMAPS public-sector framework.
The researchers reported that 86% of registered systems were intended for internal operations.
The study found 44% of registered systems were in development and 39% were already in production.
The Ottawa Citizen reported on Aug. 14 that some agencies used only internally developed tools while others relied heavily on external vendors.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Complete-register counts, single-publisher relay
The underlying work is strong in kind: a full-population analysis of all 409 register entries with reproducible counts, a named conference venue and a named coding framework, plus corroborating newspaper reporting with a named lead author. But everything reaches this cluster through one aggregator with no primary paper or register link, no confidence intervals, and no performance or outcome data, and the register's own uneven disclosure caps what the counts can establish.
409 systems, 39% in production, 42 of 200-plus bodies
Adoption is documented rather than projected: a disclosed inventory of 409 systems (412 by mid-August) with 39% already in production and 44% in development, concentrated in internal back-office use. Breadth is bounded, however, because only 42 organizations appear against a federal estate of more than 200 departments and agencies, so the register measures disclosed adoption, not total adoption.
Claims track the evidence, slightly conservative
The cluster's framing is unusually restrained for an adoption story: every headline number is attributed, the vendor finding is explicitly not generalized to all agencies, and the report states outright that counts establish breadth but not safety, effectiveness or accountability. If anything the write-up understates the governance implication of a register covering fewer than one in five federal bodies, which is why the gap sits marginally below zero rather than at it.
Content-marketing publisher, academic authorship
The publishing page carries a commercial upsell for paid SQL and Python practice datasets, so the write-up has a lead-generation incentive around governance-flavoured news. The underlying findings, by contrast, come from academic authors publishing at a peer-reviewed fairness and accountability venue and from a newspaper, and no vendor sponsorship, funding relationship or government commissioning is disclosed anywhere in the cluster, so the incentive load is real but modest.
Specific and internally consistent, but unreplicated here
Figures are specific, mutually consistent and arithmetically checkable, and one independent review of the same register lands in the same range, which supports moderate confidence. Confidence is held below that by the single-publisher cluster, the absence of primary documents, an unverifiable exact date for the March comparison review, and the fact that the most actionable material - the inventory field list - is the report's own prescription.
build
Grok 4.6 lands in Copilot two days after launch, and the model picker becomes a procurement problem1 distinct publisher
product
Washington's secret AI test is coming for open weights, and release dates go with it2 distinct publishers
product
The AI-wrote-it claim died in eight hours. The Actions injection pattern did not.1 distinct publisher
invest
Microsoft's Idle AI Chips Are A Construction Problem, Not A Shortage1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 14, 2026