Singapore counsel are increasingly using AI to draft 2-page board memos on the scope of the amendment, generate client-facing summaries of MAS Notice 637 changes effective 31 December 2025, prepare partner-level briefings on capital-treatment cross-references, and validate group-structure language against the Reporting Bank perimeter on the face of the Notice.
In Singapore-incorporated banks and financial holding companies the workflow shape is now consistent: a frontier AI assistant produces a clean first draft on MAS Notice 637 risk-based capital adequacy for Reporting Banks, and the reviewer is asked to spot-check the cited MAS instruments and drafting-convention claims against the regulator-issued source before the deliverable goes out. The two AI failures recorded by the RLB Specialist Panel sit precisely at that spot-check boundary.
Two frontier AI models tested by the RLB Specialist Panel on MAS Notice 637 (Amendment) 2025 produced FABRICATED_FACT errors against the regulator-issued source held as primary substrate. The first invented a sibling "Notice FHC-N637" for financial holding companies that does not appear on the MAS Notices and Directives register; the actual FHC capital framework is a separate MAS notice issued under the Financial Holding Companies Act.
The second misread the yellow-highlight convention in the MAS Notice 637 amendment PDF as visual emphasis, when the regulator's cover note states the yellow is annotation describing the change and will not appear in the published untracked Notice. Both findings sit in the same failure class: Source-Credit Fabrication, where the AI produces a confident, lawyer-shaped citation that does not exist or contradicts a regulator-stated convention. Neither AI subject hedged, flagged low confidence, or refused.
Both produced clean, deployable prose with the wrong substantive content, which is the version of AI failure that is hardest for a reviewer to catch on a fast-moving deliverable. 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, and records the AI subject, the question class, and the operational consequence for each affected audience.
For Singapore counsel the operational consequence is concrete. A legal opinion that cites the fabricated FHC notice number would not survive a single round of regulatory diligence, because the MAS Notices and Directives register does not list any such instrument. A memo that treats the amendment yellow highlight as substantive new Notice text would mischaracterise drafting-aid annotation as enforceable rule content. Both errors expose the client to a written advice product that the regulator and opposing counsel can dismantle on the face of the source.
The RLB Specialist Panel records each error against the underlying regulator-issued text and names the AI subject for audit transparency. The two findings carry Citation IDs RLB-H-SG-MAS-NOTICE-637-CAPITAL-ADEQUACY-BANKS-2025-Q010-Opus47 and RLB-H-SG-MAS-NOTICE-637-CAPITAL-ADEQUACY-BANKS-2025-Q012-Opus47; Claude Opus 4.7 is the AI subject in both events and the source-text excerpts are quoted verbatim in the briefing body that follows.
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 Singapore counsel, the practical exposure here is precise: Opus 4.7 invented a non-existent MAS instrument, "Notice FHC-N637", in response to a holding-company question, while the actual MAS Notice 637 applies, by its own paragraph 1.1, to Reporting Banks only. A memo citing the fabricated FHC notice would not survive a single round of regulatory diligence; on rebuttal, opposing counsel or the supervisor would point to the absence of any such notice on the MAS Notices and Directives register.
Lawyers advising on group-level capital obligations for Singapore FHCs must work from the Financial Holding Companies Act and MAS's separate FHC framework, not from any AI-asserted Notice number. Verbatim source verification of every notice reference is the minimum standard when AI-drafted text is incorporated into a legal opinion.
The yellow-highlight finding is squarely a question of how to read MAS's amendment-publication convention, an area where counsel is routinely asked to advise on what the amendment text legally becomes on commencement. Opus 4.7 reads the yellow as visual emphasis, when the MAS amendment package itself states, in its prefatory note, that yellow-highlighted text is annotation describing the change and will not appear in the published untracked Notice. A legal opinion built on the AI reading would mischaracterise drafting-aid annotation as substantive Notice text.
The drafting convention is a regulator-stated rule on the face of the PDF; lawyers should treat the annotation marker as authoritative and disregard any AI gloss that contradicts it.
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.