In-house counsel at statutory boards and payments-oversight agencies reads CPMI material against a tight set of legal artefacts: the legislative impact memo on a payments-act amendment, the inter-agency MOU on cross-border-payments coordination, and the legal opinion on the body's designated-FMI perimeter. Two AI failures on this regulation hit those artefacts directly. Opus 4.7 denied the SARB pre-validation partnership documented in CPMI Brief No. 9, and Opus 4.7 returned a per-recommendation stakeholder taxonomy reconstructed from category labels rather than the d224 recommendation text. A legal memo built on either AI output denies a documented regulator workstream or misallocates domestic legal action.
What the AI got wrong, and why it matters here
Both failures sit on the artefacts in-house counsel produces from cold-read CPMI material: a partner-naming denial and a fabricated obligation taxonomy. Neither has a retrieval-gap signal.
Finding 1: SARB pre-validation partnership denied
Opus 4.7 denied any public CPMI statement names SARB as the pre-validation pilot partner. CPMI Brief No. 9 (November 2025) names SARB outright. A legislative impact memo or inter-agency MOU draft that relies on the AI denial misrepresents a documented regulator workstream in a document the counterpart agency will read in print.
Citation: RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q007-Opus47.
Finding 2: Invented per-recommendation stakeholder taxonomy
Opus 4.7 returned a clean stakeholder taxonomy across d224's 10 recommendations, built from category labels rather than the recommendation text. A legislative impact memo built on that taxonomy misallocates legal action between the statutory body and other parts of the domestic regulatory perimeter.
Citation: RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q008-Opus47.
When this hits the legal calendar
Statutory-body counsel touches CPMI material on three artefacts: the legislative impact memo on the payments-act amendment, the inter-agency MOU on cross-border-payments coordination, and the legal opinion on the body's designated-FMI perimeter.
| Standing artefact | Where the AI risk surfaces | Failure mode |
|---|---|---|
| Legislative impact memo on the payments-act amendment | Stakeholder-obligation mapping | Finding 2 |
| Inter-agency MOU on cross-border-payments coordination | Pilot-partner naming | Finding 1 |
| Legal opinion on the body's designated-FMI perimeter | Both | Both |
Aggregate impact on the team
The two failures corrupt both the partner-naming line and the obligation-mapping that the rest of the legal pack depends on; the integrity cost is borne at inter-agency review.
| Risk Impact | Count | Affected findings |
|---|---|---|
| 0 | ||
| 0 |
What this team should do
Treat AI partner-naming and AI stakeholder-obligation tables as draft material requiring verification against the relevant CPMI brief by number and the d224 recommendation text before they enter a legislative impact memo or inter-agency MOU.
Detection patterns to add to AI-review
- Pilot-partner statements must trace to a numbered CPMI brief.
- Stakeholder taxonomies on d224 must be verified against the recommendation text.
How RLB can help
RLB tracks AI failures on d224 and the CPMI brief series and refreshes the catalogue against live AI subjects on rotation. Statutory-board counsel can wire the catalogue into the legal-deliverable review step so these two failure shapes are caught before they enter a legislative memo or MOU draft.