Retail-bank in-house counsel reads CPMI material against a narrow set of legal artefacts: the FPS scheme-membership agreement update, the remittance-partner change-of-law clause, the consumer-disclosure schedule for cross-border products, and the board pack on cross-border roadmap exposure. 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 team that copies either output into a contractual clause assigns obligation the regulator did not assign.
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 carries 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. Quoted into a scheme-membership update or a remittance-partner change-of-law clause, the denial creates avoidable misalignment with the counterparty's roadmap.
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 retail-bank integration-agreement scope schedule drafted off that taxonomy misallocates obligation between the bank and the FPS scheme.
Citation: RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q008-Opus47.
When this hits the legal calendar
Counsel touches CPMI material on three artefacts: the FPS scheme-membership agreement, the remittance-partner change-of-law clause, and the board cross-border roadmap brief.
| Standing artefact | Where the AI risk surfaces | Failure mode |
|---|---|---|
| FPS scheme-membership agreement | Stakeholder-obligation mapping | Finding 2 |
| Remittance-partner change-of-law clause | Pilot-partner naming | Finding 1 |
| Board cross-border roadmap brief | Both | Both |
Aggregate impact on the team
The two failures together corrupt the obligation-mapping that the rest of the legal pack depends on; the integrity cost is borne at counterparty-challenge time.
| 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 contractual clause.
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. Retail-bank legal can wire the catalogue into the AI-draft review checkpoint so these two failure shapes are caught before they enter a contractual document.