Where this goes wrong

A weak answer is rarely a wrong one. It is usually a true statement doing less work than it appears to — a policy that exists but binds nobody, an artefact produced once and never since, a judgement recorded without the person who made it or the basis they made it on. Each entry below names the specific failure for its provision; the obligation page it links to sets out what discharges the duty instead.

The answer that does not hold

• AI Model Risk Management §5.3Observations from a Thematic Review

  A rating produced once, at the point of approval, and never asked to earn its place. The method is documented, the scores are complete, and every system in the estate was assessed on the day it was proposed. Nothing has been re-scored since, no measure has been revisited, and the bands map to nothing an assessor can inspect: the same validation and the same monitoring apply whichever band a system falls in. It reads as a control and behaves as an intake form, and the give-away is that no rating has ever changed anything about how a system is run.

• AI Model Risk Management §6.4Observations from a Thematic Review

  A validation function that has never stopped anything. The reports are thorough, the templates complete, the coverage against the model inventory total, and every one of them concludes that the model is fit for its intended use subject to recommendations. Asked when a finding last held up a release, the firm cannot name an occasion; asked what would happen if one did, it describes an escalation route nobody has used. Challenge that has never been exercised is indistinguishable, from outside, from challenge that could not be.

• MAS Notice 658, paragraphs 2 to 4Management of Outsourced Relevant Services for Banks

  The register that lists the cloud and not the service running on it. A bank shows a complete, promptly updated filing in which the hyperscaler appears with a material rating and a thorough exit plan, while the model services consumed through that platform appear nowhere — procurement treated them as consumption inside an arrangement already registered. Each is separately obtained, separately terminable and separately capable of failing on its own, and the definitions attach to the service rather than to the invoice it happens to arrive on.

• MAS Notice FSM-N05, paragraphs 4 to 6Notice on Technology Risk Management

  The model inventory offered in answer to a critical-systems question. The bank produces a well-kept list of every model in production, with owners and risk ratings, and observes that none of them is classified critical. Both statements are true, and neither addresses paragraph 4, which asks what the bank’s critical systems are and what sits inside them. The classification travels the other way — from the consequence of a failure to the components inside its boundary. A model that is nobody’s critical system can still be the thing whose failure takes one down.

• Notice FSM-N05, paragraph 9Notice on Technology Risk Management

  The vendor’s security page offered as the control. A firm asks whether customer data is safe with the model provider, receives a well-produced answer about encryption in transit and at rest, certification and a training opt-out, and files it. Every statement in it may be true and none of it addresses the paragraph. The duty runs to the bank, over the information wherever it now sits — including inside artefacts the bank itself created, the index it built and the logging it switched on, none of which the provider’s assurance was written about.

• SAFR v1.0Safeguards for Agentic Finance at Runtime

  The paper cited as the standard the firm is aligned to. A steering pack says the agentic programme follows MAS’ agentic finance framework; the phrase survives into a board minute and then into a supervisory conversation, where it will not hold — the document says of itself that it is neither guidance nor an expectation, so alignment with it discharges nothing. The quieter version is worse: an architecture drawn accurately in slides, with the disposition engine present as a box and absent from the code path that actually releases money.