VerifiedIntelligence
The Week the Record Caught Up With the Claim
Across seven domains this week, cybersecurity to verification research, the record kept saying less than the label claimed.
My book, Enterprise Architecture in Practice: A Field Guide to Applying the TOGAF® Standard, releases on 1 November 2026. Across nineteen chapters it follows one fictional company, Astela Telecommunications, through the whole method, for architects working under real constraints. This book is independent of, and has not been reviewed, approved or endorsed by, The Open Group.
This week's seven pieces keep landing on the same gap: a claim that something is settled or controlled, against what the primary record supports once checked. A regulator's "nothing new" statement covers obligations of different ages. A kernel version string named a release that did not exist for three more days. A vendor named a security control with no shipping date behind it. An adoption survey's headline figure said little about whether an organisation had changed. Even V.E.R.A.'s own process confirmed figures already on file, in better form, because confirming a claim true is a different question from checking whether it was already known. On this week's evidence, across governance, engineering, software and research practice, the organisations that held up checked the record rather than the label.
This week's Saturday piece, on how a confirmed fact can still be stale, is worth five minutes before any team calls a clean check new.Read the full analysis
Cybersecurity Governance: The Expectations That Created Nothing
Two regulators called their 15 October statement confirmation, not news. Reporting and outsourcing already bind; the standard making vendor risk enforceable stays in consultation until 2027. The test is the paperwork, not the statement.
Orbital Manufacturing: The Dome That Did Not Meet the Standard
Rocket Lab delayed Neutron a year rather than fly a dome it could not verify. The regulator enforcing satellite deadlines missed its own: the slow clock belonged to the checker, not the checked.
Ninety-One Per Cent Adopted, Four Per Cent Changed
New Zealand AI adoption hit 91 per cent while core-operations transformation fell to 4. Resistance ranks nearly as high as capability gaps, and nobody has written the stopping rule that would catch a failing pilot.
The Distribution Shipped a Kernel That Did Not Exist Yet
Ubuntu 26.10 shipped Linux kernel 7.3 three days before it was finished, a release candidate dressed as a release. A distribution's calendar and a kernel maintainer's judgement are different authorities that usually agree.
Zero Trust for AI Agents: The Vendor Named the Control and Shipped No Date
Microsoft named three AI-agent controls on 19 October with no release date, licence or Learn page: a sentence in a blog post, not a line in code.
You Do Not Control the Substrate
Open licensing let four governments build their own RISC-V roadmap, but none can fork a fab the way code forks. ARM withdrew Huawei's access in 2019; at the hardware layer, governance is the only lever left.
AI Verification: We Verified It, and We Already Had It
Three figures checked out true this week; two were already in this project's file, in sharper form. A regulator's release rounded 91 per cent to 90, the file held the precise figure instead.
Before your board treats a vendor announcement, a regulator statement, or an adoption figure as settled, has anyone checked the primary document behind it?

