← Red Threads

Canadian TCAP contributions: named recipient, amendment and agreement scope

9 September 2026. Bounded public acquisition closed. No account, outreach, paid request, harmful-content access, new case record or canonical mutation. This lane read actual proactive-disclosure record pages, not just indexed snippets. Nine original public responses and their hashes/scopes are retained in canadian-award-captures.json. Executed agreements and payment evidence were not acquired.

The new evidence

The Canadian disclosures supply the recipient/project connection that the earlier announcement left indirect. They name QuantSpark Foundation for TCAP agreement 21415, and Online Harms Foundation for Phase 2 agreement 22841. Their fields explicitly identify these as recipient legal names. The current official data schema says that field should come from the agreement, and that agreement value means the total stated in the agreement, in CAD, not an amendment increment. These are government-published disclosure assertions about agreements, not the signed instruments themselves.

All three identify Public Safety Canada and (CRF) Community Resilience Fund. Full substantive record fields were read, including expected outcomes. Those expected outcomes concern identifying emerging issues and research/programming gaps, applying relevant initiatives, best practices and partner preparedness; they are not measurable project-specific milestone schedules or proof of outcomes delivered.

The amendment's derived increase is CAD 101,065.65. Adding the two displayed 21415 totals would double-count the pre-amendment commitment. The start dates differ by one day—26 February in the original entry versus25February in the amended entry—and the end date changes. Preserve those source values; no signed original/amendment was acquired to resolve the one-day discrepancy. The panel is an amendment disclosure, not evidence of a third payment or award.

How this changes the earlier announcement

The retained [20 September 2022 Public Safety release](http[local research file] announces up toCAD 1.9million over three years to TAT for Phase 2 and retrospectively says approximatelyCAD 1million was provided in June 2019 to create TCAP. Its original was acquired and fully read in the preceding private-verification lane, not reacquired here; SHA256 4f830f539c2839ae245a4c04e29f2b8a41f072f58e2feee0a6b27faea4cfb619. Prior scope: ../private-verification-wave-2026-09-09/tat.md and its capture manifest.

The newly acquired records add precise totals, an explicit amendment, legal-name fields, agreement identifiers and later periods. The 2022 announcement's1.9million formulation is not exactly the1,945,904 later disclosed total. It may be announcement rounding or later agreement setting, but no acquired record explains the difference. Likewise, the 2019 statement and the 2020 agreement entry are not automatically separate funding: same project language is a strong reconciliation lead, but does not prove the timing or allocation of the reported 2019 provision. Do not add announcement figures to agreement totals or recast agreement value as paid cash.

Identity boundary. The accepted Companies House packet identifies company 11656320 as Online Harms Foundation, previously QuantSpark Foundation until11May 2021. This supports reading these labels as the historical names of the same company, distinct from QuantSpark Limited company 10304694. That legal-name history is retained prior primary research, not a fresh registry inspection in this lane. The November 2021 Canadian amendment continues to display the former Foundation name after the reported UK name change; this may be a legacy agreement label. It is not evidence of a second foundation, an undisclosed recipient or the Limited company itself receiving the Canadian award. No UK company number appears in the inspected Canadian records, so the registry-number crosswalk remains separately sourced.

Public funding controls — actual current terms, not invented historical schedules

The [CRF Terms and Conditions](http[local research file] page modified 25 May 2026, were read completely, sections1–15.6. They provide department-approved project budgets (§8), Steering Committee proposal/cost decisions (§12), and conditional, auditable contributions tied to milestones (§13). Contributions require financial/nonfinancial reporting and final expenditure accounting; frequency depends on risk (§15.2). Progress payments require departmental acceptance of interim financial/project reports, with risk/cash-flow-based advances possible (§15.4).

Recipient copyright remains; a royalty-free, permanent, nonexclusive departmental licence may be given (§10), not automatic government ownership. Onward redistribution requires prior departmental approval, while recipients independently choose beneficiaries with minimal guidance and do not act as government agents; selection records may be reviewed (§15.6). This is approval of redistribution plus recipient selection discretion, not unconstrained pass-through or automatic control of every subcontract. No actual redistribution, licence or content-classification instruction is proved.

These currently published terms show a concrete programme architecture. They do not establish which version or bespoke schedules governed 21415/22841, when a particular milestone was accepted, whether money was advanced/reimbursed, or whether a donor exercised any selection right. The precise executed agreements, incorporated terms, approved budgets, reporting schedules, amendment and acceptance/payment records remain the decisive missing documents.

Source ancestry and finite frontier

The original announcement led to a narrowly targeted search of official grants disclosures. Indexed results surfaced TCAP identifiers but their very large paginated URLs had changed contents when opened; those stale snippets were discovery only. The live filtered public search returned the exact record hrefs subsequently read and retained. A web-reader failure on the TCAP search, a403 on the dataset landing and cache miss on the Phase 2 detail were resolved by one ordinary unauthenticated GET of each public page; there was no proxy, account, authentication workaround or repeated failed route. Other acquisition GETs succeeded on first attempt.

The [official dataset landing](http[local research file] links the [public schema](http[local research file] Only the agreement-value, start/end-date, amendment-date/number and recipient-legal-name definitions were read. The schema distinguishes projected end dates from completed performance. Its current guidance helps interpret displayed records but does not retroactively certify historical data quality. The million-record bulk CSV was not downloaded. No broad recipient roster was harvested.

Ten targeted search queries covered TCAP/TAT/OHF in official grants records, agreement 21415/22841, the dataset, CRF reporting and programme terms. A 2019–20 departmental-results-report hit and general programme-plan snippets were discovery only; they were not acquired or added as evidence. The old and current award record bodies and amendment panel were read in full. The four-record extract is a derivative for local navigation; no original text is altered. Full metadata and SHA256 appear in the adjacent manifest.

Forest implication: the useful path is now Public Safety Canada→identified contribution→named foundation→specified TCAP workstreams. This does not prove Canada→QuantSpark consultancy payment, classification command, individual removal or Australian deployment. Those would require their own allocation/implementation records. The most discriminating next record is the executed 21415 amendment or 22841 agreement with its approved budget and payment/milestone annex, then a corresponding acceptance/payment record. Public Safety Canada's CRF grants/contributions administrators and the recipient hold them. No request or follow-up branch was initiated.

Original custody

Four-record normalized extract (derivative) SHA256: 57f51a5f2a1d76cec0dd75148ff9524b3eceacc8931ad469aeb91acdc4a6292b.