Enumeration Collapse on a CFTC margin rule: two frontier AI models rewrote the Regulation 1.44 currency deadline tiers, and a hedge fund operations system configured against either output would generate the wrong deadline expectations on every multi-currency margin call routed through an FCM counterparty.

System-level parameter errors are the operational risk class hardest to roll back once propagated: they enter transaction records and reconciliation outputs before any review fires.

The pattern in one line

Frontier AI models, asked for an operational map of CFTC Regulation 1.44's currency deadline tiers, returned two structurally wrong outputs: one collapsed three regulatory tiers into two, the other added a noon Eastern Time cutoff that does not exist in the rule. A hedge fund margin processing system, deadline reference card, or operations procedure built from either output would carry that error into every multi-currency margin call the fund processes against its FCM counterparties.

How the RLB Specialist Panel tested this

Questions are prepared by the RLB Specialist Panel based on real practical AI usage in the workflows the respective audience uses AI for. For Regulation 1.44, the Panel set an operations-facing brief: prepare a guidance note for a margin team configuring system parameters for Regulation 1.44 separate account compliance, specifying which currencies require same-day margin collection, which receive extended deadlines, and the exact timing requirements for each currency category.

Two frontier AI subjects answered the brief with web search enabled, mirroring how operations and treasury teams at hedge funds actually use AI assistants on a finalised rule when setting up a new counterparty or onboarding a new currency pair. The Panel binds each AI finding to verbatim regulator-issued source text held as primary substrate, in this case the eCFR text of 17 CFR Section 1.44 as of June 2026.

What the models got wrong

Claude Opus 4.7, with web search active, wrote: "For margin called in a fiat currency other than USD, the deadline may be extended by up to one additional business day... T+1 should be the default presumption... For all other non-USD currencies, default to same-day (T)." The structural error has two arms. The ten currencies enumerated in Appendix A (AUD, CNY, HKD, HUF, ILS, JPY, NZD, SGD, ZAR, TRY) were assigned T+1. Section 1.44(f)(2) sets T+2, "the end of the second business day after the day on which the margin call is issued." Every remaining non-USD, non-Canadian-dollar currency was assigned same-day.

Section 1.44(f)(3) grants T+1, end of the business day after the day on which the call was issued. Three regulatory tiers compressed into two. Citation ID RLB-H-US-CFTC-FCM-MARGIN-ADEQUACY-SEPARATE-ACCOUNTS-REG-1-44-Q001-Opus47 carries the full audit trail.

Claude Sonnet 4.6, given the same brief, wrote: "TIER 1 EXTENSION, OTHER NON-USD/CAD FIAT CURRENCIES (T+1, 12:00 p.m. ET) Deadline: 12:00 p.m. ET on the FIRST U.S. business day after the business day on which the margin call was issued." Section 1.44(f)(3) sets no intraday cutoff. The verbatim text reads "no later than the end of the business day after the day on which the margin call is issued." The "12:00 p.m. ET" figure does not appear in the rule or in Appendix A. Citation ID RLB-H-US-CFTC-FCM-MARGIN-ADEQUACY-SEPARATE-ACCOUNTS-REG-1-44-Q001-Sonnet46 carries the full audit trail.

Why this matters for hedge fund operations teams

System parameters are the exposure point. A margin processing system configured against the Opus 4.7 reconstruction will set Appendix A deadline checks at T+1 close-of-business. Every margin call the FCM places on an Appendix A currency, JPY, AUD, HKD, SGD, that is settled on T+2, the regulation's actual deadline, will be flagged by the system as a breach. The fund's operations review pack will surface false positives on every Appendix A call. Counterparty disputes will be raised against the FCM on the basis of a documented internal monitoring threshold that does not reflect the rule.

