Corrections

17 August 2026, currency and evidence review

A second review, this time of whether what the site says is still true rather than whether it was ever true, found one class of error running through most of the site and a second, smaller class of invented evidence. Both are recorded here in full.

The regulatory calendar was out of date everywhere. The EU AI Omnibus entered into force on 27 July 2026 and moved the high-risk obligations under Regulation (EU) 2024/1689 to 2 December 2027 for Annex III systems and 2 August 2028 for Annex I systems embedded in physical products. Until today this site said otherwise in several places.

• The site wide banner, present on every page, read that the Omnibus was at trilogue on 28 April 2026 and that the deadline "may shift". It was labelled Live. It now states the position as it stands, with the dates.
• Nineteen editor's update and regulatory note panels described the Omnibus as a proposal that had not been adopted, several of them stating that the 2 August 2026 date "remains legally binding". Every one has been rewritten and dated to today.
• The article published on 3 August 2026 under the headline "What certification evidence deployers need now that enforcement is live" was built on the premise that the Omnibus deferral had failed to arrive in time and that the original 2 August 2026 date had governed. That premise was wrong on the day it was published, six days after the Omnibus entered into force. The article's substance, the five elements of the Article 26 operator file and how they relate to certification, was correct and has been kept. Its framing, headline, standfirst, key takeaways, FAQ answers and references have been rewritten. It is now titled "What evidence an EU AI Act deployer needs to hold in 2026" and states the current dates. The URL has not changed, so anyone who bookmarked or cited the old page lands on the corrected one.
• Four further articles stated that high-risk or conformity assessment obligations applied from 2 August 2026 without qualification. All four now carry the current dates. Statements that Article 50 transparency obligations apply from 2 August 2026 were checked and kept, because the Omnibus did not move them.
• A deadline was published two months later than it falls. The Article 50(2) transition, which lets systems already on the market before 2 August 2026 delay only the machine-readable marking of AI generated content, was given across this network as ending 2 February 2027. That was the European Commission's proposed six months reported as though it were law. The transition ends 2 December 2026. Anyone who planned marking work against February has two months less than they were told. This site described the transition without a date; it now carries the correct one on both pages that discuss it.

Claims about a body of assessments that does not exist were removed. No organisation has been assessed or certified under the Agent Certified methodology to date. Four passages implied otherwise and have been corrected.

• "In assessments conducted against the Agent Certified framework, prompt injection vulnerabilities are the most frequently identified high-severity finding" was removed. There are no such assessments. The passage now attributes the ranking to the OWASP Top 10 for Large Language Model Applications, where prompt injection is LLM01, which is the actual basis for the dimension's weighting.
• "Most AI agent deployments this framework has assessed did not enter the process with governance documentation" was removed and rewritten as an assumption the framework makes rather than an observation it has recorded.
• "Reviewers routinely cite Elite agents as reference profiles when producing sector guidance" and "Used as a reference profile for insurer underwriting models" were removed. No agent has been assessed at the Elite tier, and no insurer uses this framework as an underwriting input. The comparison table entry "Priceable risk for insurers" was removed for the same reason.
• Two statements that an assessment takes a given number of weeks "for most operators" were rewritten as the scoped duration of the process, because there is no population of operators to average.

A third party was described more strongly than its own record supports. The cost article cited "the EEOC's 365,000 US dollar 2023 settlement over a discriminatory AI hiring tool". The settlement is real: EEOC v iTutorGroup, 365,000 US dollars, announced 11 September 2023, more than 200 affected applicants. The EEOC's own announcement describes tutor application software programmed to reject female applicants aged 55 or older and male applicants aged 60 or older, and does not call the system AI. Every reference on this site now says what the EEOC says.

Two dates could not be confirmed at source and are now marked as such. The adoption of the Council of Europe Framework Convention on Artificial Intelligence in May 2024 and its opening for signature in Vilnius in September 2024 are stated on the Council of Europe's own published record, but coe.int, rm.coe.int and eur-lex.europa.eu all refused automated access during this review, so neither date was read against a retrieved document. Rather than remove the dates or quietly leave them, the article now carries a dated sourcing note saying exactly that, and warning that a search engine confirming the dates may be drawing on this page.

The carrier alignment language removed on 15 August was checked again across every page, every JSON-LD block, the sitemap and llms.txt. It is gone and has not returned.

15 August 2026, site wide factual review

A review of every published page removed statements about named insurers and reinsurers that could not be verified at the administering company's own domain. The changes were as follows.

• Statements that the Agent Certified assessment report is formatted to align with the supplemental AI questionnaires of named carriers were removed. The report follows the Agent Certified methodology and no insurer's questionnaire. Agent Certified has no arrangement with any insurer or reinsurer.
• Descriptions of specific policy terms, schedules, notification periods and coverage triggers attributed to named carriers were removed, because they could not be verified at source.
• Coverage limits and funding round details attributed to named carriers were removed for the same reason. The qualitative statements they sat inside were kept.
• Statements that named carriers give preferential pricing to operators assessed under this framework were removed. No carrier has adopted the Agent Certified methodology as an underwriting or pricing input.
• The full name of the Artificial Intelligence Underwriting Company was normalised across the site, and unverified dates attached to the first AIUC-1 backed policy were removed.
• References to Agent Certified as a registry were replaced with accurate wording. Agent Certified publishes a methodology and issues assessments; it is not a registry, an issuing authority, or a governing body.
• Brussels was removed as a location datum in page footers. Future Proof Intelligence has no Brussels presence.
• Two citations to European Insurance and Occupational Pensions Authority material were corrected to the Opinion on artificial intelligence governance and risk management published on 6 August 2025, replacing a placeholder document number.

15 August 2026, second pass on the AIUC name

A later review the same day found five further places where the acronym AIUC was expanded incorrectly, all of them in reference lists and footnotes rather than in body copy, which is why the first pass missed them.

• AI Underwriting Consortium, in the certification assessment guide, the recertification article and the methodology reference table, has been corrected to Artificial Intelligence Underwriting Company.
• AI Underwriting Code, in the dynamic behaviour audit article, has been corrected to the same. The citation in that entry pointed to aiuc.org, which is not the company's domain; it now points to aiuc.com.

A network-wide correction issued the same day removed the description of Munich Re aiSure as a parametric product, because Munich Re does not use that word for it. No page on this site made that claim, so nothing here changed. Where this site uses parametric it refers to the insurance model in general, which is ordinary industry vocabulary and remains accurate.