Singapore-incorporated bank and FHC company secretaries are increasingly using AI to summarise the MAS Notice 637 amendment scope for the board, draft commencement-date alerts to the audit committee, update the corporate compliance register with the applicable instruments for a bank or financial holding company, and prepare the regulatory-update appendix in the annual report.
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-incorporated bank and FHC company secretaries the operational consequence is concrete. A board pack that names a fabricated MAS instrument would propagate the error into the minutes, the corporate compliance register, and external auditor working papers. A compliance-register entry that treats amendment yellow-highlight text as substantive Notice content would create a permanent record divergence between the bank's documentation and the published Notice. Both errors are visible to any reviewer who checks the MAS 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.
Company secretaries at Singapore-incorporated financial holding companies routinely receive board papers referencing capital-adequacy compliance. The Opus 4.7 fabrication of "Notice FHC-N637" is dangerous in this setting because a board minute or risk-management report citing the non-existent notice could be carried forward into corporate records and external auditor packs. The secretary's responsibility is to confirm that any regulatory instrument named in board documents actually exists and applies to the entity; this requires checking the MAS Notices and Directives register before circulating drafts. If AI-drafted board content is being used, the verification step is non-negotiable.
Amendment-tracking and version control of regulatory notices is a standard company-secretarial task, and the yellow-highlight question is precisely the kind of detail a secretary is expected to read correctly when summarising changes for the board. Opus 4.7's claim that the yellow markup is visual emphasis would lead the secretary to record amendment-annotation text as if it were substantive Notice content, polluting the corporate record. The MAS PDF itself states the yellow is annotation that will not appear in the untracked Notice; this is the controlling fact.
Company secretaries should establish a working rule: annotation markers on a regulator's amendment package take precedence over any AI characterisation of them.
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.