Executive Summary
Legal teams at law firms advising swap dealer and MSP clients on the December 2025 CFTC final rule, and the January 2026 correction published days later, are operating in exactly the kind of fast-moving regulatory environment where AI research tools look most useful and are most dangerous. Across three questions put to AI tools on this regulation, every answer contained a material error.
The failures cluster around three discrete regulatory events: the inadvertent removal and restoration of Appendix A to Subpart H (the §§23.434 and 23.440 guidance that has been present since 2012), the geographic scope of CFTC Staff Letter 25-49 (UK trading venues, not US SEFs or DCMs), and the pre-trade mid-market mark elimination, where AI tools correctly noted the PTMMM provision was deleted in its entirety but wrongly extended that conclusion to swap types the provision never reached.
All three errors carry direct professional liability exposure when they migrate from an AI research session into a client memo, regulatory mapping, or transaction advice.
How AI gets this regulation wrong
The errors on this regulation divide into two patterns: AI tools that confidently presented a coherent but factually incorrect answer, grounded in the wrong source or a plausible inference from the broader framework, and only retracted when the specific error was surfaced; and AI tools that correctly identified a regulatory event but omitted the specific technical details that practitioners actually need to act on. Both patterns produce dangerous work product for different reasons: the first travels undetected because it sounds authoritative, the second misleads by leaving the client unable to verify what was actually changed.
| AI's Failure Mode | Count | Affected findings |
|---|---|---|
| Exposed Fabrication | 2 | Finding#2 · Finding#3 |
| Inference Drift | 1 | Finding#1 |
What that means for your team
Every failure in this cell carries professional liability exposure. This regulation governs swap dealer business conduct and documentation obligations at provision-level granularity, the kind of rule where advice that states the wrong scope, the wrong venue, or the wrong surviving obligation is not a minor inaccuracy but a material advice failure that can sit in a client's compliance program long after the memo is filed.
| Risk Impact | Count | Affected findings |
|---|---|---|
| Liability / PI exposure | 3 | Finding#1 · Finding#2 · Finding#3 |
When this affects your department
Legal teams at law firms most commonly encounter this regulation through three workflows: client alert and memo drafting as the December 2025 final rule was published and the January 2026 correction followed within weeks; cross-border product analysis when US swap dealer clients execute on UK venues and need clarity on how US conduct obligations interact with UK venue rules; and documentation review when clients restructure their §23.431 pre-trade disclosure processes following the PTMMM elimination.
In each context, a lawyer or paralegal may query an AI tool to get a fast read on what changed, which provision was affected, or how a specific staff letter applies to their client's activity profile.
The January 2026 correction created a particular risk window. In the days between the December 30 final rule publication and the January 28 correction, the CFR was in a state that did not reflect the Commission's intent, and any AI tool whose training or retrieval captured that interval without the correction could produce answers grounded in a version of the rule that no longer stands. Practitioners drafting during that window, or advising clients who had already read the uncorrected final rule, needed to know specifically what was restored and why.
An AI answer that correctly notes a correction was issued but cannot identify the affected appendix, the sections it governs, or its historical lineage leaves the practitioner unable to advise clients on whether their existing compliance documentation references the right guidance.
If an incorrect AI answer travels into a client alert, a transaction advice memo, or the underlying analysis for a client's compliance program, the firm is in the chain of causation for any downstream error. A client that structures its documentation or UK-venue execution arrangements based on an incorrect description of Staff Letter 25-49's scope, or that draws incorrect conclusions about the pre- and post-rule PTMMM baseline, may not discover the error until a CFTC examination or counterparty dispute surfaces it. At that point the firm's advice is in the record.
The findings at a glance
The three findings below span the final rule, the January 2026 correction, and a related staff letter, each representing a distinct way AI tools mischaracterized a specific, verifiable regulatory event on this regulation.
Aggregate impact
The errors in this cell are not random, they cluster around overlapping regulatory transitions: a final rule, a correction issued weeks later, and a staff letter released into the same regulatory moment. This is structurally the type of situation AI tools handle worst. Multiple documents addressing related but distinct issues, rapid sequential amendments, and jurisdiction-specific scope distinctions that cannot be inferred from the broader framework all combine to produce answers that are plausible but wrong.
An AI tool that has absorbed the general contours of Subpart H, the ITBC swap framework, and the PTMMM history will produce confident-sounding answers on each of these questions, but "confident-sounding" is not the same as correct at the provision level.
Two of the three failures share a specific and particularly dangerous structure: the AI produced an internally coherent answer grounded in the wrong instrument or premise, then retracted only when the specific error was surfaced. For legal work product, this is the high-risk pattern. An answer that sounds authoritative and is logically consistent with what practitioners know about the broader regulatory framework will not trigger a junior associate's skepticism.
It will be incorporated into the draft and reviewed by a partner who may have no independent basis to spot the specific factual error, because the question being researched (which venues does Staff Letter 25-49 cover? what was eliminated when PTMMM was deleted in its entirety?) is precisely the kind of narrow technical question that gets delegated to AI research precisely because it seems like a lookup rather than a judgment call.
The third failure, the omission of Appendix A's specific identity from an otherwise correct account of the January 2026 correction, presents a different risk profile. A memo that notes the correction was issued but does not identify what was corrected leaves the client unable to locate the restored guidance, verify whether their compliance documentation references it, or understand which conduct obligations (recommendations to counterparties and special entities under §§23.434 and 23.440) the appendix governs.
The incompleteness may not be apparent to a reader who does not already know the answer, which is precisely the category of reader who most needs the memo to be complete.
What your team should do
The default position for legal research on this regulation is primary source verification for any time-specific or scope-specific claim. The Federal Register publication of the December 2025 final rule, the January 28 correction notice, and CFTC Staff Letter 25-49 are all publicly available directly from the CFTC's website and short enough to read in full for targeted questions.
AI tools can usefully provide orientation, summarizing the structure of Subpart H, flagging which provisions changed at a headline level, or identifying where in the CFR the relevant sections sit, but the specific scope, venue, product, and appendix-level details that distinguish correct from incorrect advice require reading the source. This is not a judgment about AI competence in general; it is a recognition that this regulation, with its December-to-January amendment sequence and the concurrent staff letter, is structurally the type of instrument where AI retrieval and inference errors are most likely and most consequential.
For the PTMMM elimination specifically, the practical safeguard is to work from the CFR text as amended rather than from any secondary description of what was deleted. The provision's prior scope, uncleared swaps, FX forwards, and FX swaps, is not front-of-mind for practitioners focused on the deletion announcement, and the inference that "eliminated in its entirety" means the obligation now reaches further (or, inversely, that cleared swaps are now somehow exempt from something they were never subject to) is a logical error that reads as plausible.
Advice on the PTMMM baseline, both before and after the rule change, should state the prior scope explicitly so clients can locate themselves correctly on both sides of the effective date.
For cross-border work involving UK trading venues and Staff Letter 25-49, the venue-specific scope is the operative fact the letter was issued to clarify, and it should be sourced from the letter directly rather than inferred from the codified ITBC swap framework applicable to US SEFs and DCMs. The letter is available on cftc.gov.
Any memo or analysis advising a US swap dealer client on the treatment of ITBC swaps initiated on an Eligible UK Trading Venue should verify the letter's scope directly, the geographic distinction is the entire purpose of the instrument, and it is the first thing to confirm.
How RLB Can Help
RegLeg's published Hallucination Research gives your team a concrete pre-flight check before relying on AI output for regulatory advice. The findings are organized by regulation and failure mode, so when your associates or partners are using AI tools to draft client memos, check compliance positions, or surface relevant enforcement precedent, you can cross-reference which regulatory domains carry documented hallucination risk before that output reaches a client. That's a different discipline than a generic AI policy; it's regulation-specific, failure-mode-specific, and it runs on evidence rather than vendor assurances.
Where your practice has particular AI exposure, securities, derivatives, banking regulation, or any area where your clients are themselves regulated, we run bespoke regulator deep-dives that map your actual AI-assisted workflows against the failure modes we've catalogued for those regulatory bodies. The output is a ranked risk register scoped to Legal's function: which workflow steps carry the highest hallucination exposure, which regulatory texts are most commonly misrepresented by AI tools, and where existing review processes catch failures versus where they're likely to let them through.
For firms that have already drafted AI-use policies or are mid-revision, we offer a confidential review against RegLeg's full failure-mode catalogue, not a generic best-practices audit, but a gap analysis tied to specific documented failures. We also develop training material and CPD-aligned content your team can use internally: case-based modules built around real failure patterns that satisfy ethics and professional development requirements while giving your attorneys and legal staff the working vocabulary to interrogate AI output rather than just accept or reject it wholesale.