<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Zovos AI — Regulatory Radar</title>
  <subtitle>FFIEC, BSA/AML, CFPB, markets and AI for compliance teams at banks and credit unions of every size.</subtitle>
  <link href="https://zovos.ai/radar.xml" rel="self" />
  <link href="https://zovos.ai/radar.html" />
  <id>https://zovos.ai/radar.html</id>
  <updated>2026-09-24T00:00:00Z</updated>
  <author><name>Adam Swenson</name></author>
  <rights>© 2026 Zovos AI, Inc.</rights>
  <entry>
    <title>The Fed hikes unanimously for the first time since 2023</title>
    <link href="https://zovos.ai/radar-september-fomc-hike.html" />
    <id>https://zovos.ai/radar-september-fomc-hike.html</id>
    <published>2026-09-24T00:00:00Z</published>
    <updated>2026-09-24T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>On September 16 the FOMC raised the federal funds target range a quarter point to 3.75–4% on a 12–0 vote, and the median projection pencils in one more increase before year-end. The cut-or-hold debate of the summer ended in the other direction.</summary>
    <content type="html"><![CDATA[<p>The Federal Open Market Committee “decided to raise the target range for the federal funds rate by 1/4 percentage point to 3-3/4 to 4 percent” on September 16. It was the committee’s first increase since July 2023, and the vote was 12–0. In July the committee held at 3.50–3.75% over three dissents that preferred a hike. Two months later, nobody dissented from one.</p>
<p>The statement’s reasoning is short and new: “Inflation remains elevated. Today’s policy action will support a timelier return to the Committee’s 2 percent goal. The Committee will deliver price stability.” Its read of the real economy is confident. It says “Economic activity is expanding at a solid pace,” and “Job gains have kept pace with the workforce, and the unemployment rate has changed little.” At the press conference, Chair Kevin Warsh put it plainly: “The plain fact is that inflation is too high and has been for too long.”</p>
<h2>What the committee now expects</h2>
<table><caption>FOMC median projections · September vs. June 2026</caption><thead><tr><th>Median</th><th>June</th><th>September</th></tr></thead><tbody><tr><td>Fed funds · end-2026</td><td>3.8%</td><td>4.1%</td></tr><tr><td>Fed funds · end-2027</td><td>3.6%</td><td>4.1%</td></tr><tr><td>Fed funds · end-2028</td><td>3.4%</td><td>3.9%</td></tr><tr><td>Unemployment · Q4 2026</td><td>4.3%</td><td>4.1%</td></tr><tr><td>Core PCE inflation · 2026</td><td>3.3%</td><td>3.4%</td></tr></tbody></table>
<p>The projections do more work than the statement. The median path now ends 2026 at 4.1%, which implies one more quarter-point increase at the October or December meeting. It stays there through 2027 before easing to 3.9% in 2028. In June the same committee saw the rate falling to 3.6% by the end of 2027. That is roughly half a point of higher-for-longer added to the medium-term path in a single quarter.</p>
<blockquote><p>The question for 2026 is no longer when the first cut arrives. It is whether your deposit book reprices faster than your loan book on the way up again.</p></blockquote>
<h2>Where it lands on a community balance sheet</h2>
<p>The mechanics started the next day. The Board raised the interest rate on reserve balances to 3.90% and the primary credit rate to 4.0%, both effective September 17. The discount window and the overnight yield on excess cash moved with the target range. Deposit competition moves more slowly and less evenly, and it is where a hiking cycle hurts institutions that fund with rate-sensitive balances.</p>
<p>The macro backdrop the committee cited is consistent with the month’s data. August payrolls rebounded to 162,000 with upward revisions to June and July, and headline CPI held at 3.4% on an energy-driven headline. The committee did not wait for the core, which has fallen to 2.4%, the lowest since March 2021. The hike is a bet that energy-led inflation stays in the headline long enough to matter for expectations.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Retire the rate-cut base case in your 2026 budget and ALCO scenarios. Model the median path of one more increase, and model an alternative with two more hikes.</li><li>Re-run deposit beta assumptions for rate-sensitive balances now. In the last hiking cycle, betas accelerated late in the cycle.</li><li>Refresh liquidity contingency pricing for the 4.0% primary credit rate and confirm your discount-window collateral is pledged and tested.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos re-baselines your rate and deposit scenarios against the FOMC’s published projections on the day they are released. Your ALCO pack then reflects the September path instead of the June one.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.federalreserve.gov/newsevents/pressreleases/monetary20260916a.htm">FOMC statement, September 16, 2026</a></li><li><a href="https://www.federalreserve.gov/newsevents/pressreleases/monetary20260916a1.htm">Implementation Note, September 16, 2026</a></li><li><a href="https://www.federalreserve.gov/monetarypolicy/fomcprojtabl20260916.htm">Summary of Economic Projections, September 16, 2026</a></li><li><a href="https://www.foxbusiness.com/economy/federal-reserve-interest-rate-decision-september-16-2026">Fed hikes for first time since 2023 (Fox Business)</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>The 2023 third-party guidance is headed for replacement</title>
    <link href="https://zovos.ai/radar-tprm-rewrite.html" />
    <id>https://zovos.ai/radar-tprm-rewrite.html</id>
    <published>2026-09-24T00:00:00Z</published>
    <updated>2026-09-24T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>On September 11 the Fed, FDIC, OCC, and NCUA proposed risk-tailored third-party guidance that would replace the June 2023 interagency guidance. The three banking agencies also put core providers’ business practices on the supervisory scale.</summary>
    <content type="html"><![CDATA[<p>The interagency guidance on third-party relationships is set to be replaced. It was issued in June 2023 and has anchored every vendor-management program in the industry since. On September 11 the Federal Reserve, FDIC, OCC, and NCUA requested comment on proposed guidance that would help institutions “better align and tailor” third-party risk management “to the risks of individual third-party relationships.” When it is finalized, the banking agencies plan to rescind the existing guidance and replace it. Comments are due November 16.</p>
<p>The agencies are unusually direct about why. Their proposal says the 2023 guidance “frequently has been interpreted in an overly broad manner and with an insufficient focus on tailoring,” and that it “unintentionally incentivized overly-process-driven approaches that fail to prioritize higher-risk relationships.” The replacement makes risk identification and assessment the foundation. Oversight would scale to the magnitude and likelihood of harm that a specific relationship poses, instead of to the category of activity it touches.</p>
<h2>Core providers, named as the hardest case</h2>
<p>Alongside the proposal, the Fed, FDIC, and OCC issued a joint statement on community banks’ engagement with core service providers. It calls core providers community banks’ “most material, complex, and highest-risk third-party relationships,” and acknowledges that “a significant percentage of the core provider market is represented by just a few large providers, which limits CBOs’ negotiating power.”</p>
<p>The statement then turns that into supervisory leverage. When the agencies decide how much examination attention to give a core provider, they will weigh its transparency. That covers its willingness to hand over timely due-diligence information, its use of measurable service levels, its disclosure of operational and security incidents, and its billing practices. They will also weigh contract terms that obstruct a bank’s exit or its use of supplemental providers. The Fed also proposed a separate third-party guide for the community banks it supervises.</p>
<blockquote><p>For the first time, a core provider’s refusal to hand you a SOC report is framed as the provider’s supervisory problem as well as yours.</p></blockquote>
<h2>The anchor for AI vendors moves too</h2>
<p>In August we pointed to the 2023 guidance as one of the two anchors that still govern generative-AI vendors after the model-risk rewrite carved GenAI out of scope. That anchor is now in motion. Tailoring cuts both ways. A lighter touch for low-risk vendors is only defensible if your risk assessment says why. An AI feature embedded in a core or compliance platform is exactly the kind of relationship whose risk rating needs to be written down instead of assumed.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Keep operating under the 2023 guidance until a final version replaces it. The proposal is non-binding and changes nothing today.</li><li>Start the re-tiering now: rank every third party by assessed magnitude and likelihood of harm, and record the rationale. That record is what tailoring will be judged on.</li><li>Comment by November 16, and use the core-provider statement in your next renewal. Ask for SOC reports, measurable SLAs, and incident-notice terms in writing.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos keeps a risk rating and a written rationale on every vendor in your inventory, including the AI features inside them. A risk-tailored program then has its evidence attached from day one.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.occ.gov/news-issuances/news-releases/2026/nr-ia-2026-77.html">Agencies seek comment on proposed third-party risk management guidance</a></li><li><a href="https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-46.html">Third-Party Risk Management: Proposed Guidance (OCC Bulletin 2026-46)</a></li><li><a href="https://ncua.gov/news/events/2026/comments-proposed-third-party-risk-management-guidance-due-november-16">NCUA: comments on proposed third-party guidance due November 16</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>“Unsafe or unsound” gets a definition, and MRAs get a materiality bar</title>
    <link href="https://zovos.ai/radar-mra-final-rule.html" />
    <id>https://zovos.ai/radar-mra-final-rule.html</id>
    <published>2026-09-24T00:00:00Z</published>
    <updated>2026-09-24T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>The OCC and FDIC’s final rule, published September 1 and effective November 2, codifies “unsafe or unsound practice” around likely material financial harm and limits when examiners may issue MRAs. The FDIC has retired MRBAs and supervisory recommendations.</summary>
    <content type="html"><![CDATA[<p>Section 8 enforcement turns on the phrase “unsafe or unsound practice,” and for the first time that phrase has a regulatory definition. Under the OCC and FDIC final rule, adopted August 27 and published in the Federal Register on September 1, it means a practice, act, or failure to act that “is contrary to generally accepted standards of prudent operation” and that, if continued, “is likely to” materially harm the institution’s financial condition or present a material risk of loss to the Deposit Insurance Fund. It also covers a practice that has already materially harmed the institution. The rule takes effect November 2.</p>
<p>The same materiality bar now governs MRAs. Examiners may issue one for a practice that is contrary to prudent operation and “could reasonably be expected to, under current or reasonably foreseeable conditions,” cause that material harm. They may also issue one for an actual violation of a banking or banking-related law or regulation. Weaknesses below that line become “supervisory observations,” which do not by themselves require corrective action.</p>
<h2>What changes in the exam report</h2>
<table><caption>Supervisory findings under the final rule</caption><thead><tr><th>Finding</th><th>Standard after Nov 2</th></tr></thead><tbody><tr><td>Unsafe or unsound practice</td><td>Likely material harm to financial condition or DIF</td></tr><tr><td>MRA</td><td>Could reasonably be expected to cause material harm, or an actual violation</td></tr><tr><td>Supervisory observation</td><td>Weakness below the MRA bar, with no required action</td></tr><tr><td>FDIC MRBA / supervisory recommendation</td><td>Discontinued, then redesignated as MRAs or closed</td></tr></tbody></table>
<p>At the FDIC the change is structural. Its implementation statement (FIL-53-2026) discontinues Matters Requiring Board Attention and supervisory recommendations. Outstanding items “will either be redesignated as MRAs where appropriate or otherwise closed out,” and exam reports will carry more concise comments. On September 17 the FDIC Board rescinded its 2016 statement on supervisory recommendations as superseded (FIL-61-2026).</p>
<blockquote><p>A higher bar for MRAs does not lower the bar for prudence. It moves the argument to whether harm is “likely” and “material,” and that argument is won with numbers.</p></blockquote>
<p>Two limits matter. The rule binds the OCC and FDIC only. The Federal Reserve and NCUA are not parties, so state member banks and credit unions keep their current frameworks. And the agencies declined to set numerical thresholds for “likely” or “material,” so the line will be drawn exam by exam.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Inventory open MRBAs and supervisory recommendations now and ask your FDIC case manager how each will be redesignated or closed.</li><li>Expect fewer MRAs for documentation-only gaps, but keep fixing them. Observations still shape management ratings and the next exam.</li><li>When you contest a finding, argue materiality with financial data. Name the balance, the loss and how likely it is.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos tracks every exam finding by type (MRA, observation or violation) with its remediation evidence. Redesignating legacy findings becomes a report you run instead of a hunt through files.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-40.html">Unsafe or Unsound Practices and MRAs: Final Rule (OCC Bulletin 2026-40)</a></li><li><a href="https://www.fdic.gov/news/financial-institution-letters/2026/implementation-final-rule-unsafe-or-unsound-practices">FDIC FIL-53-2026: Implementation of the final rule</a></li><li><a href="https://www.fdic.gov/news/financial-institution-letters/2026/rescission-board-statement-development-and-communication">FDIC FIL-61-2026: Rescission of the 2016 supervisory recommendations statement</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>The 18-month exam cycle now reaches banks under $6 billion</title>
    <link href="https://zovos.ai/radar-exam-cycle-6b.html" />
    <id>https://zovos.ai/radar-exam-cycle-6b.html</id>
    <published>2026-09-24T00:00:00Z</published>
    <updated>2026-09-24T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>An interagency interim final rule, effective September 14, raises the asset ceiling for the extended on-site exam cycle from $3 billion to $6 billion, as the 21st Century ROAD to Housing Act requires.</summary>
    <content type="html"><![CDATA[<p>On September 10 the FDIC, Federal Reserve, and OCC issued an interim final rule implementing the 21st Century ROAD to Housing Act’s increase in the asset threshold for the 18-month on-site examination cycle, from $3 billion to $6 billion. The rule took effect on publication, September 14, and comments are due October 14. In the agencies’ words, moving qualifying banks from a 12- to an 18-month cycle “appropriately reduces burden, including time and resources spent, for these low-risk institutions.”</p>
<p>Eligibility is not automatic by size. A qualifying institution must be well capitalized and well managed, carry an “outstanding” or “good” composite rating, not be subject to a formal enforcement proceeding or order, and not have undergone a change in control in the prior 12 months. Offsite monitoring continues between exams.</p>
<h2>Who gains the longer cycle</h2>
<p>Newly eligible banks and savings associations · by primary regulator</p>
<p>The agencies estimate about 188 more banks and savings associations become eligible, bringing the total that may qualify for an 18-month cycle to 4,016. The rule does not reach credit unions, whose exam schedule is set by NCUA.</p>
<blockquote><p>Eighteen months between exams means six more months of evidence that the next examiner reads cold. Keep the file ready for an examiner at any time, instead of only in exam season.</p></blockquote>
<p><strong>What this means for your bank</strong></p>
<ul><li>If you are between $3 billion and $6 billion, confirm with your regulator whether your ratings and status put you on the 18-month cycle.</li><li>Re-sequence internal audit and board reporting to the longer cycle rather than letting coverage lapse between exams.</li><li>Remember that eligibility can be lost. A rating downgrade, an enforcement action, or a change in control resets it.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos keeps exam-ready evidence current continuously, so a longer cycle means less disruption. It should not mean a bigger scramble when the entry letter arrives.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.federalreserve.gov/newsevents/pressreleases/bcreg20260910a.htm">Agencies increase eligibility for the 18-month exam cycle (Federal Reserve)</a></li><li><a href="https://www.fdic.gov/news/financial-institution-letters/2026/interim-final-rule-expanded-examination-cycle-small-insured">FDIC FIL-57-2026: Interim final rule on expanded examination cycle</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Headline CPI holds at 3.4% while the core falls to 2.4%</title>
    <link href="https://zovos.ai/radar-august-cpi.html" />
    <id>https://zovos.ai/radar-august-cpi.html</id>
    <published>2026-09-24T00:00:00Z</published>
    <updated>2026-09-24T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>August’s CPI rose 0.4% on the month with gasoline accounting for over a third of the increase, while the core’s annual rate fell to its lowest since March 2021. Five days later, the Fed hiked anyway.</summary>
    <content type="html"><![CDATA[<p>The Consumer Price Index rose 0.4% in August on a seasonally adjusted basis, and 3.4% over the year, the same annual rate as July. The BLS release, published September 11, pinned the source. Gasoline rose 3.9% on the month and “accounted for over one third of the monthly all items increase.” Over the year, gasoline is up 27.4% and the energy index 16.3%.</p>
<p>Underneath, the picture is the reverse. Prices excluding food and energy rose 0.3% on the month but just 2.4% over the year. That is the lowest core rate since March 2021. Shelter rose 0.3% after two softer months, and food rose 0.1%.</p>
<h2>Where the 3.4% comes from</h2>
<p>CPI · 12-month change by component, August 2026</p>
<blockquote><p>A 2.4% core and a rate hike in the same week is the committee telling you which number it thinks your customers feel.</p></blockquote>
<p><strong>What this means for your bank</strong></p>
<ul><li>Stress household-credit segments on fuel costs instead of the core. A 27% rise in gasoline over the year hits commuting borrowers first.</li><li>With wages up 3.1% against 3.4% prices, watch early-stage consumer delinquency and overdraft usage for the squeeze.</li><li>Present both the headline and the core in the ALCO pack. The Fed just showed which one sets policy right now.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos maps the macro series behind each of your credit and deposit assumptions, so a CPI release updates the right model inputs automatically.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.bls.gov/news.release/cpi.nr0.htm">Consumer Price Index, August 2026</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Payrolls rebound to 162K, and July is no longer negative</title>
    <link href="https://zovos.ai/radar-august-payrolls-rebound.html" />
    <id>https://zovos.ai/radar-august-payrolls-rebound.html</id>
    <published>2026-09-24T00:00:00Z</published>
    <updated>2026-09-24T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>August payrolls rose 162,000, and revisions turned July’s first-reported decline into a gain. Unemployment held at 4.1%. The stalled labor market in last month’s lead story did not survive the revisions.</summary>
    <content type="html"><![CDATA[<p>Total nonfarm payroll employment rose by 162,000 in August, according to the September 4 Employment Situation release. It was the strongest gain since March and far above expectations. The revisions reversed the story we led with last month. July, first reported as a 23,000 decline, now shows a 21,000 gain, and June was revised up to 31,000. Combined, June and July are 55,000 higher than previously reported. The August figure is preliminary and will be revised twice more.</p>
<p>The unemployment rate held at 4.1%, and labor-force participation rose to 61.6%. Average hourly earnings rose 10 cents, or 0.3%, to $37.75, and are up 3.1% over the year. That is still below August’s 3.4% CPI, so real wages are falling.</p>
<h2>How the record changed</h2>
<table><caption>Payroll gains · as first reported vs. as revised</caption><thead><tr><th>Month</th><th>First reported</th><th>Now</th></tr></thead><tbody><tr><td>June</td><td>+57K</td><td>+31K</td></tr><tr><td>July</td><td>−23K</td><td>+21K</td></tr><tr><td>August</td><td>+162K</td><td>Preliminary</td></tr></tbody></table>
<blockquote><p>Two months ago the revisions took jobs away. This month they gave them back. Build credit assumptions on the three-month average, never on a single print.</p></blockquote>
<p><strong>What this means for your bank</strong></p>
<ul><li>Unwind any recession overlay you added on July’s negative print. The revised record shows slow growth instead of contraction.</li><li>Keep the real-wage squeeze in view. Wages rising 3.1% against 3.4% inflation put pressure on lower-income borrowers even with hiring intact.</li><li>Expect a labor market this firm to keep the Fed on its hiking path, and price deposits accordingly.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos re-runs your credit and deposit baselines when a revision moves the macro record in either direction.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.bls.gov/news.release/empsit.nr0.htm">Employment Situation, August 2026</a></li><li><a href="https://www.foxbusiness.com/economy/us-jobs-report-august-2026">August jobs report: US adds 162,000 positions (Fox Business)</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Frontier AI crosses the “Critical” cyber line</title>
    <link href="https://zovos.ai/radar-astra-critical-cyber.html" />
    <id>https://zovos.ai/radar-astra-critical-cyber.html</id>
    <published>2026-09-24T00:00:00Z</published>
    <updated>2026-09-24T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>OpenAI rated GPT-6 Astra “Critical” for cyber capability and released it broadly. It is the first OpenAI model to reach that level. Nineteen days later, Anthropic shipped Opus 5.5 with most cybersecurity tasks rerouted to an older model.</summary>
    <content type="html"><![CDATA[<p>OpenAI’s GPT-6 Astra system card, published September 3, says the model “is a significant step up in cyber capabilities and meets our Critical threshold.” It is the first OpenAI model to reach that threshold. OpenAI explains what that means: “With the right tools and access, GPT-6 Astra can find previously unknown security flaws and develop new ways to exploit them across many well-protected systems without a person guiding each step.” The model nonetheless rolled out broadly to paid ChatGPT plans, the API, and Amazon Bedrock. It costs $10 per million input tokens and $50 per million output.</p>
<p>On September 22 Anthropic released Claude Opus 5.5, which it says “performs at the level of Claude Fable 5.1 on most work and costs 40% less to run than Opus 5,” at $4 and $20 per million tokens. Because the model “has extremely strong cyber capabilities,” Anthropic applied safeguards under which routine bug-fixing still works, “but most cybersecurity tasks will be re-routed to Opus 4.8.” Vetted defenders get a separate path through an expanded Cyber Verification Program.</p>
<h2>Two risks, one month</h2>
<p>The first risk is on the threat side. Autonomous discovery and exploitation of unknown flaws is now a commercial capability, with the labs’ safeguards as the main brake on misuse. For a community bank, the exposed surface is mostly someone else’s code, such as the core, the online-banking platform and the payment processor. That makes a provider’s patch cadence and incident transparency a first-order control.</p>
<p>The second is on the vendor side. Safeguard routing means the model a vendor contracts for is not always the model that answers. By design, some requests go to a different, older model. Enterprise access is also a configuration decision, because ChatGPT Enterprise administrators must switch Astra on for their organizations. A vendor attestation that names one model and one version no longer describes what actually runs.</p>
<blockquote><p>When the model can find the zero-day, the question for your vendors is no longer whether they use AI. The question is how fast they patch, and how fast they tell you.</p></blockquote>
<p><strong>What this means for your bank</strong></p>
<ul><li>Ask core and digital-banking providers for their patch-cadence commitments and incident-notice timelines in writing. The new core-provider statement supports the request.</li><li>Update AI-vendor attestations to cover routing. They should say which models may serve your requests, under what conditions, and how you are told when that changes.</li><li>Add AI-accelerated vulnerability discovery to your cyber risk assessment and tabletop scenarios this quarter.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos records the model, version, and routing disclosures behind every AI feature in your vendor stack, and opens a review when a provider’s release changes them.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://deploymentsafety.openai.com/gpt-6-astra">GPT-6 Astra System Card (OpenAI)</a></li><li><a href="https://www.anthropic.com/news/claude-opus-5-5">Introducing Claude Opus 5.5, September 22, 2026</a></li><li><a href="https://www.csoonline.com/article/4218679/openai-launches-gpt-6-astra-its-first-model-to-cross-a-critical-cybersecurity-threshold.html">OpenAI launches GPT-6 Astra (CSO Online)</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Payrolls turn negative, and the months behind them shrink</title>
    <link href="https://zovos.ai/radar-july-jobs-negative.html" />
    <id>https://zovos.ai/radar-july-jobs-negative.html</id>
    <published>2026-08-08T00:00:00Z</published>
    <updated>2026-08-08T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>July shed 23,000 jobs, the first monthly decline of the cycle, while revisions erased another 103,000 from May and June. The labor market has stopped absorbing workers, six weeks before the September FOMC.</summary>
    <content type="html"><![CDATA[<p>Nonfarm payrolls fell by 23,000 in July, against expectations of roughly 83,000 gains. It was the first monthly decline of this cycle. The revisions were the harder blow. May was cut by 66,000 to just 63,000 and June by 37,000 to 20,000, taking 103,000 jobs out of the recent record. What looked in early July like a cooling labor market now reads, three prints later, like one that has stalled.</p>
<p>The unemployment rate fell to 4.1%, and that is not good news either. The decline came largely from people leaving the labor force. Participation dropped to 61.4%, a level not seen in over five years. Wage growth confirms the loosening. Average hourly earnings rose 3.2% over the year, the slowest since May 2021.</p>
<h2>How fast the picture changed</h2>
<table><caption>Payroll gains · as first reported vs. as revised</caption><thead><tr><th>Month</th><th>First reported</th><th>Now</th></tr></thead><tbody><tr><td>May</td><td>+172K</td><td>+63K</td></tr><tr><td>June</td><td>+57K</td><td>+20K</td></tr><tr><td>July</td><td>−23K</td><td>Preliminary</td></tr></tbody></table>
<blockquote><p>Revisions of this size mean the economy your June assumptions were built on did not exist. Recalibrate to the revised record instead of the remembered one.</p></blockquote>
<h2>Into the September meeting</h2>
<p>This report lands on a committee that split 9–3 in July with all three dissents preferring a hike. A negative payroll print and decelerating wages are the strongest counterargument the doves have had all year. With inflation at 3.5% and falling, September 15–16 is now a genuinely open meeting. The July CPI, due August 12, becomes the swing data point.</p>
<p>For community banks the credit signal outranks the rate signal. Consumer delinquency cycles begin when a labor market sheds jobs, however mildly. The payroll-deposit inflows that anchor community funding soften first.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Refresh loss and delinquency assumptions against the revised payroll record. The June-quarter economy was weaker than your models were told.</li><li>Watch payroll-linked deposit inflows weekly through the fall. They are your earliest local read on this national turn.</li><li>Hold both a cut and a hold scenario for September at real weight, and pre-draft the ALCO narrative for each.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos re-runs your credit and deposit scenario baselines automatically when a data revision moves the macro record. Your assumptions follow the data instead of the headline.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.bls.gov/news.release/empsit.nr0.htm">Employment Situation, July 2026</a></li><li><a href="https://www.federalreserve.gov/newsevents/pressreleases/monetary20260729a.htm">FOMC statement, July 29, 2026</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>The FDIC’s appeals office opens with wider grounds</title>
    <link href="https://zovos.ai/radar-fdic-appeals-office.html" />
    <id>https://zovos.ai/radar-fdic-appeals-office.html</id>
    <published>2026-08-08T00:00:00Z</published>
    <updated>2026-08-08T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>The independent Office of Supervisory Appeals is operational as of August 4 and replaces the SARC. Appeal rights now extend to certain matters even when an enforcement action is proposed or pending.</summary>
    <content type="html"><![CDATA[<p>As of August 4, FDIC-supervised institutions have a new final level of review for disputed exam findings. The Office of Supervisory Appeals is operational (FIL-46-2026) and replaces the Supervision Appeals Review Committee under revised guidelines the FDIC Board approved in January. The office has a history. It was first stood up in 2021 and disbanded after a leadership change before hearing a single appeal. This is its second launch.</p>
<p>The design answers the standing critique of the SARC, which was that appeals were decided inside the same reporting lines that made the original call. The new office “is independent of the Divisions that make supervisory determinations” and will decide appeals “without deferring to the judgments of either party.” Panels draw on reviewing officials with varied backgrounds. Each panel includes at least one official with bank-supervisory experience and at least one with industry experience.</p>
<h2>The scope expansion that matters</h2>
<p>The quietly significant change is what can be appealed. Under the revised guidelines, “institutions’ appeal rights are now expanded to permit appeals in certain cases when an enforcement action is proposed or pending.” Under the prior regime, a pending enforcement matter could effectively freeze a bank’s ability to contest the underlying supervisory determination. The new guidelines narrow that blocker.</p>
<blockquote><p>An appeal channel you never intend to use still changes your exam. The possibility of independent review disciplines what gets written down.</p></blockquote>
<p><strong>What this means for your bank</strong></p>
<ul><li>Refresh your exam-dispute playbook. Know the deadlines and the determinations that qualify as material before the next ROE arrives.</li><li>Contemporaneous documentation is the whole appeal. Build the factual record at the exit meeting, before the ratings land.</li><li>Weigh the relationship cost honestly, but price in the new independence. This office is structurally different from the SARC.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos keeps your exam workpapers, examiner correspondence, and finding-by-finding responses in one timeline. If you ever appeal, the record already exists.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.fdic.gov/news/financial-institution-letters/2026/fdic-office-supervisory-appeals-operational">FDIC FIL-46-2026: Office of Supervisory Appeals is operational</a></li><li><a href="https://www.fdic.gov/news/press-releases/2026/fdic-launches-new-office-supervisory-appeals">FDIC press release: Office of Supervisory Appeals launch</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Open banking heads back to the drawing board</title>
    <link href="https://zovos.ai/radar-data-rule-oira.html" />
    <id>https://zovos.ai/radar-data-rule-oira.html</id>
    <published>2026-08-08T00:00:00Z</published>
    <updated>2026-08-08T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>A revised §1033 proposal reached OIRA in the first week of August while the October 2024 rule sits enjoined, its appeal stayed, and its compliance clock paused. The direction survives, but the deadlines do not.</summary>
    <content type="html"><![CDATA[<p>In the first week of August, the CFPB sent a revised Personal Financial Data Rights proposal to OIRA. That is one of the final steps before a proposed rule publishes for comment, and it confirms that the Bureau intends to substantially rework the October 2024 §1033 rule rather than defend it.</p>
<p>The operative status of the 2024 rule deserves precision, because it is genuinely tangled. A federal court in Kentucky enjoined the Bureau from enforcing it. The appeal of that ruling is stayed in the Sixth Circuit at the CFPB’s request while the Bureau rewrites the rule. The looming compliance deadlines are paused along with it. The rule exists on paper. Its obligations, for now, do not bind.</p>
<h2>What we said in May, and what changed</h2>
<p>Our May edition described §1033 entering its first compliance tier, with a build clock running for smaller institutions. That was the frame the 2024 rule prescribed, and the injunction and the OIRA submission have formally suspended it. The correction matters. If your 2027–2028 roadmap still cites the old tier dates, it is planning against a schedule that no longer exists.</p>
<blockquote><p>The deadline is gone, but the direction remains. Open banking keeps arriving. The rewrite is about who pays for the rails and who holds the liability.</p></blockquote>
<h2>Build for the strategy instead of a dead deadline</h2>
<p>Reporting on the revised proposal suggests the contested ground is cost recovery for data-access infrastructure and liability allocation. Whether consumers get API access to their data is not in dispute. Credential-based screen scraping is still the practice every party wants retired. The 2024 rule demanded authenticated APIs, consent and authorization logging, and revocation. The market and the eventual rule are still converging on those capabilities. What changed is the clock and possibly the cost model.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Update board and roadmap language to say the 2024 tier deadlines are paused. Cite the injunction and the pending rewrite, with dates.</li><li>Keep data-access, consent-logging, and revocation work as strategic investments with flexible timing. Do not dismantle what you built.</li><li>Comment when the revised NPRM publishes. Cost recovery and liability allocation are exactly where community-bank economics need a voice.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos tracks the status, litigation posture and live deadlines of each rule your roadmap depends on. It also flags the documents in your governance stack that still cite superseded dates.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.consumerfinancemonitor.com/2026/08/06/cfpb-sends-new-section-1033-open-banking-proposal-to-oira-for-review/">CFPB sends new §1033 proposal to OIRA (Consumer Finance Monitor)</a></li><li><a href="https://www.reginfo.gov/public/do/eoReviewSearch">OIRA: regulatory review dashboard</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>The model-risk rewrite left GenAI ungoverned, and the RFI hasn’t come</title>
    <link href="https://zovos.ai/radar-model-risk-vacuum.html" />
    <id>https://zovos.ai/radar-model-risk-vacuum.html</id>
    <published>2026-08-08T00:00:00Z</published>
    <updated>2026-08-08T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>April’s SR 26-2 superseded fifteen years of SR 11-7 and explicitly carved generative and agentic AI out of scope, promising an RFI “in the near future.” Four months on, it has not arrived, and the models keep shipping.</summary>
    <content type="html"><![CDATA[<p>On April 17 the Federal Reserve, OCC, and FDIC issued revised model risk management guidance (SR 26-2, OCC Bulletin 2026-13, FDIC FIL-15-2026). It supersedes SR 11-7, the 2011 document that governed bank model risk for fifteen years. The revision modernizes the framework for statistical and traditional AI models. Then it draws a line. Generative and agentic AI models are explicitly out of scope, described as too “novel and rapidly evolving” to govern in this document.</p>
<p>The agencies paired the carve-out with a promise. They said a request for information on model risk and banks’ use of AI, including generative and agentic AI, would come “in the near future.” As this edition went to press on August 8, no such RFI had been published. The result is a genuine vacuum. The fastest-moving model class in your institution is the one class your model-risk guidance now formally declines to cover.</p>
<h2>The gap, precisely</h2>
<table><caption>What governs what, as of August 2026</caption><thead><tr><th>Model class</th><th>Governing framework</th></tr></thead><tbody><tr><td>Traditional statistical &amp; quantitative models</td><td>SR 26-2 (revised guidance)</td></tr><tr><td>Non-generative, non-agentic AI/ML</td><td>SR 26-2 (revised guidance)</td></tr><tr><td>Generative AI · agentic AI</td><td>Out of scope. RFI promised but not yet issued</td></tr><tr><td>AI vendors as third parties</td><td>Interagency TPRM guidance (unchanged since June 2023)</td></tr></tbody></table>
<blockquote><p>A carve-out is not a safe harbor. The examiner who agrees your chatbot is outside SR 26-2 will still ask what does govern it, and “nothing” is the wrong answer.</p></blockquote>
<h2>Governing into the vacuum</h2>
<p>Two anchors survive. The first is the third-party risk lens. The interagency guidance on third-party relationships has not changed since June 2023, and it still covers every GenAI vendor relationship. Inventory, diligence, and monitoring obligations stand regardless of the model-risk carve-out. The second is that nothing prevents you from applying SR 26-2’s own principles to GenAI voluntarily. That means an inventory entry, a documented validation approach sized to use-case risk, and defined ownership. Banks that do so now will have both a defensible exam answer and a ready-made RFI comment letter.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>State your GenAI governance position in writing. Say which framework you apply voluntarily, to which use cases, and who owns it.</li><li>Keep GenAI tools in the model inventory even though SR 26-2 does not require it. The inventory is your exam answer.</li><li>Pre-draft your RFI response now, while the pain points are fresh. The comment window will be short when it finally opens.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos maintains your AI use-case inventory with each tool’s governance status, covering framework, validation state and owner. Your own documented policy fills the gap the guidance left.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-13.html">Model Risk Management: Revised Guidance (OCC Bulletin 2026-13)</a></li><li><a href="https://www.occ.gov/news-issuances/news-releases/2026/nr-occ-2026-29.html">OCC news release: revised model risk management guidance</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>GDP slows to 1.5%, but private demand accelerated</title>
    <link href="https://zovos.ai/radar-q2-gdp-advance.html" />
    <id>https://zovos.ai/radar-q2-gdp-advance.html</id>
    <published>2026-08-08T00:00:00Z</published>
    <updated>2026-08-08T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>The advance estimate’s headline hides the split that matters. Final sales to private domestic purchasers sped up to 3.9% while the energy quarter pushed the price indexes to their highest readings of the cycle.</summary>
    <content type="html"><![CDATA[<p>Real GDP grew at a 1.5% annual rate in the second quarter per the BEA’s July 30 advance estimate, down from 2.1% in the first quarter. The headline is the least informative number in the release. Growth came from consumer spending, investment, and exports, offset by lower government spending and a rise in imports.</p>
<p>Real final sales to private domestic purchasers strip out the noise and give the purest read on underlying private demand. That measure accelerated from 1.7% to 3.9%. The economy was not losing momentum in the spring. The private sector was speeding up underneath a soft trade-and-government headline.</p>
<h2>The price quarter</h2>
<p>The energy shock owned the quarter’s price data. The PCE price index rose at a 5.1% annual rate (from 4.6%), and the gross domestic purchases price index hit 5.7% (from 3.6%). Core PCE prices decelerated sharply to 3.4%, from 4.4% in the first quarter. The monthly CPI has been drawing the same shape, with a loud, energy-driven headline over a genuinely improving core.</p>
<blockquote><p>Read the quarter twice. Nominal statements will look inflated by the price spike, while real private demand was the strongest it has been all year.</p></blockquote>
<p><strong>What this means for your bank</strong></p>
<ul><li>Use private domestic final sales instead of headline GDP as the demand assumption behind your loan-growth outlook.</li><li>Deflate Q2 nominal comparisons before drawing conclusions. A 5.7% purchases-price quarter distorts every unadjusted trend line.</li><li>Note the tension between GDP and payrolls in ALCO minutes. Demand accelerated while hiring stalled, and one of them will give this fall.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos annotates your board packs with the macro series that actually drive your assumptions. The committee then debates the right number instead of the headline.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.bea.gov/news/2026/gdp-advance-estimate-2nd-quarter-2026">GDP (Advance Estimate), 2nd Quarter 2026 (BEA)</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Loan officers ease CRE standards for the first time this cycle</title>
    <link href="https://zovos.ai/radar-july-sloos.html" />
    <id>https://zovos.ai/radar-july-sloos.html</id>
    <published>2026-08-08T00:00:00Z</published>
    <updated>2026-08-08T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>The Fed’s July survey shows C&amp;I standards steady and demand firming from larger borrowers. It also shows the first net easing in commercial real estate lending standards of the cycle.</summary>
    <content type="html"><![CDATA[<p>The Federal Reserve’s July Senior Loan Officer Opinion Survey, released August 3, reads like a credit market exhaling. On C&amp;I, banks reported “basically unchanged standards for commercial and industrial (C&amp;I) loans to firms of all sizes,” with “stronger demand for C&amp;I loans from large and middle-market firms” and little change from small firms.</p>
<p>The turn is in commercial real estate. Banks “generally reported easier standards and basically unchanged demand for commercial real estate (CRE) loans.” Specifically, “moderate and modest net shares of banks reported having eased standards” for nonfarm nonresidential and multifamily loans respectively. After years of one-way tightening, that is the first net easing of the cycle.</p>
<h2>What an easing turn means mid-cycle</h2>
<p>An easing cycle in CRE arriving in the same week payrolls turned negative is a combination worth sitting with. Competitive pressure to follow looser terms will build just as the labor data argues for discipline. For community banks, CRE concentration is already the exam topic that never leaves the table. If you can show your standards held while the market eased, that counts in your favor at the exam. Quietly matching the street is how concentration findings start.</p>
<blockquote><p>The first bank to ease sets the market price of risk for everyone. Decide deliberately whether to follow, and write the decision down.</p></blockquote>
<p><strong>What this means for your bank</strong></p>
<ul><li>Restate your CRE risk appetite before the competition forces the question. Make an explicit decision to hold or follow, and minute it.</li><li>If you ease, do it visibly and on stated criteria. Name the property types, the sponsors and the pricing floor, so the change does not drift deal by deal.</li><li>Pair the SLOOS turn with the payrolls print in your next credit committee pack. Underwriting into a softening labor market deserves both charts.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos tracks your loan-level underwriting exceptions against your stated risk appetite, so standards drift shows up in a report before it shows up in an exam.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.federalreserve.gov/data/sloos/sloos-202607.htm">Senior Loan Officer Opinion Survey, July 2026</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Two frontier releases in 24 days, and no rulebook yet</title>
    <link href="https://zovos.ai/radar-opus-5-cadence.html" />
    <id>https://zovos.ai/radar-opus-5-cadence.html</id>
    <published>2026-08-08T00:00:00Z</published>
    <updated>2026-08-08T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>Claude Opus 5 landed July 24, three and a half weeks after Sonnet 5. That release cadence is now structurally faster than the guidance meant to govern it.</summary>
    <content type="html"><![CDATA[<p>On July 24, Anthropic released Claude Opus 5 at $5 per million input tokens and $25 per million output, 24 days after Sonnet 5. The company says the model “more than doubles Opus 4.8’s performance at a lower cost per task” on its hardest agentic benchmark and “comes close to the frontier intelligence of Claude Fable 5 at half the price.” Two frontier-class releases in under a month no longer count as an event. That is now the operating tempo of the industry your vendors build on.</p>
<p>Set that tempo against the regulatory calendar. The revised model-risk guidance took fifteen years to replace its predecessor, explicitly excludes generative and agentic AI, and the RFI meant to start closing that gap has not yet been issued. In the time since the guidance published in April, the frontier has shipped at least two major models. The clock speeds are not close, and they are not converging.</p>
<h2>Tempo as a risk parameter</h2>
<blockquote><p>Your model-governance cycle is annual. Your vendors’ model supply chain now turns over monthly. The risk is that ratio, more than any single release.</p></blockquote>
<p>A monthly cadence plus falling prices creates constant swap pressure. Every few weeks, each vendor with an AI feature gets a fresh reason to change the model underneath you. The reason may be cost or capability, or a version may have been deprecated. A governance process that assumes model stability between annual reviews is now assuming something false.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Move AI-vendor attestations covering model, version and change log to a quarterly cadence. Annual reviews cannot see monthly churn.</li><li>Require deprecation notice periods in AI-relevant contracts. A forced upgrade on a vendor’s schedule becomes your validation emergency.</li><li>Log the cadence itself in your risk assessment. It is the honest justification for the monitoring budget you are about to ask for.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos watches the release feeds of the model providers under your vendor stack and opens a review task when one ships. Software that runs at release speed handles the tempo problem for you.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.anthropic.com/news/claude-opus-5">Introducing Claude Opus 5, July 24, 2026</a></li><li><a href="https://www.anthropic.com/news/claude-sonnet-5">Introducing Claude Sonnet 5, June 30, 2026</a></li><li><a href="https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-13.html">Model Risk Management: Revised Guidance (OCC Bulletin 2026-13)</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Inflation snaps back to 3.5% as the energy shock unwinds</title>
    <link href="https://zovos.ai/radar-june-cpi-snapback.html" />
    <id>https://zovos.ai/radar-june-cpi-snapback.html</id>
    <published>2026-08-03T00:00:00Z</published>
    <updated>2026-08-03T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>One month after crossing 4%, headline CPI posted its sharpest monthly drop in years while the core quietly made new progress. The supply shock is leaving the data faster than it arrived.</summary>
    <content type="html"><![CDATA[<p>June’s Consumer Price Index fell 0.4% on the month, seasonally adjusted, pulling the annual rate down from 4.2% to 3.5% in a single print. The driver was the same one that caused the spike, now in reverse. Gasoline dropped 9.7% in June alone as the reopened Strait of Hormuz let crude retrace. Energy is still up 15.7% over the year, so the shock has not left the year-over-year math, but the direction has turned decisively.</p>
<p>The quieter story is the core. Excluding food and energy, prices rose 2.6% over the year, down from 2.9% in May. Shelter rose just 0.1% on the month, the smallest one-month change for that index since January 2021. The categories the Fed watches for persistence are holding, and they are also improving.</p>
<h2>The round trip, by category</h2>
<p>CPI · 12-month change by component, June 2026</p>
<blockquote><p>A supply shock that unwinds in one month rewards the patient. It also rebukes anyone who repriced their balance sheet at the top.</p></blockquote>
<h2>What it means after the 9–3</h2>
<p>The July 29 FOMC held at 3.50–3.75% with three dissents for a hike, and those votes were cast with this CPI report in hand. That tension defines the second half. The headline is falling fast and the core is at 2.6%, yet a bloc of the committee reads the energy episode as a warning about inflation expectations rather than a passing distortion. For banks, the practical read is that the bar for a near-term cut is higher than the improving data alone would suggest.</p>
<p>Deposit and lending behavior will normalize on the same lag as pump prices. The transaction-pattern noise that energy stress pushed into AML monitoring this spring should recede over the summer. That is exactly when thresholds tuned to the stressed baseline start over-alerting in the other direction.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Unwind the emergency assumptions deliberately. Re-baseline AML thresholds and deposit scenarios to the post-shock data, and date the change.</li><li>Keep rate-cut expectations out of your base case until the dissent pattern breaks. A committee with three hike votes is not about to ease.</li><li>Use the April-to-June episode as your documented supply-shock playbook. The next one will look the same in the data.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos flags when your monitoring thresholds were last calibrated against a materially different macro baseline. The unwind then gets the same documented re-tuning the shock did.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.bls.gov/news.release/cpi.nr0.htm">Consumer Price Index, June 2026 release</a></li><li><a href="https://www.bls.gov/opub/ted/2026/consumer-prices-up-3-5-percent-over-the-year-ended-june-2026.htm">Consumer prices up 3.5 percent over the year ended June 2026</a></li><li><a href="https://www.federalreserve.gov/newsevents/pressreleases/monetary20260729a.htm">FOMC statement, July 29, 2026</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>The Fed joins the AML/CFT program rewrite</title>
    <link href="https://zovos.ai/radar-fed-aml-nprm.html" />
    <id>https://zovos.ai/radar-fed-aml-nprm.html</id>
    <published>2026-08-03T00:00:00Z</published>
    <updated>2026-08-03T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>The Board’s July 7 proposal would rebuild Regulation H’s AML program rule around risk and effectiveness, with FinCEN’s priorities wired into a documented risk assessment. Comments close September 8.</summary>
    <content type="html"><![CDATA[<p>On July 7 the Federal Reserve Board proposed amending the AML/CFT program requirements for the banks it supervises (published July 9 at 91 FR 42363, with comments due September 8). The Board voted 6–1 to issue the proposal, with Governor Michael Barr dissenting. It is the Fed’s entry into a rewrite already proposed separately by four other agencies, implementing the Anti-Money Laundering Act of 2020.</p>
<p>The direction of travel is consistent across the proposals. Programs would be judged by effectiveness rather than procedural completeness. Banks would “focus their anti-money laundering resources based on risk, with more attention given to higher-risk customers and activities,” and would “incorporate the Financial Crimes Enforcement Network’s anti-money laundering priorities into their risk assessment processes.” Once a program is established, the Fed says it would concentrate “supervision and enforcement activities on significant failures to implement the program.”</p>
<h2>The pivot from process to risk</h2>
<table><caption>What changes under the proposed program rule</caption><thead><tr><th>Today</th><th>Proposed</th></tr></thead><tbody><tr><td>Pillar-based program checklist</td><td>Risk-based program judged on effectiveness</td></tr><tr><td>Risk assessment as best practice</td><td>Documented risk assessment as an anchor requirement</td></tr><tr><td>National priorities referenced loosely</td><td>FinCEN priorities wired into the risk assessment</td></tr><tr><td>Findings on any program gap</td><td>Supervision focused on significant implementation failures</td></tr></tbody></table>
<blockquote><p>The risk assessment stops being the binder nobody opens and becomes the load-bearing wall of the program. Everything else must trace back to it.</p></blockquote>
<h2>What to do with the comment window</h2>
<p>For community institutions, the promise of this framework is proportionality. Resources go to your actual risk instead of a uniform checklist. The risk is ambiguity, because “effectiveness” and “significant failure” are standards examiners will interpret in the field. The comment window (through September 8) is the moment to ask for the definitions and examples that will constrain that discretion, and to say concretely what a proportionate program looks like at a $500 million bank.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Start the gap analysis now. Put your current risk assessment next to FinCEN’s priorities and note what it does not address.</li><li>Comment by September 8. Ask for concrete effectiveness criteria and community-bank examples, citing your own scale.</li><li>Track the five proposals as one program rewrite. Your BSA policy will need a single coherent update instead of five patches.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos drafts the documented risk assessment the proposed rules anchor on. It builds the assessment from your activity data and maps it line by line to FinCEN’s priorities.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.federalreserve.gov/newsevents/pressreleases/bcreg20260707a.htm">Board requests comment on AML program proposal, July 7, 2026</a></li><li><a href="https://www.federalregister.gov/documents/2026/07/09/2026-13919/anti-money-laundering-and-countering-the-financing-of-terrorism-programs">AML/CFT Programs, 91 FR 42363</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Exams go need-to-know on highly sensitive information</title>
    <link href="https://zovos.ai/radar-sensitive-info-exams.html" />
    <id>https://zovos.ai/radar-sensitive-info-exams.html</id>
    <published>2026-08-03T00:00:00Z</published>
    <updated>2026-08-03T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>A July 16 joint statement lets banks flag their most sensitive materials for on-site or direct-access review instead of handing them over. It also commits the agencies to 72-hour notice if supervisory information is compromised.</summary>
    <content type="html"><![CDATA[<p>On July 16 the Federal Reserve, OCC, and FDIC issued a joint statement on handling highly sensitive information during examinations (OCC Bulletin 2026-32 and FDIC FIL-37-2026). Security teams have argued the premise for years. Some documents are more dangerous in transit than they are informative in an exam file. Examples include network diagrams and schematics, detailed penetration-test results, technical details of specific IT control weaknesses, and succession plans.</p>
<p>The mechanics put the first move with the bank. Management identifies the requested materials it believes are highly sensitive, and the agencies then evaluate whether additional protocols should apply. Chief among them are alternative review methods, such as on-site examination or direct digital access through the bank’s own systems. These reduce the need to transfer sensitive data onto agency systems at all.</p>
<h2>The 72-hour commitment</h2>
<p>The statement also formalizes an obligation running in the other direction. If an agency has a reasonable basis to believe a material compromise of confidential supervisory information has occurred, it commits to notify affected banks as soon as practicable and within no more than 72 hours of determining which banks are affected, subject to applicable legal considerations. Exam material sitting on agency infrastructure is a real attack surface. The agencies are now on the clock to tell you if it leaks.</p>
<blockquote><p>Your pen-test results are a map of your weakest points. The new statement recognizes that the safest place for that map is inside your own walls.</p></blockquote>
<p><strong>What this means for your bank</strong></p>
<ul><li>Build a standing “highly sensitive” inventory now that lists diagrams, pen-test reports, IT control details and succession plans. When the first-day letter arrives, identifying them becomes a lookup instead of a scramble.</li><li>Decide your preferred review method (on-site or direct digital access) for each document class, and be ready to propose it to your EIC.</li><li>Add agency-side CSI compromise to your incident-response playbook. Name who receives the 72-hour notice and what happens in the next 24 hours.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos tags exam-request items against your sensitivity inventory automatically, so the highly-sensitive flag and the review method you want travel with every document request.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-32.html">OCC Bulletin 2026-32: Joint statement on highly sensitive information</a></li><li><a href="https://www.fdic.gov/news/financial-institution-letters/2026/handling-highly-sensitive-information-during-examinations">FDIC FIL-37-2026: Handling of highly sensitive information</a></li><li><a href="https://www.federalreserve.gov/newsevents/pressreleases/bcreg20260716a.htm">Federal Reserve press release, July 16, 2026</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>A narrower CRA with new tiers, a lending-test focus and no Fed</title>
    <link href="https://zovos.ai/radar-cra-rewrite-nprm.html" />
    <id>https://zovos.ai/radar-cra-rewrite-nprm.html</id>
    <published>2026-08-03T00:00:00Z</published>
    <updated>2026-08-03T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>The July 31 proposal would let banks up to $1B examine as small banks and reserve full large-bank exams for those over $10B. It refocuses evaluation on lending. The Federal Reserve did not join.</summary>
    <content type="html"><![CDATA[<p>On July 31 the FDIC and OCC jointly proposed amending their Community Reinvestment Act regulations (FDIC FIL-44-2026 and OCC Bulletin 2026-35). The targeted substantive, technical, and process changes would meaningfully shrink the compliance surface for community institutions. The Federal Reserve, notably, is not a party to the proposal.</p>
<p>The structural change is the asset tiers. Banks under $1 billion would be examined as small banks, up from today’s $412 million cutoff. Banks between $1 billion and $10 billion would be intermediate. Only banks above $10 billion would face the full large-bank examination regime, compared with $1.65 billion today. Institutions at or below $10 billion would also face fewer data collection, maintenance, and reporting requirements.</p>
<h2>Where the tiers would land</h2>
<p>Proposed CRA examination tiers · by total assets</p>
<p>Substantively, the proposal refocuses evaluation on the lending test, tightens community-development grant criteria toward the communities they are meant to benefit, and narrows the retail services considered for CRA credit by excluding deposit services. It is a deliberate turn back toward lending as the core of CRA performance.</p>
<blockquote><p>Two agencies rewriting CRA without the third is itself the story. A bank’s CRA obligations may soon depend on who its regulator is.</p></blockquote>
<h2>The comment window</h2>
<p>Comments are due 60 days after the proposal publishes in the Federal Register. Publication was still pending as this issue went to press, so watch for the date. For most community banks the proposal is relief. The open questions worth commenting on are the transition mechanics, the treatment of in-flight evaluations, and how examiners will weigh lending distribution when the deposit-services lens goes away.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Locate your tier under the proposal and note what falls away. Keep collecting current-rule data until a final rule says otherwise.</li><li>If you are Fed-supervised, plan for divergence. Your CRA regime may end up differing from the national banks across the street.</li><li>Put the comment deadline on the calendar the day the Federal Register publishes. The 60-day clock starts then.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos tracks each of your open comment windows against the Federal Register and drafts the letter skeleton the day the clock starts.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.fdic.gov/news/financial-institution-letters/2026/fdic-and-occ-seek-public-comment-joint-notice-proposed">FDIC FIL-44-2026: Joint CRA notice of proposed rulemaking</a></li><li><a href="https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-35.html">OCC Bulletin 2026-35: CRA proposed rule</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Payrolls cool to 57K as the labor force shrinks</title>
    <link href="https://zovos.ai/radar-june-payrolls.html" />
    <id>https://zovos.ai/radar-june-payrolls.html</id>
    <published>2026-08-03T00:00:00Z</published>
    <updated>2026-08-03T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>June payrolls came in at half the expected gain, with 74,000 in downward revisions behind them and participation at its lowest since 2021. The labor market is finally loosening from the supply side.</summary>
    <content type="html"><![CDATA[<p>Nonfarm payrolls rose just 57,000 in June, roughly half the ~115,000 economists expected. The months behind it got smaller too. May was revised down to 129,000 and April to 148,000, a combined 74,000 fewer jobs than previously reported. The unemployment rate edged down to 4.2%, but for the least reassuring reason. The labor force shrank, with participation falling 0.3 point to 61.5%, its lowest since early 2021.</p>
<p>The composition tells the same late-cycle story as May, but softer. Professional and business services added 36,000, social assistance 25,000, and healthcare 22,000. Leisure and hospitality shed 61,000 on weak seasonal hiring. Hiring is narrowing to the least cyclical corners of the economy.</p>
<h2>Where June’s jobs came from</h2>
<p>Payroll change by sector · thousands, June 2026</p>
<blockquote><p>An unemployment rate that falls because workers leave is a sign of a shrinking labor market. Deposit bases follow workers.</p></blockquote>
<h2>Why it matters for your bank</h2>
<p>A cooling labor market softens the outlook for consumer credit quality and deposit inflows at the same time, and it lands on a committee already split over inflation. Watch your local employers in leisure, hospitality, and retail. The national seasonal-hiring weakness shows up first as payroll-deposit shrinkage in community footprints.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Move consumer-credit monitoring from quarterly to monthly for portfolios concentrated in cyclical employers.</li><li>Recheck deposit-growth assumptions against payroll-inflow data as well as balances. Inflows soften before balances do.</li><li>Log the participation-rate observation in ALCO minutes. Labor supply is the story to track into the fall, more than layoffs.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos maps national sector shifts onto your own commercial exposure and payroll-deposit flows, so the macro release reads as news about your portfolio instead of a headline.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.bls.gov/news.release/archives/empsit_07022026.htm">Employment Situation, June 2026 (July 2 release)</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>A 9–3 hold, with all three dissents for a hike</title>
    <link href="https://zovos.ai/radar-july-fomc-dissent.html" />
    <id>https://zovos.ai/radar-july-fomc-dissent.html</id>
    <published>2026-08-03T00:00:00Z</published>
    <updated>2026-08-03T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>Six weeks after opening with unanimity, the Warsh committee split, and every dissent pointed in the same hawkish direction. The two-sided problem now has an edge.</summary>
    <content type="html"><![CDATA[<p>The FOMC held the target range at 3.50–3.75% on July 29, but the unanimity of June lasted exactly one meeting. Three members dissented, and all three went in the same direction. Beth Hammack, Neel Kashkari, and Lorie Logan each preferred a quarter-point increase. After April’s four-way scatter and June’s 12–0, the committee has found its disagreement again, and this time it points up.</p>
<p>The statement itself barely moved. It still described activity as “expanding at a solid pace” and inflation as “elevated relative to the Committee’s 2 percent goal, in part reflecting supply shocks.” What changed is the arithmetic behind it. The dissenters looked at 3.5% headline inflation and a cooling labor market and still concluded that inflation expectations, more than growth, were the risk worth voting against.</p>
<h2>Three meetings, three committees</h2>
<table><caption>The 2026 vote pattern under two chairs</caption><thead><tr><th>Meeting</th><th>Decision</th><th>Vote</th></tr></thead><tbody><tr><td>April 28–29</td><td>Hold 3.50–3.75%</td><td>Four-way dissent</td></tr><tr><td>June 16–17</td><td>Hold 3.50–3.75%</td><td>12–0</td></tr><tr><td>July 28–29</td><td>Hold 3.50–3.75%</td><td>9–3 · all dissents for +25bp</td></tr></tbody></table>
<blockquote><p>When every dissent points the same way, it stops being noise and becomes a signal about where the committee’s pain threshold sits.</p></blockquote>
<h2>Positioning into September</h2>
<p>September 15–16 brings the next decision and a fresh set of projections. A hawkish bloc of three does not make a hike likely. It does make near-term cuts hard, and it widens the tail in both directions. For deposit pricing, that argues for holding the line. For ALCO, it argues for keeping a genuine hike scenario alive even as the headline data improves.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Keep hold as the base case and retain a live +25bp scenario through year-end. The dissent bloc makes it more than a tail.</li><li>Resist deposit repricing on the CPI improvement alone. The committee has told you it is not convinced yet.</li><li>Refresh the rate narrative in your September ALCO pack after the projections land. The dot pattern will say more than the statement.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos drafts the rate-environment section of your ALCO pack from the primary record each meeting cycle, including votes, dissents, and statement diffs.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.federalreserve.gov/newsevents/pressreleases/monetary20260729a.htm">FOMC statement, July 29, 2026</a></li><li><a href="https://www.federalreserve.gov/monetarypolicy/fomccalendars.htm">FOMC meeting calendar, 2026</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Compliance AI mints a unicorn</title>
    <link href="https://zovos.ai/radar-norm-ai-series-c.html" />
    <id>https://zovos.ai/radar-norm-ai-series-c.html</id>
    <published>2026-08-03T00:00:00Z</published>
    <updated>2026-08-03T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>Norm Ai raised $120M at a $1.2B valuation on July 7. The tools compliance teams buy are now frontier-AI vendors themselves, with everything that implies for your diligence.</summary>
    <content type="html"><![CDATA[<p>On July 7, Norm Ai announced a $120 million Series C at a $1.2 billion valuation, led by Khosla Ventures with participation including Blackstone, Bain Capital Ventures, Coatue, and the law firm Fenwick. The round takes the company past $260 million raised in under three years. Norm builds what it calls “agentic law,” meaning AI that interprets regulatory rules, monitors compliance in real time, and governs how other AI systems operate.</p>
<p>For a community bank, the signal is the category more than this particular vendor. Venture capital at unicorn scale is now flowing into software that sits inside the compliance function itself, reading your policies, watching your communications, and increasingly supervising your other AI. The tools you buy to manage AI risk are AI vendors, with the same concentration, continuity, and model-change questions as any other.</p>
<h2>The recursive vendor problem</h2>
<blockquote><p>When your compliance tooling is itself frontier AI, the question “who validates the validator?” stops being philosophy and becomes a vendor-file entry.</p></blockquote>
<p>A funded category also churns. Capital at this scale brings rapid feature releases, aggressive model upgrades, and eventual consolidation. Every one of those is a change-management event for a program that depends on the tool’s behavior staying validated. The discipline that applies to your core processor applies here, along with the model-version questions that are unique to AI.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Risk-rate compliance-AI tools like any critical vendor. Cover the model provider underneath, data handling, the continuity plan and the exit path.</li><li>Ask which foundation models power the product and how model swaps are disclosed. Write the answer into the contract.</li><li>Treat well-capitalized vendors as more durable but faster-moving. Schedule validation refreshes around their release cadence instead of your own calendar.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>We hold ourselves to the same standard. Zovos publishes its model providers, version history, and change log to every customer console, so your diligence file is already filled in.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.prnewswire.com/news-releases/norm-ai-raises-120-million-at-a-1-2-billion-valuation-led-by-khosla-ventures-to-deliver-the-full-stack-model-for-legal-ai-302819152.html">Norm Ai raises $120M at a $1.2B valuation (company announcement)</a></li><li><a href="https://techcrunch.com/2026/07/07/ai-law-startup-norm-raises-120m-hits-unicorn-valuation/">AI law startup Norm raises $120M, hits unicorn valuation</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>The Warsh Fed opens with a hold and five words on inflation</title>
    <link href="https://zovos.ai/radar-warsh-first-hold.html" />
    <id>https://zovos.ai/radar-warsh-first-hold.html</id>
    <published>2026-07-07T00:00:00Z</published>
    <updated>2026-07-07T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>After April's four-way split, Kevin Warsh's first meeting produced a unanimous 12–0 hold and a sharply pared-back statement. One day later, the strait that started the inflation scare reopened.</summary>
    <content type="html"><![CDATA[<p>The FOMC held its target range at 3.50–3.75% on June 17. It was the first decision of the Kevin Warsh era, and it was unanimous. April had produced a four-way dissent, the widest split on the committee in years, so a 12–0 vote was itself the headline. The new chair opened with consensus instead of a pivot.</p>
<p>The statement read differently too. It was sharply shorter than the committee’s recent releases, and the customary forward-guidance paragraph was gone. In its place was this: “Inflation remains elevated relative to the Committee’s 2 percent goal, in part reflecting supply shocks that have driven price increases in certain sectors, including energy. The Committee will deliver price stability.”</p>
<h2>April versus June</h2>
<table><caption>Two meetings and one rate: how the committee moved</caption><thead><tr><th></th><th>April 28–29</th><th>June 16–17</th></tr></thead><tbody><tr><td>Decision</td><td>Hold at 3.50–3.75%</td><td>Hold at 3.50–3.75%</td></tr><tr><td>Vote</td><td>Four-way dissent</td><td>12–0, no dissents</td></tr><tr><td>Chair</td><td>Jerome Powell · final meeting</td><td>Kevin Warsh · first meeting</td></tr><tr><td>Statement</td><td>Customary length</td><td>Sharply pared back</td></tr></tbody></table>
<blockquote><p>Five words, “The Committee will deliver price stability,” replaced the paragraph of forward guidance markets usually parse line by line.</p></blockquote>
<h2>The shock started unwinding a day later</h2>
<p>The committee decided with May’s 4.2% CPI print on the table and the Strait of Hormuz still effectively closed. On June 18, one day after the decision, a U.S.–Iran memorandum of understanding reopened the strait. Brent crude averaged $85 per barrel in June, down $22 from May and $32 from the April peak, per the EIA. The supply shock the statement cites began reversing almost immediately after the vote.</p>
<p>For bank balance sheets, the message is symmetrical patience. The statement acknowledged that “economic activity is expanding at a solid pace despite elevated uncertainty that owes, in part, to the conflict in the Middle East.” A unanimous hold in front of a reversing energy shock shows a committee content to let the data settle before the July 28–29 meeting.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Keep the no-change path as your ALCO base case through the summer. A unanimous committee moves slower than a divided one.</li><li>Re-run your energy-shock deposit and credit scenarios in reverse. The unwind changes borrower cash flow assumptions too.</li><li>Note the communication shift in your rate-outlook minutes. Shorter statements mean fewer signals between meetings, and more weight on each data release.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos drafts the rate-environment narrative for your ALCO minutes from the primary record, including statement diffs. Each draft is timestamped, sourced, and ready to review.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.federalreserve.gov/newsevents/pressreleases/monetary20260617a.htm">FOMC statement, June 17, 2026</a></li><li><a href="https://www.federalreserve.gov/monetarypolicy/fomccalendars.htm">FOMC meeting calendar, 2026</a></li><li><a href="https://www.eia.gov/pressroom/releases/press590.php">EIA Short-Term Energy Outlook, July 7, 2026</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>CAMELS gets its first rewrite since 1996</title>
    <link href="https://zovos.ai/radar-camels-rewrite.html" />
    <id>https://zovos.ai/radar-camels-rewrite.html</id>
    <published>2026-07-07T00:00:00Z</published>
    <updated>2026-07-07T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>The FFIEC proposal drops the Management component's 'special consideration,' strips reputation risk, and puts material financial risk first. Comments close August 17.</summary>
    <content type="html"><![CDATA[<p>On May 19 the FFIEC proposed the first comprehensive revision of the Uniform Financial Institutions Rating System, the CAMELS framework, since December 1996 (FDIC FIL-23-2026 and 91 FR 29128). Adopted in 1979 and last updated three decades ago, the rating system behind every safety-and-soundness exam is finally on the operating table, and the comment window closes August 17.</p>
<p>The headline change is to the Management component. The proposal “would remove the sentence directing examiners to give ‘special consideration’ to the Management component in the composite rating,” and rewrites the component’s definition and evaluation factors. As Comptroller Jonathan Gould put it, the Management rating has historically “reflected deficiencies already captured in other components.” The proposal recasts it as a standalone assessment.</p>
<h2>What the proposal actually changes</h2>
<p>Beyond Management, the proposal changes the treatment of specialty-review findings, and revises the composite rating definitions. In the agencies’ words, it would also “emphasize consideration of material financial risks over concerns related to policies, procedures, and documentation.” That last sentence is the philosophical core. Ratings would be anchored to financial condition instead of how the paperwork looks.</p>
<p>UFIRS / CAMELS · the long arc</p>
<h2>Reputation risk exits the framework</h2>
<p>The proposal also “would remove all references to reputation risk, consistent with the policies of the Board, OCC, FDIC, and NCUA.” It lands inside a larger campaign. An OCC/FDIC final rule prohibiting reputation-risk-based supervisory criticism took effect June 9 (91 FR 18279, responding to Executive Order 14331). On June 2 the FDIC, OCC, and Federal Reserve announced they had scrubbed reputation-risk references from 14 interagency guidance documents (FIL-27-2026).</p>
<blockquote><p>The philosophical core of the rewrite is ratings anchored to material financial risk instead of paperwork. That is the part worth a comment letter.</p></blockquote>
<p><strong>What this means for your bank</strong></p>
<ul><li>Read the proposed Management-component definition against your last report of examination. If your M rating leaned on findings already reflected elsewhere, the rewrite is your argument.</li><li>File a comment by August 17 (Docket OCC-2026-0562). Community-bank voices are underrepresented in ratings-methodology dockets.</li><li>Update policy and risk-register language that still cites reputation risk as a standalone supervisory category. The interagency documents it referenced have changed.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos diffs the proposed CAMELS definitions against your latest exam-prep materials and drafts a comment letter grounded in your own findings. You review it, edit it and file it.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.fdic.gov/news/financial-institution-letters/2026/proposed-revisions-uniform-financial-institutions-rating">FDIC FIL-23-2026: Proposed revisions to UFIRS</a></li><li><a href="https://www.federalregister.gov/documents/2026/05/19/2026-09944/uniform-financial-institutions-rating-system">Uniform Financial Institutions Rating System, 91 FR 29128</a></li><li><a href="https://www.fdic.gov/news/financial-institution-letters/2026/agencies-remove-references-reputation-risk-interagency">FDIC FIL-27-2026: Reputation-risk references removed</a></li><li><a href="https://www.occ.gov/news-issuances/news-releases/2026/nr-occ-2026-39.html">Comptroller Gould statement, May 19, 2026</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>The 1071 rule lands at 1,000 loans, and the clock is already counting</title>
    <link href="https://zovos.ai/radar-small-biz-1071.html" />
    <id>https://zovos.ai/radar-small-biz-1071.html</id>
    <published>2026-07-07T00:00:00Z</published>
    <updated>2026-07-07T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>The revised small-business lending rule raises the reporting threshold tenfold and sets one compliance date: January 1, 2028. Your 2026–27 origination counts decide whether you are covered.</summary>
    <content type="html"><![CDATA[<p>The CFPB’s revised Section 1071 small-business lending rule was finalized May 1 (91 FR 23530), took effect June 30, and sets a single compliance date of January 1, 2028. The structural change is the threshold. A lender is covered only if it originated at least 1,000 covered credit transactions in each of two consecutive calendar years. That is ten times the 2023 rule’s 100-loan trigger.</p>
<p>The rule’s reach narrows in kind as well as count. Farm Credit System lenders are excluded from coverage outright, and merchant cash advances, agricultural lending, and small-dollar transactions drop out of the covered-transaction definition. The discretionary data points are removed from the collection. They were application method, application recipient, denial reasons, pricing information, and number of workers.</p>
<h2>What survives the revision</h2>
<p>Despite the tenfold threshold increase, the Bureau estimates the revised rule still captures 92 to 93 percent of small-business loan volume at depository institutions, versus roughly 94 to 95 percent under the 2023 rule. Coverage concentrates in the highest-volume lenders rather than disappearing.</p>
<table><caption>The 2023 rule vs. the 2026 revision</caption><thead><tr><th></th><th>2023 final rule</th><th>2026 revised rule</th></tr></thead><tbody><tr><td>Coverage threshold</td><td>100 covered originations</td><td>1,000 in each of 2 consecutive years</td></tr><tr><td>Farm Credit System</td><td>Covered</td><td>Excluded</td></tr><tr><td>MCAs · ag · small-dollar</td><td>In scope</td><td>Carved out</td></tr><tr><td>Discretionary data points</td><td>Collected</td><td>Removed</td></tr><tr><td>Depository loan volume covered</td><td>~94–95%</td><td>~92–93%</td></tr></tbody></table>
<blockquote><p>The two-consecutive-year lookback means coverage is decided before compliance begins. The 2026 and 2027 origination counts are the test, and 2026 is half over.</p></blockquote>
<h2>The quiet urgency</h2>
<p>A 2028 compliance date reads like runway, but the lookback inverts it. Whether you are a covered financial institution on January 1, 2028 depends on origination counts you are generating right now. A community bank near the 1,000-loan line needs a defensible count of covered transactions for 2026 before it can even decide whether to build. The count has to follow the rule’s definition instead of your core system’s loan codes.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Count 2026 originations against the rule’s covered-transaction definition now, including the exclusions, and document the methodology.</li><li>If you are near the threshold, brief the board on the build-versus-monitor decision this quarter instead of waiting for 2027.</li><li>Keep fair-lending fundamentals independent of 1071 coverage. ECOA risk does not switch off below 1,000 loans.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos runs your loan tape against the revised covered-transaction definition and produces the documented count. The coverage question is then settled by evidence instead of an estimate.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.federalregister.gov/documents/2026/05/01/2026-08494/small-business-lending-under-the-equal-credit-opportunity-act-regulation-b">Small Business Lending under ECOA (Regulation B), 91 FR 23530</a></li><li><a href="https://www.federalregister.gov/documents/full_text/text/2026/05/01/2026-08494.txt">Rule full text (Federal Register)</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>An OCC consent order maps the BaaS failure pattern</title>
    <link href="https://zovos.ai/radar-cfsb-consent-order.html" />
    <id>https://zovos.ai/radar-cfsb-consent-order.html</id>
    <published>2026-07-07T00:00:00Z</published>
    <updated>2026-07-07T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>Payments volume at Community Federal Savings Bank grew faster than its controls. Every fintech-partner bank should read the detail about the alert-triage system that auto-closed what it should have escalated.</summary>
    <content type="html"><![CDATA[<p>The OCC’s consent order against Community Federal Savings Bank of Woodhaven, New York (AA-ENF-2025-21, executed April 24 and released May 21) is a case study in a pattern examiners now look for on sight. It shows a small institution whose payment-processing business grew dramatically while its BSA/AML program stood still. The order cites violations of the BSA compliance-program rule (12 C.F.R. § 21.21), suspicious-activity reporting requirements, and Section 314(a) information-sharing obligations.</p>
<p>The findings read like a checklist of fintech-partner risk. Since 2020 the bank “significantly grew its payment processing line, relative to its size,” including cross-border activity with foreign financial institutions, but it “failed to develop and maintain controls and risk management processes commensurate with its risk and growth.” Customer due diligence was found ineffective, independent testing weak, BSA staffing thin, and internal audit missed all of it.</p>
<h2>The detail that should stop you</h2>
<p>The most instructive finding is about automation. The bank ran an automated alert-triage system, but “several deficiencies in its logic, data, and methodology resulted in the system auto-closing alerts that should have been escalated for further review. As a result, the system auto-closed a very high percentage of all ingested alerts.” A misconfigured automated control became an automated failure at scale.</p>
<blockquote><p>A triage model that auto-closes what it should escalate has stopped monitoring. It has become a suppression program with good intentions.</p></blockquote>
<h2>The order’s clock</h2>
<table><caption>Key remediation deadlines in the order</caption><thead><tr><th>Deadline</th><th>Requirement</th></tr></thead><tbody><tr><td>15 days</td><td>Board compliance committee of 3+ members, mostly non-employee directors</td></tr><tr><td>90 days</td><td>Written action plan to the OCC for non-objection (Articles V–X)</td></tr><tr><td>Per plan</td><td>Independent consultant engaged for a SAR look-back review</td></tr><tr><td>60 days after look-back</td><td>Consultant’s report on the look-back due</td></tr></tbody></table>
<p>Two things the order does not do are also worth noting. It imposes no civil money penalty, and it states expressly that its findings are “based on concerns largely unrelated to customers involved in digital assets activities.” This is a story about controls. It is not a story about crypto.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Validate your alert-triage and auto-close logic against escalation outcomes. Sample the closed queue as well as the worked one.</li><li>Tie BSA staffing and monitoring capacity to payments volume with a written trigger, so growth forces a program review automatically.</li><li>Refresh CDD on payment-processing and fintech-program customers until you can state each one’s business and expected activity in a sentence.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos benchmarks your alert auto-close rate and escalation outcomes against your transaction growth, and flags the divergence examiners flagged here before your exam finds it.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.occ.gov/static/enforcement-actions/eaAA-ENF-2025-21.pdf">Consent order AA-ENF-2025-21: Community Federal Savings Bank</a></li><li><a href="https://www.occ.gov/news-issuances/news-releases/2026/nr-occ-2026-40.html">OCC enforcement actions, May 2026 (NR 2026-40)</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Core PCE runs 3.4% as the saving rate touches 3.0%</title>
    <link href="https://zovos.ai/radar-may-pce.html" />
    <id>https://zovos.ai/radar-may-pce.html</id>
    <published>2026-07-07T00:00:00Z</published>
    <updated>2026-07-07T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>The Fed’s preferred gauge confirms the CPI story from the other side. It shows an energy-led headline, a firmer core than CPI shows, and a consumer saving less to keep spending.</summary>
    <content type="html"><![CDATA[<p>May’s PCE price index, the Fed’s preferred inflation measure, was released June 25. It rose 0.4% on the month and 4.1% year-over-year, with core PCE up 0.3% and 3.4% respectively. The shape matches the CPI story, with an energy-driven headline over a far quieter core. But note the level. Core PCE at 3.4% sits meaningfully above core CPI’s 2.9%, a reminder that the Fed’s own gauge shows less progress.</p>
<p>The consumer detail matters more for deposit-takers. Personal income rose 0.7% ($181.6 billion) and spending rose 0.7% ($156.1 billion). Real spending was flat, though, and the personal saving rate fell to 3.0%, with saving at $704.2 billion. Households are absorbing the energy shock by saving less while they keep spending.</p>
<h2>The May consumer ledger</h2>
<table><caption>Personal income and outlays · May 2026</caption><thead><tr><th>Measure</th><th>May 2026</th></tr></thead><tbody><tr><td>PCE price index</td><td>+0.4% m/m · +4.1% y/y</td></tr><tr><td>Core PCE (ex food &amp; energy)</td><td>+0.3% m/m · +3.4% y/y</td></tr><tr><td>Personal income</td><td>+0.7% m/m</td></tr><tr><td>Real PCE (spending)</td><td>0.0% m/m</td></tr><tr><td>Personal saving rate</td><td>3.0%</td></tr></tbody></table>
<blockquote><p>A 3.0% saving rate is the deposit story hiding inside the inflation release. Households are paying for gas out of their savings.</p></blockquote>
<h2>Why it matters for your balance sheet</h2>
<p>A falling saving rate is a leading indicator for deposit growth, because the flows that build consumer balances are the first casualty of an energy squeeze. Paired with flat real spending, it argues for conservative deposit-growth assumptions through the second half. That holds even as the energy unwind takes pressure off the headline.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Trim second-half deposit-growth assumptions and watch average consumer balances monthly instead of quarterly.</li><li>Treat core PCE at 3.4%, rather than core CPI at 2.9%, as the number the Fed is staring at when you draft the rate outlook.</li><li>Date-stamp the saving-rate observation in ALCO minutes. If deposit growth softens later, the contemporaneous record shows you saw it.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos ties macro releases to your deposit-concentration reports automatically, so a national saving-rate turn maps straight onto your own funding profile.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.bea.gov/news/2026/personal-income-and-outlays-may-2026">Personal Income and Outlays, May 2026</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Hormuz reopens and Brent sheds $22 in a month</title>
    <link href="https://zovos.ai/radar-hormuz-reopens.html" />
    <id>https://zovos.ai/radar-hormuz-reopens.html</id>
    <published>2026-07-07T00:00:00Z</published>
    <updated>2026-07-07T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>A June 18 U.S.–Iran memorandum ended the closure that drove the spring inflation spike. The unwind is in motion, and the EIA now sees pump prices falling through year-end.</summary>
    <content type="html"><![CDATA[<p>The supply shock that pushed May’s CPI above 4% is unwinding. On June 18, a U.S.–Iran memorandum of understanding ended the conflict that had kept the Strait of Hormuz effectively closed since late February, and shipping traffic through the strait has increased since. Brent crude averaged $85 per barrel in June, according to the EIA’s July outlook. That is down $22 from May and $32 below the April peak.</p>
<p>Pump prices lag crude, so the consumer relief arrives on a delay. The EIA projects retail gasoline averaging $3.80 per gallon in the third quarter, down from $4.21 in the second, with further declines toward year-end.</p>
<h2>The round trip, in one chart</h2>
<p>Brent crude · 2026 reference points ($/b)</p>
<blockquote><p>The shock arrived through the gas pump and the wire room at the same time. The unwind will leave through both, on different clocks.</p></blockquote>
<h2>What the unwind changes for banks</h2>
<p>For credit, an energy retreat eases the household cash-flow squeeze that was starting to show in transaction patterns. For AML programs, it is the mirror image of the spring. Monitoring thresholds re-baselined for energy-driven volatility will need re-tuning again as volumes normalize, or yesterday’s calibration becomes today’s blind spot. Year-over-year comparisons also stay distorted well into 2027. June’s level is calmer, but it is still far above last summer’s.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Revisit the AML monitoring thresholds you adjusted for the spike. Normalization needs the same documented re-tuning the shock did.</li><li>Refresh borrower stress assumptions for energy-sensitive commercial customers. The relief is real but arrives with a lag.</li><li>Keep the April–June price path in your ALCO record. It is the cleanest recent example of a supply shock your scenario library should hold.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos tracks the calibration history of your monitoring thresholds against the macro record, so the re-tuning trail is documented before an examiner asks for it.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.eia.gov/pressroom/releases/press590.php">EIA Short-Term Energy Outlook, July 7, 2026</a></li><li><a href="https://www.federalreserve.gov/newsevents/pressreleases/monetary20260617a.htm">FOMC statement, June 17, 2026</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Sonnet 5 ships near-frontier agents at commodity prices</title>
    <link href="https://zovos.ai/radar-sonnet-5.html" />
    <id>https://zovos.ai/radar-sonnet-5.html</id>
    <published>2026-07-07T00:00:00Z</published>
    <updated>2026-07-07T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>Anthropic’s June 30 release narrows the gap to its flagship at a fraction of the price. Falling model prices are exactly how models get swapped underneath your vendors.</summary>
    <content type="html"><![CDATA[<p>On June 30 Anthropic released Claude Sonnet 5, describing it as “built to be the most agentic Sonnet model yet.” For a bank, the claim that matters is the price tag more than the benchmark chart. Sonnet 5 lists at $3 per million input tokens and $15 per million output, with introductory pricing of $2/$10 through August 31, while Anthropic says its “performance is close to that of Opus 4.8, but at lower prices.”</p>
<p>Near-flagship capability at mid-tier prices changes vendor economics overnight. Every software vendor with an AI feature now has a strong financial incentive to swap the model underneath it. Most vendor contracts let them do exactly that without telling you.</p>
<h2>Why a cheaper model is a compliance event</h2>
<p>A model swap inside a vendor product changes behavior you may have validated, such as alert-triage thresholds, document summaries and customer-facing language. The May consent order against Community Federal Savings Bank showed what a miscalibrated automated triage system costs. A silent model change is how a calibrated system becomes a miscalibrated one without anyone deciding anything.</p>
<blockquote><p>Falling frontier prices are a feature for your budget and a bug for your change management. The cheaper the swap, the more often it happens.</p></blockquote>
<p><strong>What this means for your bank</strong></p>
<ul><li>Ask every AI-bearing vendor which model and version is in production for your instance, and log the answer. Repeat the question quarterly.</li><li>Put model-change notification into new and renewing vendor contracts. A swap that changes output behavior is a change-management event.</li><li>Re-run your validation samples after any disclosed model change, and date the results in the vendor file.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos keeps the model-version log for every AI vendor in your inventory and flags the ones that have gone a quarter without an attestation. The record manages the swap risk, so you are not relying on trust.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.anthropic.com/news/claude-sonnet-5">Introducing Claude Sonnet 5, June 30, 2026</a></li><li><a href="https://www.occ.gov/static/enforcement-actions/eaAA-ENF-2025-21.pdf">Consent order AA-ENF-2025-21: Community Federal Savings Bank</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Inflation crosses 4% on an energy shock, but the core stays quiet</title>
    <link href="https://zovos.ai/radar-inflation-4pct.html" />
    <id>https://zovos.ai/radar-inflation-4pct.html</id>
    <published>2026-06-12T00:00:00Z</published>
    <updated>2026-06-12T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>A Strait of Hormuz disruption did what tariffs couldn't. It also handed the next Fed chair a two-sided problem.</summary>
    <content type="html"><![CDATA[<p>May's Consumer Price Index rose 0.5% on the month to 4.2% year-over-year, the fastest annual pace since April 2023. Yet strip out food and energy and core inflation held at just 2.9%, a sign the surge is a supply shock rather than broad overheating. Energy alone drove more than 60% of the monthly gain, with gasoline up 40.5% over the year.</p>
<p>The trigger was geopolitical rather than domestic. A disruption to shipping through the Strait of Hormuz pushed crude sharply higher in late spring, and the pass-through to pump prices was almost immediate. Tariff policy, long expected to be the inflationary wildcard of 2026, turned out to be a sideshow next to a classic oil shock.</p>
<h2>Where the price pressure actually sits</h2>
<p>The headline figure hides a sharp divergence by category. Energy is doing nearly all the work. Shelter and core services are the components the Fed watches most closely for persistence, and they remain close to target.</p>
<p>CPI component change · year-over-year</p>
<blockquote><p>A contained core keeps the Fed patient rather than punitive. The headline number is a borrower problem before it is a policy one.</p></blockquote>
<h2>What it means for the Fed</h2>
<p>With the FOMC holding at 3.50–3.75% and a four-way dissent on the record, the committee is signalling that a supply-driven spike does not by itself justify renewed tightening. The June 16–17 meeting, the first under incoming Chair Kevin Warsh, is widely read as another hold. For banks, the risk is the volatility between meetings more than a rate move.</p>
<p>For deposit-takers, an energy-led squeeze on household budgets tends to show up first in transaction patterns. Balances thin out, small-dollar activity becomes more frequent, and payment-adjacent fraud ticks up measurably as consumers feel cash-flow strain. That mix inflates AML alert volume without changing the underlying risk picture. It is exactly the kind of noise that drowns a small compliance team.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Re-baseline AML monitoring thresholds for energy-driven transaction volatility so fuel-price swings don't inflate your false-positive queue.</li><li>Stress-test deposit assumptions against a sustained headline-CPI scenario, separate from your rate-path assumptions.</li><li>Document the macro rationale in your next ALCO and BSA committee minutes. Examiners reward a contemporaneous record.</li></ul>
<p>The takeaway is to calibrate without alarm. A 4.2% print is uncomfortable, but a 2.9% core says the underlying economy is not running hot. The institutions that fare best this cycle will be the ones that separate the signal from the shock and adjust their controls to the difference.</p>
<p><strong>From Zovos AI</strong></p>
<p>Our AML monitoring models were re-tuned this month for energy-driven transaction volatility. If you are an existing customer, the update is live in your console.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.bls.gov/news.release/cpi.nr0.htm">Consumer Price Index, May 2026 release</a></li><li><a href="https://www.federalreserve.gov/newsevents/pressreleases/monetary20260429a.htm">FOMC statement, April 2026</a></li><li><a href="https://www.bls.gov/news.release/empsit.nr0.htm">Employment Situation, May 2026</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Personal Financial Data Rights enters its first compliance tier</title>
    <link href="https://zovos.ai/radar-open-banking.html" />
    <id>https://zovos.ai/radar-open-banking.html</id>
    <published>2026-06-12T00:00:00Z</published>
    <updated>2026-06-12T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>The open-banking rule advances even amid ongoing litigation. Here's what tier one actually requires, and the clock you're now on.</summary>
    <content type="html"><![CDATA[<p>The CFPB's Personal Financial Data Rights rule, the agency's implementation of Section 1033 of the Dodd-Frank Act, has cleared its first compliance checkpoint despite a pending legal challenge. For community banks and credit unions, the headline is simple. Open banking is no longer a future scenario to monitor. It is something you have to build.</p>
<p>At its core, §1033 gives consumers the right to access and share their financial data with third parties of their choosing. It also obligates the institutions that hold that data to make it available through secure, standardized interfaces. The rule deliberately steers the market away from credential-based screen scraping toward authenticated, permissioned APIs.</p>
<h2>The tiered timeline</h2>
<p>Compliance phases in by asset size. The largest institutions go first, and smaller depositories get more runway. That runway is not idle time. The build, vendor selection, and authorization plumbing all need to start well ahead of your own deadline.</p>
<p>§1033 compliance tiers · by asset size</p>
<blockquote><p>The model provider behind your new data-access layer is now a vendor you must risk-rate. Examiners are already treating it that way.</p></blockquote>
<h2>What tier one requires</h2>
<p>Even institutions still years from their own deadline should treat the tier-one requirements as the reference architecture. The capabilities below are what a compliant data-sharing program looks like in practice.</p>
<p><strong>Readiness checklist</strong></p>
<ul><li>Consumer data-access APIs. Provide standardized, authenticated endpoints for the covered data fields, with no credential sharing.</li><li>Authorization &amp; consent logging. Keep a durable, scoped and time-bound record of who was granted access, to what, and when.</li><li>Third-party sharing governance. Apply diligence and ongoing oversight to the data recipients and aggregators in your ecosystem.</li><li>Revocation on demand. Consumers can withdraw access at any time, and your systems must honor it promptly and verifiably.</li></ul>
<h2>What to do now</h2>
<p>The litigation creates uncertainty about the edges of the rule, but its direction is clear. Treating a delay as a reprieve is the expensive mistake. Inventory the covered data you hold, map it to your core and digital-banking vendors, and put the third-party providers who will touch consumer data into your formal risk-rating process today. That is the work that takes the longest and that examiners will ask about first.</p>
<p><strong>From Zovos AI</strong></p>
<p>Zovos maps your §1033 covered-data inventory to your vendor stack automatically and flags every data recipient that belongs in your third-party risk program. The longest part of the build can then start on day one.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.consumerfinance.gov/rules-policy/final-rules/required-rulemaking-on-personal-financial-data-rights/">Personal Financial Data Rights rule</a></li><li><a href="https://www.fincen.gov/boi">FinCEN: Beneficial Ownership guidance</a></li><li><a href="https://www.federalreserve.gov/supervisionreg/srletters/SR2304.htm">SR 23-04: Third-party risk management</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Beneficial ownership stays narrowed to foreign entities</title>
    <link href="https://zovos.ai/radar-beneficial-ownership.html" />
    <id>https://zovos.ai/radar-beneficial-ownership.html</id>
    <published>2026-06-12T00:00:00Z</published>
    <updated>2026-06-12T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>The interim Corporate Transparency Act scope holds, and your CDD procedures need to say so before your next exam.</summary>
    <content type="html"><![CDATA[<p>FinCEN's interim rule narrowing the Corporate Transparency Act's beneficial-ownership reporting to foreign-formed entities remains in force. Domestic companies and their U.S. owners are, for now, outside the BOI reporting regime. That is a meaningful contraction from the original rule's sweep of millions of small businesses.</p>
<p>For a bank, the change is less about who files with FinCEN and more about what your own customer due-diligence procedures assume. Manuals written to the original scope now over-reach, and manuals written before the CTA under-reach. Either way, the document an examiner opens should match the rule as it stands today.</p>
<h2>What changed</h2>
<table><caption>Original CTA scope vs. the interim scope now in force</caption><thead><tr><th></th><th>Original CTA scope</th><th>Interim scope · in force</th></tr></thead><tbody><tr><td>Covered entities</td><td>All domestic reporting companies</td><td>Foreign-formed entities only</td></tr><tr><td>U.S. beneficial owners</td><td>U.S. beneficial owners reported</td><td>U.S. persons exempt from reporting</td></tr><tr><td>Filer population</td><td>~32M entities in initial estimate</td><td>Sharp reduction in covered filers</td></tr></tbody></table>
<blockquote><p>A narrower rule is a different obligation, even if it is not a lighter one. Your procedures have to name it.</p></blockquote>
<h2>Re-papering your CDD</h2>
<p>The beneficial-ownership rule for banks' own customers is distinct from the CTA filing regime, but examiners will expect your program to reflect the current legal landscape coherently. Treat the items below as a documentation pass. They do not call for a system overhaul.</p>
<p><strong>Re-paper checklist</strong></p>
<ul><li>Update the scope language. State the interim foreign-entity scope explicitly in your CDD/BOI procedures, with the effective date.</li><li>Reconcile customer onboarding. Confirm your account-opening forms and CIP flows still collect what the bank rule requires, independent of CTA.</li><li>Brief frontline staff. Make sure tellers and lenders are not citing the superseded broad-scope guidance to customers.</li><li>Log the change. Record the procedure revision in your BSA committee minutes so the timeline is auditable.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos diffs your live CDD manual against the current rule text and drafts the redline. Re-papering becomes a review instead of a rewrite.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.fincen.gov/boi">FinCEN: Beneficial Ownership Information</a></li><li><a href="https://www.fincen.gov/resources/statutes-and-regulations/cdd-final-rule">Customer Due Diligence (CDD) Final Rule</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>AI vendors land inside third-party risk scope</title>
    <link href="https://zovos.ai/radar-ai-vendor-risk.html" />
    <id>https://zovos.ai/radar-ai-vendor-risk.html</id>
    <published>2026-06-12T00:00:00Z</published>
    <updated>2026-06-12T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>The model provider behind your new tool is a vendor you must risk-rate. Examiners are already treating it that way.</summary>
    <content type="html"><![CDATA[<p>The interagency third-party risk guidance was written to be technology-neutral, and examiners are now applying it exactly that way. If an AI model or its provider touches a banking process, it belongs in your vendor inventory and your risk-rating workflow. The novelty of the technology does not create an exception. It raises the bar.</p>
<p>The wrinkle with AI is the supply chain. A single customer-facing feature can ride on a model provider, a cloud host, and a software vendor that stitches them together. Those are three distinct relationships, and each has its own concentration, data-handling, and continuity profile.</p>
<h2>The AI vendor layers</h2>
<table><caption>Inventory by layer · suggested risk tier</caption><thead><tr><th>Layer</th><th>Suggested tier</th></tr></thead><tbody><tr><td>Model provider: the frontier-AI lab behind the underlying weights and API</td><td>Critical</td></tr><tr><td>Cloud / inference host: where the model runs and your data transits</td><td>Critical</td></tr><tr><td>Application vendor: the product that wraps the model into a workflow</td><td>Elevated</td></tr><tr><td>Fine-tuning / data partner: anyone who sees your data to adapt a model</td><td>Elevated</td></tr></tbody></table>
<blockquote><p>One AI feature is rarely one vendor. It is a stack, and the guidance expects you to see all of it.</p></blockquote>
<h2>Adding AI to the inventory</h2>
<p>You do not need a new framework. You need to run your existing third-party process across a category most inventories missed. Start with the AI you already use, including the tools that arrived inside other products.</p>
<p><strong>This quarter</strong></p>
<ul><li>Discover the shadow AI. Inventory every model, embedded feature, and pilot, including the ones procurement never saw.</li><li>Risk-rate the provider as well as the app. Push diligence through to the model and host underneath the product.</li><li>Pin versions and log changes. Model snapshots shift between exams, so record which version is in production and when it moved.</li><li>Map concentration. Flag where one provider sits under multiple critical processes. That is your single point of failure.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos auto-discovers the AI and model providers already in your stack, tiers them against your criticality criteria, and keeps the version log current. You build the inventory once and it stays current.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.federalreserve.gov/supervisionreg/srletters/SR2304.htm">SR 23-04: Third-party risk management guidance</a></li><li><a href="https://www.ffiec.gov/">FFIEC: examination resources</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Fed holds at 3.50–3.75% amid a four-way dissent</title>
    <link href="https://zovos.ai/radar-fed-hold.html" />
    <id>https://zovos.ai/radar-fed-hold.html</id>
    <published>2026-06-12T00:00:00Z</published>
    <updated>2026-06-12T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>Powell's final meeting laid bare a committee that no longer agrees on the path. It also handed his successor an open question.</summary>
    <content type="html"><![CDATA[<p>The FOMC left its target range unchanged at 3.50–3.75% in Jerome Powell's final meeting as chair. The decision was never really in doubt. What made the meeting notable was the dissent. Four members broke from the majority in three different directions, the widest split on the committee in years.</p>
<p>The disagreement is less about today's data than about how to read an energy-driven inflation spike sitting on top of a still-firm labor market. One camp wants insurance cuts before growth softens. Another worries that easing into a supply shock re-anchors expectations the wrong way.</p>
<h2>How the room split</h2>
<table><caption>FOMC positions · 12 voting members</caption><thead><tr><th>Position</th><th>Lean</th><th>Votes</th></tr></thead><tbody><tr><td>Hold</td><td>Majority</td><td>7</td></tr><tr><td>Cut 25 bp</td><td>Dove</td><td>3</td></tr><tr><td>Cut 50 bp</td><td>Dove</td><td>1</td></tr><tr><td>Hike 25 bp</td><td>Hawk</td><td>1</td></tr></tbody></table>
<blockquote><p>For banks, the bigger risk is the volatility in the months of disagreement before the next rate decision.</p></blockquote>
<h2>What it means for your balance sheet</h2>
<p>A hold keeps deposit costs where they are for now, but a visibly divided committee widens the range of plausible paths into the back half of the year. The June 16–17 meeting, the first under incoming Chair Kevin Warsh, is read as another hold, yet the market will price every speech in between. That is exactly the environment in which a static ALCO assumption set quietly goes stale.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Refresh ALCO rate scenarios to include a genuine no-change path alongside the cut and hike cases. The dissent makes all three live.</li><li>Hold deposit-pricing discipline. A divided Fed is not a signal to chase rate, and re-pricing is hard to unwind.</li><li>Document the rate outlook your committee actually used, and date it. Examiners reward a contemporaneous record over a tidy one.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos drafts the rate-environment narrative for your ALCO and BSA minutes from the primary record. Each draft is timestamped, sourced, and ready to review.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.federalreserve.gov/newsevents/pressreleases/monetary20260429a.htm">FOMC statement, April 2026</a></li><li><a href="https://www.federalreserve.gov/monetarypolicy/fomccalendars.htm">FOMC meeting calendar, 2026</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Payrolls add 172K, beating expectations</title>
    <link href="https://zovos.ai/radar-payrolls.html" />
    <id>https://zovos.ai/radar-payrolls.html</id>
    <published>2026-06-12T00:00:00Z</published>
    <updated>2026-06-12T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>A firm labor market gives the Fed room to keep its focus squarely on prices, and it keeps the soft-landing case alive.</summary>
    <content type="html"><![CDATA[<p>Nonfarm payrolls rose 172,000 in May, comfortably ahead of the roughly 145,000 economists expected, while unemployment held at 4.1% and wage growth ran at 3.9% year-over-year. After an energy-driven inflation scare, the labor data is the reassuring half of the picture. Demand for workers is cooling gradually without cracking.</p>
<p>The composition matters as much as the headline. Hiring concentrated in healthcare and government, with cyclical sectors flat to soft. That is the pattern of a late-cycle labor market that is durable but no longer broad.</p>
<h2>Where the jobs came from</h2>
<p>Payroll change by sector · thousands</p>
<blockquote><p>A firm jobs print is what lets the Fed treat the inflation spike as a shock to wait out rather than a fire to fight.</p></blockquote>
<h2>Why it matters for your bank</h2>
<p>A resilient labor market underpins consumer credit quality and supports deposit stability, and both are good news for community balance sheets. But the narrowing breadth is the signal to watch. When hiring leans on healthcare and government, a downturn in your local cyclical employers can hit your loan book before the national numbers turn.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Map your commercial book against local sector exposure. Manufacturing and construction soften first.</li><li>Hold current deposit-stability assumptions. The data does not yet warrant a runoff scenario, but date the call.</li><li>Keep CRA lending targets on track. A firm labor market is the window to make the community-reinvestment numbers.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos ties macro releases to your concentration reports automatically, so the sectors driving the national number map straight onto your own exposure.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.bls.gov/news.release/empsit.nr0.htm">Employment Situation, May 2026</a></li><li><a href="https://www.bls.gov/ces/">Current Employment Statistics: sector detail</a></li></ul>]]></content>
  </entry>
  <entry>
    <title>Anthropic closes financing above OpenAI and files to go public</title>
    <link href="https://zovos.ai/radar-anthropic.html" />
    <id>https://zovos.ai/radar-anthropic.html</id>
    <published>2026-06-12T00:00:00Z</published>
    <updated>2026-06-12T00:00:00Z</updated>
    <author><name>Adam Swenson</name></author>
    <summary>A reported $965B valuation and a confidential IPO filing show how fast frontier-AI capital is consolidating into a few hands.</summary>
    <content type="html"><![CDATA[<p>Anthropic closed a financing round at a reported $965B valuation and filed confidentially for an IPO. The round clears OpenAI's last private mark and, for now, puts Anthropic at the front of the frontier pack. Whatever the exact number proves to be, the direction is unmistakable. The capital and capability behind generative AI are pooling into a very small number of providers.</p>
<p>For a community bank, none of this is a market-timing question. It is a concentration question. The models that increasingly sit inside your vendors' products are produced by a handful of firms. That handful is exactly where third-party and continuity risk concentrate.</p>
<h2>The frontier, by valuation</h2>
<table><caption>Reported private valuations · $ billions</caption><thead><tr><th>Provider</th><th>Valuation</th><th>Note</th></tr></thead><tbody><tr><td>Anthropic</td><td>965</td><td>Reported round</td></tr><tr><td>OpenAI</td><td>~850</td><td>Last private mark</td></tr><tr><td>Google DeepMind</td><td>n/a*</td><td>Held inside Alphabet</td></tr><tr><td>Others (combined)</td><td>n/a</td><td>Remaining frontier firms</td></tr></tbody></table>
<blockquote><p>When the whole frontier fits on one hand, vendor concentration stops being a footnote and becomes the headline risk.</p></blockquote>
<h2>Why a bank should care</h2>
<p>A public Anthropic or OpenAI means more disclosure, more scrutiny, and more stability in the providers your vendors depend on. That is broadly good for diligence. But it also cements a market structure where a small set of firms underpins a growing share of banking technology, and where an outage, price change, or policy shift at one of them ripples across your stack at once.</p>
<p><strong>What this means for your bank</strong></p>
<ul><li>Map which of your critical vendors share an underlying model provider. That shared provider is your real concentration, more than the length of the vendor list.</li><li>Ask vendors for their model-provider continuity and fallback plans, and keep the answers on file.</li><li>Treat a provider's IPO disclosures as free diligence material, and read the risk factors into your vendor file.</li></ul>
<p><strong>From Zovos AI</strong></p>
<p>Zovos traces every vendor in your inventory down to the model provider underneath, so concentration across the frontier takes one report instead of a research project.</p>
<p><strong>Sources</strong></p>
<ul><li><a href="https://www.cnbc.com/2026/06/01/microsoft-and-google-take-on-anthropic-and-openai-in-ai-coding-models.html">Coverage of the frontier-AI capital race</a></li><li><a href="https://pricepertoken.com/news/model-releases">Model release tracker</a></li></ul>]]></content>
  </entry>
</feed>
