aceTRV-2026-1118Version 3 · Revised
Reason for this version
Copy cleanup: removed remarks about truncated source text.
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1118 version: 3 kind: revised reason: Copy cleanup: removed remarks about truncated source text. timestamp: 2026-11-04T09:00:01.581660Z status: published lens: general sector: policy headline: Silicon Valley shouldn’t self-regulate on AI safety, Cohere CEO says dek: TORONTO — Aidan Gomez, CEO of Canadian AI company Cohere, says a "small group of companies in Silicon Valley" shouldn’t be left in charge of ensuring AI is safe. gain_title: (none) problem_title: Concentrating AI safety governance in a small group of Silicon Valley companies risks inadequate public oversight trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: Concentrating AI safety governance in a small group of Silicon Valley companies risks inadequate public oversight problem_evidence: small group of companies in Silicon Valley quick_read: On 2026-09-15, reporting from Toronto cited Cohere CEO Aidan Gomez saying a small group of companies in Silicon Valley should not be left in charge of ensuring AI is safe. limitation: tag: Context key_points: Aidan Gomez is identified as CEO of Canadian AI company Cohere speaking in Toronto | Statement targets concentration of AI safety oversight in a small group of Silicon Valley companies | Source frames issue as who should be in charge of ensuring AI is safe rundown: The item is datelined Toronto and attributes the position to Aidan Gomez, CEO of Canadian AI company Cohere. The quoted concern is that a small group of companies in Silicon Valley should not be left in charge of ensuring AI is safe, raising a policy question about self-regulation versus broader oversight. sources: - journalism | BayToday | https://www.baytoday.ca/national-news/silicon-valley-shouldnt-self-regulate-on-ai-safety-cohere-ceo-says-12781344 | 2026-09-15 prev: 6131ea7ace47f033574d8055d6ac4044baf0d8cfeaadaa140d8367bc6b249e6b
- sha256
- f65a12850bcb2b05658ad09abb7e6f8aa0840ee43b1a7a89149ca5fcc18f6f93
- previous
- 6131ea7ace47f033574d8055d6ac4044baf0d8cfeaadaa140d8367bc6b249e6b
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1118 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.