Treasury staff will reconcile to the wrong calendar. The fund's COO will see a high-rate breach signal that resolves to no actual breach. The reverse risk is also live. The same Opus 4.7 output assigned same-day to currencies the rule grants T+1, EUR, GBP, CHF among them; an operations system applying same-day urgency to those currencies will treat in-compliance T+1 receipts as late and document the firm's monitoring of the FCM at a standard the regulation has not set. The Sonnet 4.6 noon cutoff layered onto the T+1 tier behaves the same way at intraday granularity, treating 3:00 p.m.

ET receipts as late on a tier the regulation evaluates at end of business.

The regulator's actual position

Section 1.44(f) sets three tiers. Tier 1, U.S. and Canadian dollars, close of the Fedwire Funds Service on the same business day the margin call is issued. Tier 2, the ten currencies listed in Appendix A, end of the second business day after the day on which the margin call is issued (T+2). Tier 3, all other fiat currencies, end of the business day after the day on which the margin call is issued (T+1). No intraday cutoff appears in any of the three tiers. The Tier 2 membership list is regulator-defined.

What this tells us about AI for hedge fund operations teams

The taxonomy lens is Enumeration Collapse: the substitution of a plausible structure for the regulation's actual enumeration, presented as desk-usable guidance with no hedging or surface signal that a substitution has occurred. Operations workflows compound the risk. A documentation error in a 2-page client memo is correctable on review. A parameter error written into a margin processing system is propagated through every margin call the system handles between configuration and detection.

The detection lag, the time between the wrong parameter going live and an operator catching the false-positive pattern, is the period during which the operational record diverges from the regulatory record. For hedge fund operations teams, the verification requirement is structural and pre-deployment: AI-generated regulatory parameters must be checked against the primary text before they enter the system, not after.

What the RLB Specialist Panel is doing about it

The RLB Specialist Panel documents both findings under the immutable citation IDs above and binds each to the verbatim Section 1.44(f) text it contradicts. The Panel records the failure mode classifications (outdated for the Opus 4.7 finding, inference_drift for the Sonnet 4.6 finding) against the eCFR primary substrate document, and sets out the methodology categories so operations teams and AI labs can identify Enumeration Collapse in their own workflows.

Partnership inquiries from hedge fund operations groups that want to test their own AI-assisted parameter configuration against the same probe family, and from AI labs that want to test their models against the same operations-facing brief, are received at the Specialist Panel level.

What hedge fund operations teams should do

Pre-deployment and reconciliation-side actions, in order of operational impact:

• Verify every AI-assisted Regulation 1.44 parameter, currency tier assignment, deadline cutoff, monitoring threshold, against 17 CFR Section 1.44(f) and Appendix A directly before the parameter is committed to a system.
• Flag intraday Eastern Time cutoffs in any AI output on the T+1 tier as a diagnostic. No such cutoff appears in the rule; its presence is a verification trigger.
• Name-check every currency in an AI-generated Tier 2 list against the Appendix A enumeration. Tier 2 membership is regulator-defined, not derivable.
• Inventory all margin processing system parameters that touch Regulation 1.44 timing and confirm the source the parameter was set from. Where the source was AI-assisted output, re-verify against the primary text.
• Re-run the most recent operations review pack against the verified Section 1.44(f) tiers. Where the pack flagged Appendix A T+2 receipts as breaches, the breaches were false positives; the operations record requires correction and the FCM-side dispute log requires withdrawal.
• For new counterparty or new currency-pair onboarding, route AI-assisted parameter recommendations through a primary-text verification step before configuration, and log the verification in the operations control file.
• Where the firm uses AI-generated deadline reference cards for treasury staff, version and re-issue each card after primary-text verification.

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: 17 CFR § 1.44, Risk-based Capital Requirements and Margin Adequacy for Separate Accounts · Substrate documents: R2-REGULATION-17CFR_1_44_eCFR_asof_2026-06-04.pdf · eCFR: ecfr.gov · CFTC: cftc.gov

Citation IDs referenced:

• RLB-H-US-CFTC-FCM-MARGIN-ADEQUACY-SEPARATE-ACCOUNTS-REG-1-44-Q001-Opus47