AI mis-frames CPMI-IOSCO d226 effective practices as supervisory or mandatory obligations when the report itself describes them as non-binding examples of how PFMI standards can be met.
Executive Summary
Compliance teams at hedge funds clearing derivatives through central counterparties are increasingly using AI to draft regulatory monitoring updates citing CPMI-IOSCO d226, prepare board compliance committee briefings on VM operational expectations, classify the January 2025 publication in the firm's horizon-scanning log, and validate proposed updates to client-clearing onboarding language for institutional investors. Leading AI assistants tested by the RLB Specialist Panel produced confident, citable answers on the binding force of d226 that the document itself directly contradicts.
This cell collects one hallucination finding on the January 2025 CPMI-IOSCO publication "Streamlining variation margin in centrally cleared markets, examples of effective practices" (d226), organised for Hedge fund Compliance working on CPMI-IOSCO VM matters in international and cross-border contexts. Across the finding, the AI subject in this audit produced a confident, citable response on the legal status of the eight effective practices in d226 that the document itself directly contradicts.
The Specialist Panel found that the AI classified each practice as a supervisory expectation or as carrying mandatory overlap with national rules, when the document's own stated purpose paragraph records it as "examples of how standards set out in the CPMI-IOSCO Principles for financial market infrastructures, as supplemented by the relevant guidance, can be met." Every finding in this cell is bound to verbatim regulator-issued source text held as primary substrate by the RLB Specialist Panel.
When this affects Hedge fund Compliance work
This pattern surfaces whenever Hedge fund Compliance use AI to characterise the binding force of d226 in regulatory monitoring updates, compliance committee briefings, and horizon-scanning logs. The risk is structural: d226 is a CPMI-IOSCO publication that frames itself as voluntary effective-practice illustration, yet the AI's commitment reads as a supervisory or mandatory classification that a practitioner would paste into a deliverable before verification against the source. The deliverable then carries forward an inverted modality on binding force into downstream work products.
Findings overview
| # | Finding title | Type | Citation ID |
|---|---|---|---|
| 1 | Inverted modality on binding force | Misstated rule | RLB-H-INT-BIS-CPMI-CPMI-IOSCO-VARIATION-MARGIN-CCPs-2025-Q004-Opus47 |
What the AI got wrong
Finding 1: Inverted modality on binding force of d226 effective practices
Citation ID: RLB-H-INT-BIS-CPMI-CPMI-IOSCO-VARIATION-MARGIN-CCPs-2025-Q004-Opus47
In response to a Specialist Panel application-style question asking for a compliance obligations memo classifying each of the eight effective practices in d226 as either (A) MANDATORY REQUIREMENT, (B) SUPERVISORY EXPECTATION, or (C) VOLUNTARY GUIDANCE, the AI subject produced a complete memo that treated every one of the eight effective practices as either a supervisory expectation in its own right or as overlapping with mandatory national rules.
The memo opened with a threshold classification that placed d226 in category (C) but immediately added "a strong gravitational pull into (B) SUPERVISORY EXPECTATION because the underlying PFMIs are the de facto binding standard against which CCPs are supervised," then classified each practice individually under (B), (B) trending (C), (B) with (A) elements, or similar mixed labels.
The document's own stated purpose paragraph, by contrast, records that d226 sets out "examples of how standards set out in the CPMI-IOSCO Principles for financial market infrastructures, as supplemented by the relevant guidance, can be met." The text is illustrative of one way the underlying PFMI standards can be met, and is not a new layer of supervisory expectation or mandatory rule. The AI subject's framing inverts that modality: it converts a voluntary illustration into a baseline supervisory expectation, with each practice acquiring its own binding-force overlay.
The Specialist Panel records this as a misstated-rule finding because the AI's commitment on the legal status of d226 contradicts the document's own characterisation of itself. The full finding analysis, including the verbatim regulator text, the AI subject's complete answer, and the AI's failure mode classification, is at See full finding analysis.
Horizon-scanning entries and compliance committee briefings that characterise d226 as a binding regulator obligation trigger remediation workstreams sized against a voluntary publication, distort the compliance function's prioritisation of regulatory-change resource, and create inconsistencies between the fund manager's d226 position and the binding national-rule position that supervisors will actually examine.
AI's failure mode
| # | Finding title | Type | Citation ID |
|---|---|---|---|
| 1 | Inverted modality on binding force | Misstated rule | RLB-H-INT-BIS-CPMI-CPMI-IOSCO-VARIATION-MARGIN-CCPs-2025-Q004-Opus47 |
Risk impact
| # | Finding title | Type | Citation ID |
|---|---|---|---|
| 1 | Inverted modality on binding force | Misstated rule | RLB-H-INT-BIS-CPMI-CPMI-IOSCO-VARIATION-MARGIN-CCPs-2025-Q004-Opus47 |
What Hedge fund Compliance teams should do
- Classify d226 in the firm's horizon-scanning log as a CPMI-IOSCO voluntary publication of effective practices, with a separate line for the underlying PFMI Principles as applied by the relevant national supervisor.
- Before circulating a compliance committee briefing that cites d226, verify the document's own framing as "examples of how standards … can be met" so the briefing does not overstate the binding force of the source.
- Where AI-generated regulatory monitoring updates label d226 as supervisory or mandatory, return them to the regulatory-change desk for re-tagging.
- In client-clearing onboarding language for institutional investors, describe d226 using the document's own framing and rely on the binding national rule for any operational commitments.
- Coordinate the firm's d226 position with the risk function and external counsel so monitoring, committee, and disclosure language are aligned on binding force.
Right of Reply
These findings and associated work have been put up in public with a view of the greater good for the development of a safer AI ecosystem. Any party reading this or any finding on reglegbrief.com may contact us and have an unconditional right of reply; the Specialist Panel will publish any factual correction or contextual response alongside the original finding, with no editorial gatekeeping. Researchers, regulators, and compliance teams with questions on methodology or specific findings can reach the Specialist Panel via the same channel.
Source & Methodology Standards
RegLeg Brief is operated by Verdus Technologies Pte. Ltd. (UEN 201616982R), incorporated in Singapore. The RLB Specialist Panel, with an aggregate of over 60 years of public-policy and industry experience, documents only confirmed hallucination findings, under a methodology that requires a verbatim regulator excerpt for every documented claim. All findings, citation IDs, model outputs, regulator excerpts, and methodology notes are open-access.
Primary source verified: d226 — Streamlining variation margin in centrally cleared markets — examples of effective practices (January 2025). R-folder reference: R6-FINAL_REPORT-00001. BIS portal: bis.org/cpmi.
Citation IDs referenced:
RLB-H-INT-BIS-CPMI-CPMI-IOSCO-VARIATION-MARGIN-CCPs-2025-Q004-Opus47