Editorial Standards

Last updated: 24 September 2026

This page sets out the rules I hold this site to. It exists because I write about AI governance, and a site on that subject should be able to show its own controls: where claims come from, what the reader is being asked to take on trust, how the machines were used, and what happened when I got something wrong.

What gets published here

Everything on this site is my own analysis, drawn from twenty-five years of delivery work and the published research I cite. There is no sponsored content, no affiliate links, no paid placements and no guest posts. Frameworks are published as versioned references with a change history. Client work appears only as case studies the client has agreed to, with figures the client has confirmed; where a figure has not been confirmed, none is given.

How claims are sourced

Every empirical claim carries a source, listed in APA 7 form at the foot of the piece and linked to the publisher's own page rather than to a secondary write-up. Primary sources are preferred: the report itself, the regulator's text, the standard. Vendor and consultancy research is cited when it is the best available evidence, and is labelled as such.

Posts that rest on statistics carry an Evidence & Methodology box that grades each claim:

  • Measured. An observed result from a study, survey or audited dataset, with the sample described.
  • Forecast or Estimate. A projection or model output. Cited because it is influential, not because it is proven.
  • Adapted. A finding from one context applied to another, with the stretch made explicit.
  • My call. A judgement from practice. No external source is claimed for it.

Each box closes with the condition under which the argument would be wrong. A statistic that cannot be traced to a real, findable source is removed, not softened.

How AI is used in producing this site

I use AI tools in research, drafting and editing, under my direction, in the same way I advise clients to: as a fast assistant whose output is checked before it counts. The positions, frameworks, judgements and recommendations are mine. Every statistic, quotation and attribution is verified against its source by a person before publication, a rule tightened in August 2026 after AI-assisted drafts were found to have introduced citations that did not hold up. Those cases are in the corrections log below.

Hero and illustrative images are AI-generated unless captioned as photographs; project photographs are real unless the alt text says the image is representative. Testimonials are quoted verbatim from LinkedIn recommendations and link to the original. No testimonial, quotation, case-study figure or client name on this site was generated or embellished by a model.

The search box (the magnifier in the menu, or ⌘K) has two parts. Results come from an index of every public page, built each time the site is deployed and searched in your browser; each result is the page itself, with the matching sentence and a link to its section. Answers, when you press Ask, are written by Claude Haiku, Anthropic's model, from passages of this site retrieved for the question and nothing else. The instruction it runs under forbids adding facts from outside the passages, requires a numbered citation on every claim, and tells it to say when the site does not cover a question rather than fill the gap. The answer is a summary of what this site already says, with the sources listed under it; the pages themselves remain the record. Questions are logged so weak answers can be found and the index improved. Nothing that identifies the person asking is stored.

The Ask Terence panel on articles and tools offers a fixed set of questions about the page, each answered in advance: drafted with AI assistance from the page itself, checked against the page, and citing the sections it draws on, so choosing one generates nothing. A question typed into the panel is answered live by Claude Haiku under the same instruction, from this page's passages first and other pages only when the page does not cover it, and every answer is checked against the site's writing rules before it is shown. The label is a name for the assistant; the answers describe Terence's published position in the third person and are not messages from him. Listen reads an answer aloud with an ElevenLabs voice.

Independence

This is a personal site. The views, frameworks and publications here are my own analysis. They do not speak for Orion Five Engineering or any past employer or client, and they do not draw on the confidential information, data or proprietary methods of any of them.

Client reference letters are held for procurement teams on request and are not published, quoted or summarised here, at the clients' preference. Where a project page mentions such a letter, it says only that one exists.

Versions and deposited records

Frameworks, technical reports and reference architectures carry a version number, a first-published date and a last-revised date. Substantive changes produce a new version; the PDF deposited on Zenodo under each DOI is frozen, so a new version means a new deposit. The record on this site and the deposited file are kept byte-identical. Copy edits do not change the version.

