OCC Bulletin 2026-54 of 4 November 2026: How the OCC's Examiner Framework Tiers National Banks' Super Intelligence and AI Agents, From Payment Agents in Tier 1 to Productivity Tools in Tier 4
What the OCC issued to its examiners on 4 November 2026
OCC Bulletin 2026-54, "Super Intelligence: Supervisory Framework," goes to the chief executives of all national banks, federal savings associations and federal branches and agencies of foreign banks, and to all OCC examining personnel. The framework, a 22-page PDF, groups 16 components under six pillars: purpose, risk, control, oversight, resilience and assurance. "Super Intelligence" is the federal term for AI under Executive Order 14434, defined by reference to the statutory definition of artificial intelligence in 15 U.S.C. 9401(3). The OCC says the document was prepared with the assistance of SI and reviewed, edited and approved by a human.
How the four illustrative tiers rank AI agents in banks
The framework scores each use case on decision consequence, reversibility, customer and financial impact, autonomy, data sensitivity, explainability and provenance. In the framework's illustration, a fully autonomous, customer-facing payment agent sits in Tier 1 "regardless of how well it performs in testing," and an internal productivity tool with no customer or financial data exposure, no direct action and fully human-controlled use sits in Tier 4. The core principle is consequence-based risk tiering: a simple rules-based agent that can initiate transactions may present more risk than a sophisticated model that only drafts internal text.
What the bulletin says about its own force
The bulletin states that it does not establish supervisory expectations for banks, that banks are not expected to use it to assess their own SI, and that banks need no separate SI risk appetite. Its text still describes, in detail, the agentic AI controls examiners may consider where they apply it, from kill switches to agent credentials.
Browser Agents Have an Obedience Problem
Browser agents are moving into ordinary commercial settings at the same time that researchers are showing how easily helpfulness can become misplaced obedience. The AgentDyn benchmark, updated on arXiv in May 2026 and surfaced in Quentir's June 28 intelligence pack, tests open-ended agent tasks across shopping, GitHub and daily-life environments, then adds hundreds of indirect prompt-injection cases. The uncomfortable finding is practical: current defenses can make agents unsafe, or so cautious that useful work breaks. That is a governance signal for any company letting an AI system read web pages, parse third-party content, operate tools or prepare business actions.
The issue is larger than one security paper. Public MCP adoption data shows action tools becoming a normal part of agent deployments, and Quentir's recent coverage of agent authority and AI compute chains shows the same shift from model answers to operating context. Browser-agent governance now has to cover untrusted page text, tool permissions, task intent, user confirmation and after-action reconstruction. The commercial bridge is also clear: agentic AI security cannot be reduced to better prompts or a generic dashboard. The useful record is the path from instruction to content exposure to proposed action to human or system approval, especially when the agent works inside accounts, repositories, procurement flows or customer-facing software.
Agent Authority Receipts Are Becoming a Board Evidence Problem
AI agents are moving from advice into business action: updating records, sharing links, triggering workflows, querying data rooms and using tools inside operational systems. That shift makes ordinary model governance incomplete. Boards need to know not only whether an output was accurate, but whether the action was authorized, scoped, approved, denied, logged and reconstructable after the fact.
This Quentir brief introduces the operational idea of an agent authority receipt: a record that connects the delegator, tool permission, data scope, source signal, approval rule, action taken, fallback or denial path, reviewer and timestamp. The article treats the receipt as a governance evidence pattern, not as a claim that current law universally requires one specific object. It draws on cyber-risk warnings, AI transparency developments, agent tooling market signals and delegated-execution research to show why agentic systems need board-readable evidence. For founders, legal teams and audit committees, the useful next step is a reconstruction exercise: choose one AI-mediated action and ask whether a non-participant can explain who authorized it, what changed and why from the evidence alone.