Governance teams can use the tools to run governance: keep the inventory current from the systems that know what is deployed, map each use case to the documents that apply, draft the board report and the regulatory responses, and check policies against new rules as they land. It is a chained workflow over a stable corpus of rules and internal policy, with a person owning every document that leaves the team. The regulation tracker on this site is the kind of corpus it reads.
AI governance (general): The model may act within a defined envelope; people sample, monitor and can stop it. Several model calls orchestrated by your code, in a sequence or a graph you designed. Low stakes, reversible, internal. The model may act within a defined envelope, with sampling, monitoring and a kill switch instead of per-action review.
Which steps belong to a person, the model and a system?
| # | Step | Owner | Note |
|---|---|---|---|
| 1 | Maintain the inventory | A system | From deployment records and the model repository; structured fields. |
| 2 | Map use cases to rules | The model | Against the governed corpus of regulation and policy, with citations. |
| 3 | Draft board and regulator reporting | The model | From the inventory, the evals and the exception logs. |
| 4 | Check policy against new rules | The model | Gap analysis when a document changes status; proposals only. |
| 5 | Decide and sign | A person | The chief risk officer or equivalent owns what is sent. |
Which control layers carry the weight?
Each layer is described, with its controls and documents, on the control plane page.
- Governance and accountability: core for this design.
- Data and knowledge: core for this design.
Which rules and guidance does this design answer to?
| Document | Authority | Why it applies here | Status |
|---|---|---|---|
| SR 26-2 | Federal Reserve | Board and senior-management governance of models; the generative and agentic carve-out. | In force |
| NIST AI RMF 1.0 | NIST | Govern, Map, Measure, Manage: the voluntary frame most US banks cite. | In force |
| Treasury FS AI RMF and AI Lexicon (Feb 2026) | U.S. Treasury | The NIST framework adapted to financial services. | Final |
| FSB AI sound practices consultation (June 2026) | FSB | Twelve sound practices from strategy to third-party risk. | Proposed |
| Machado speech: 'Technology is neutral, governance is not' (Feb 2026) | ECB | Accountability, senior oversight, effective challenge. | Final |
| Regulation (EU) 2024/1689 | EU AI Act | The EU AI Act sets the strictest documentation floor. | In force |
| PRA SS1/23 | UK (BoE / PRA / FCA) | UK: the widest model perimeter. | In force |
| SR 23-4 | Federal Reserve | The model provider is a third party: due diligence, contract terms, monitoring, exit. | In force |
| FSB AI monitoring report (Oct 2025) | FSB | Concentration on a small number of model suppliers. | Final |
How will you know it works, before and after launch?
- A golden dataset of at least 50 real cases with expected outputs, including adversarial inputs: wrong documents, unusual formats, prompts that try to change the task.
- A judge model scoring against a written rubric (accuracy, completeness, tone, citation present), calibrated against a human-scored sample every month. Threshold set from the human sample, not guessed.
- Citation checks: every factual claim resolves to a passage in the governed set; unsupported claims below 2% of answers.
- Trace evals per step, not only end to end: which step fails, how often, at what cost, so a prompt or model change can be judged step by step.
- The same suite reruns on every prompt change, model version change and retrieval change; a regression blocks the release. That is what ongoing monitoring and outcomes analysis mean in model-risk terms.
Where must a person be in the loop?
- An action envelope: which tools, which systems, what value, what volume, what the model may never do.
- Sampled human review of outputs and a weekly look at the exception log.
- Turn and cost budgets, logged, with an automatic stop when exceeded.
- A kill switch that any owner can pull.
- An inventory the model believes rather than one the systems report.
- Board papers that assert control effectiveness without the evals to show it.
- Rules mapped from memory instead of from a dated corpus.
What will a validator or an examiner ask?
- Where is this system in your inventory, what tier did you assign, and who signed it off?
- What counts as a model here, and what does your validation cover for the parts that are not?
- Show me the data lineage behind the retrieval set and the training or tuning data.
- What can the system do without a person, and where is that written down?
- How do you know it is still working: which evals run, how often, and what happened the last time one failed?
- What did you do about the vendor: due diligence, contract, exit plan, concentration?
- Walk me through one wrong output from production and what the customer, if any, saw.
- Who can switch it off, and has that been tested?
What it does: runs the AI inventory, policy and reporting that the board and supervisors ask for; the model may act within a defined envelope; people sample, monitor and can stop it.
Pattern: workflow (prompt chaining, evaluator and optimizer); tier 3: act within an envelope.
Rules it answers to: 4 documents across several jurisdictions, each linked in the brief.
How we know it works: a golden dataset, automated checks on every release, and human review at the level the tier demands.
What could go wrong and who answers: the accountable owner, the kill switch, the escalation route.
Which of the 100 largest US banks have put this use case on the record?
Every rule this brief cites, the morning it changes.
agent deployments, regulator positions and the day's six stories · in your inbox by 7 am ET · free
plus every tracker, bank and agent page update, the morning after · leave any morning