Compliance teams at Singapore investment-banking divisions are increasingly using AI to update the investment-banking regulatory-perimeter map for MAS Notice 637, draft deal-clearance regulatory-impact memoranda referencing the FHC framework, generate compliance-training summaries on the 31 December 2025 amendment, and prepare supervisor-facing position papers on group-capital obligations. 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 Compliance teams at Singapore investment-banking divisions the operational consequence is concrete. An IB deal-clearance memo that cites a fabricated MAS instrument would enter transaction documentation and surface on external diligence. A regulator-facing position paper that treats amendment annotation as substantive Notice text would mischaracterise the rule estate to MAS. Both errors are direct enforcement-risk events tied to AI output that was not bound to the regulator's 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.
Investment-banking compliance teams at Singapore-incorporated banks operate within the MAS Notice 637 framework for capital adequacy and against the FHC framework where the IB sits inside a financial-holding structure. Opus 4.7's fabrication of "Notice FHC-N637" is particularly damaging in IB compliance because deal-specific regulatory-impact memos routinely name MAS instruments, and a fabricated reference could enter transaction documentation. Compliance must verify every MAS instrument reference against the Notices and Directives register; the FHC framework is MAS's separate notice under the Financial Holding Companies Act.
Investment-banking compliance teams reviewing the MAS Notice 637 amendment package to update the IB regulatory-framework map and deal-clearance protocols need to identify the text that legally enters the consolidated Notice. Opus 4.7's reading of the yellow as visual emphasis would cause IB compliance to encode annotation text into deal-clearance criteria and product approval workflows, producing a mismatch against the regulator's actual published Notice. The cover-note convention controls; IB compliance documentation should follow 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.