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.
The RLB Specialist Panel tested whether two frontier AI models could correctly characterise the legal status of d226, asking them to classify each of the eight effective practices set out in the document as either a mandatory requirement with enforcement consequences, a supervisory expectation that regulators will test against, or voluntary guidance with no binding legal force. The exercise targeted what the Panel calls inverted modality: AI commitments that flip the binding force of a source text from voluntary illustration to supervisory or mandatory rule.
The frontier model under test produced a complete compliance obligations memo that classified every one of the eight effective practices as either a supervisory expectation in its own right or as overlapping with mandatory national rules, with a threshold classification asserting that d226 carries "a strong gravitational pull into (B) SUPERVISORY EXPECTATION." 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."
For Hedge fund Compliance, the operational consequence is direct. 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. The pattern is also reproducible: it surfaces wherever a deliverable asks the model to commit to a legal characterisation of an international standard-setter publication, and it is not addressed by general-purpose prompting.
The RLB Specialist Panel records the finding under the misstated-rule failure category and binds it to verbatim regulator text drawn from the d226 final report held as primary substrate.
The full finding is recorded under Citation ID RLB-H-INT-BIS-CPMI-CPMI-IOSCO-VARIATION-MARGIN-CCPs-2025-Q004-Opus47. The regulation hub is at /regulators/j1/INT/BIS-CPMI-INT-001/CPMI-IOSCO-VARIATION-MARGIN-CCPs-2025/. Questions are prepared by the RLB Specialist Panel based on real practical AI usage in the workflows the respective audience uses AI for. The Panel binds each AI finding to verbatim regulator-issued source text held as primary substrate.
This is the consolidated view of findings. Click the Citation IDs or 'see details →' on any item for the full details for each finding.
For Hedge fund Compliance, the AI's stated answer reads as a verbatim quotation that a practitioner would paste into a deliverable before verification against the source. The document's own stated purpose paragraph records that d226 sets out "examples of how standards … can be met." The AI's commitment inverts that modality. 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.
Every finding on this page compares an AI subject's account of the rule against the regulator's verbatim text from the regulator's own portal. Both are linked. Each delta, its root causes, and impact analysis are documented and published with immutable Citation IDs.