Corrections

When a factual error is found, the page is corrected in place. Substantive corrections are noted on the page and recorded in the log below with the date and what changed. Trivial fixes (typos, formatting, broken links) are made without notice. To report an error, use the contact page; you will hear back within one business day, and if you are right the fix and the log entry will follow.

Corrections log

DateCorrectionWhere
2026-09-30The 56% coding-speed figure was still credited to McKinsey in the summary box and a slide description, after the 21 August correction fixed the body. Both now credit the Microsoft, GitHub and MIT controlled study./blog/vibe-coding-pragmatic-adoption-professional/
2026-09-30Tool pages brought into line with their own logic: the TRACE evaluator's Not Ready rule (any failed criterion, with Reversibility alone routed to Human-in-the-Loop), the board checklist's item count (23), the vendor scorecard's dimension count (nine), and the operations map's process count (16)./resources/
2026-09-24Stanford "Canaries in the Coal Mine" early-career employment decline corrected from 16% to 13%, the figure in the August 2025 paper, with the August 2026 update of about 19% noted./blog/entry-level-job-market-broke-opening-it-left-behind/
2026-09-24Stanford "Canaries in the Coal Mine" figure corrected from 16% to 13% (August 2025 paper), with the August 2026 update of about 19% noted, in the summary box, table, text and evidence table./blog/why-experience-alone-no-longer-guarantees-higher-pay/
2026-09-24Knight Capital loss corrected from US$440 million to more than US$460 million, the figure in the SEC's 2013 order./blog/9-ai-deployments-fail-what-do/
2026-09-24Lyell et al. (2017) figure of a 56.9% rise in prescribing errors does not appear in the paper. Replaced with the paper's reported results: incorrect decision support increased missed errors by 24.5% to 33.3%, and 51.7% to 65.8% of participants accepted false alerts (simulation, 120 medical students)./blog/ai-can-triage-it-cant-be-accountable/
2026-09-24A figure of 92% of AI-related breaches occurring at organisations without AI access controls is not in IBM's 2026 release and was removed. Replaced with the release's figures: more than 20% of organisations reported a breach targeting AI models or applications, with compromised APIs, apps and plug-ins and cloud misconfigurations each 27% of root causes./blog/ai-cyberdefense-why-it-matters-now/
2026-09-24IBM "92%" access-control figure removed (not in IBM's 2026 release) and replaced with the release's "more than 20%" figure. EU AI Act Article 14 oversight obligations were described as in force since 2 August 2026; Regulation (EU) 2026/1744 deferred them to 2 December 2027 (Annex III) and 2 August 2028 (Annex I)./blog/rogue-agents-containment-when-detection-fails/
2026-09-24Disclosure dates corrected: Hugging Face disclosed the incident on 16 July 2026, OpenAI published its account on 21 July, and Hugging Face its technical timeline on 27 July. The post had dated both disclosures 22 July./blog/openai-hugging-face-agent-hack-what-actually-happened/
2026-09-24MIT NANDA finding corrected from "more than 90% of employees" to workers at more than 90% of surveyed companies using personal AI tools./blog/shadow-ai-is-already-inside-your-organisation/
2026-09-24MIT NANDA shadow-AI finding corrected from "over 90% of employees" to workers at over 90% of companies./blog/beginners-guide-enterprise-ai-transformation/
2026-09-24The 72-hour breach-notification window was attributed to the EU AI Act and GDPR. It is a GDPR requirement (Article 33) only./blog/what-your-ai-vendor-contract-is-probably-missing/
2026-09-24Bank of Singapore tool name corrected from "Helios" to Source of Wealth Assistant (SOWA), and its markets from Singapore, Hong Kong and Dubai to Singapore and Hong Kong, per the bank's October 2025 release. Unsupported expansion plans removed; time saving restated as about an hour./blog/agentic-ai-most-common-use-cases-singapore/
2026-09-24Closing note said "the team I co-founded". Terence is Executive Director of Orion Five Engineering's AI Governance & Assurance Practice, not a co-founder; now "the team I lead"./blog/orchestrating-agents-new-job-agents-catching-up/
2026-09-24The OSI model was described as fifty years old. ISO first published it in 1984; now "forty years"./blog/layer-8-cognitive-programming-enterprise-ai/
2026-09-24The OSI model was described as fifty years old. ISO first published it in 1984; now "forty years"./frameworks/layer8/
2026-09-24Unsourced claim that "85% of AI deployment failures" trace to one of five dimensions removed. The point is now made without a figure./frameworks/readiness/
2026-09-24IBM's US$4.45 million was described as the yearly cost of poor data governance; it is IBM's 2023 average cost of a data breach, and is now described that way. A McKinsey "2.5x" figure for unified data could not be traced to the cited survey and was removed./blog/data-fragmentation-before-ai-adoption/
2026-09-24McKinsey figures (78%, 71%, 33%, 5.5% high performers, and a "3.6x efficiency gap by 2027") did not match the November 2025 State of AI survey the post cites. Corrected to the survey: 88% use AI regularly, about one-third scaling, about 6% high performers; 3.6x is how much more likely high performers are to say they use AI for transformational change./blog/ai-implementation-paradox-poc-scaling-architectural-debt/
2026-09-24MIT NANDA's 67% versus 33% deployment gap was attributed to governance maturity, which the report does not say. Restated as the report's finding: purchased tools and external partnerships versus internal builds, self-reported, from interviews with 52 organisations./blog/why-most-ai-projects-fail-what-do/
2026-09-13Sultan Haitham City site area corrected to 1,570 hectares, matching the client letter on file./projects/, project page and résumé
2026-09-12AIGP credential issuer corrected to Singapore Management University. Earlier copy said IAPP, or "SMU via IAPP". The IAPP exam has not been taken.Credentials, résumé, footer chips, partner portal
2026-09-11Five posts corrected during the evidence-grading rollout: a GitClear figure that did not match its source, an unsourced closing-note statistic, a cited "SmartDev" study that could not be found and was removed, composite examples that read as real cases and are now labelled, an unverifiable Gartner pilot-failure rate, and a JPMorgan/Netflix case pairing that could not be substantiated. Three carousel decks carrying the same numbers were regenerated.Blog
2026-09-02Site-wide blog audit across 64 posts: a hallucination-rate figure matched to its real source, a mislabelled APA citation fixed, a PwC figure re-quoted correctly, unverifiable claims softened or removed, and the EU AI Act enforcement date corrected in three posts after confirming the postponement (originally written as August 2026).Blog
2026-08-21Six posts corrected after citation research: GitClear duplicate-code finding is 4x, not 8x; a coding-speed statistic credited to McKinsey belongs to Microsoft, GitHub and MIT; a cognitive-atrophy finding was wrongly credited to Harvard; three figures in the "wisdom gap" post (a Forrester ROI claim, a 23% measurement statistic, an MIT Sloan attribution) could not be verified and were removed; a PwC "creative self-destruction" citation could not be found and was removed; manufacturing ROI figures were re-read from the original report.Blog
2026-08-19Topic images on the speaking page contained AI-generated text with invented statistics. Replaced with images carrying no figures./speaking/
2026-08-07Cool N Lite Solar Film engagement end date corrected to 2025./about/, résumé PDF

Contact

Questions about these standards, or about a specific claim, go to Terence Kok via the contact page.

Terence Kok
Before You Go

Publishing my own corrections log felt uncomfortable the first time I wrote it out, which is roughly how I know it belongs here. I ask boards to show me their AI incident register before I believe their governance slides. It would be odd to hold a website about that discipline to a lower bar. If you find something wrong, tell me. It goes in the log, and the log is the point.

Terence Kok