Bureaucracy Times

The Hospital Built on a Document That Never Existed

In September 2026, the Department of Veterans Affairs Office of Inspector General published a review of the new VA medical center in Louisville, Kentucky, a hospital that Congress authorized in 2010 and that, as of this writing, still is not open. The current completion estimate is November 2027. That puts the project at thirteen years behind its original schedule, sixteen years past its congressional authorization, and about $700 million over its 2007 cost estimate of $418.8 million. The bill now stands at more than $1.1 billion.

None of that is the interesting part. Federal construction runs late; everyone involved has made peace with it. The interesting part is what the OIG found when it went looking for the document that was supposed to justify all of it, the “business case” that federal budget rules require agencies to submit to the Office of Management and Budget before spending real money on a capital project. VA never submitted one. Not a bad one, not an outdated one. None. The OIG’s entire review of thirteen extra years and $700 million in overruns had to be built on a draft business case from 2007 that VA itself says was abandoned when the project got left out of the fiscal year 2009 budget request. The department spent nineteen years building a hospital against a plan that was never finished and never approved, and then acted surprised when the OIG asked to see the paperwork.

A Billion Dollars, Zero Documentation

Under OMB Circular A-11, a business case is not a formality. It is the instrument that establishes a project’s cost, schedule, and performance goals, the baseline against which everyone (Congress, OMB, and eventually inspectors general) is supposed to measure whether the government got what it paid for. VA’s executive director of the Office of Asset Enterprise Management confirmed to the OIG, on the record, that no business case for Louisville was ever submitted to OMB. Because VA could not produce one, the OIG did the only thing it could do under the Inspector General Act, classifying the entire $1.17 billion in project obligations as a questioned cost, meaning money spent without adequate supporting documentation to justify it.

VA’s defense, offered in its official response, is that the business case “was not required” because Louisville funding did not make it into the fiscal year 2009 budget request. This is the bureaucratic equivalent of explaining that you never filed a permit application because the building got built before you got around to filling out the form. The OIG did not buy it, noting plainly that being left out of one year’s budget cycle does not relieve a department of its ongoing obligation to maintain a supportable basis for a billion-dollar decision. VA also leaned on the fact that the Army Corps of Engineers has managed construction execution since 2015, arguing that anything that went wrong afterward was the Corps’ problem, not VA’s. The OIG’s response to that one is worth quoting for the sheer bluntness of it; the mandated construction services provided by the Corps do not absolve VA of its own responsibility to approve and report changes and account for costs. In plain terms, VA does not get to outsource the paperwork along with the construction.

The Books Do Not Add Up, and Nobody Told Congress

The missing business case would be a bureaucratic embarrassment on its own. What makes it worse is that VA also cannot accurately tell Congress what the project has actually cost. The congressionally approved cost ceiling, set in fiscal year 2023, is just over $1.013 billion. The OIG’s own reconciliation of VA’s accounting systems found $1.17 billion in actual obligations and pending user costs, once you add in $43.4 million in advance planning charges, $76.6 million in Army Corps management fees, and $40 million in unreported “user-requested changes” (design fixes for sterile processing, mental health space, and interventional radiology that must happen before the hospital can even open) that never made it into the reported total. That is a discrepancy of nearly $160 million, comfortably past the 10 percent threshold that federal rules say requires notifying Congress that a project has blown through its authorized ceiling. VA did not send that notice. It also missed two consecutive quarterly cost reports to Congress that are legally required under 38 U.S.C. § 8120 for any project over $100 million, a category Louisville has occupied for well over a decade.

Layered on top of the money problem is a change-control problem. VA’s internal process requires anything altering a project’s scope, schedule, or cost by more than 10 percent to be signed off by the Secretary and a body called the Construction Review Council. The OIG found five major change requests on this project. Two of the three that should have gone to the Secretary or the Council never got that approval. Four of the five were missing at least one required signature. In one memorable stretch documented in the report, a design contractor was told in May 2013 to build the new hospital as a shared structure with a Veterans Benefits Administration office, then in August was ordered to stop and redesign around an entirely new atrium concept, then was formally suspended in October and not cleared to resume until the following February. That is 288 days of paid design work thrown out for a change nobody ran through the approval process, on a project that did not have years to spare.

Sixteen Years of Warnings the Department Had Already Heard

If any of this sounds familiar, that is because GAO told VA the same story more than a decade ago. In an April 2013 report examining VA’s largest medical-facility projects at the time (Denver, Las Vegas, Orlando, and New Orleans), GAO found cost increases ranging from 59 to 144 percent and schedule delays averaging nearly three years, driven by the same failures the Louisville OIG report identifies now (inadequate planning, unmanaged scope changes, and a construction management structure that could not keep pace with its own decisions). Congress held hearings. GAO made recommendations. VA implemented some of them. And Louisville, which had already been under construction for years by the time that 2013 report came out, went on to rack up cost increases north of 170 percent anyway.

The environmental review process alone cost the project years it did not have to lose. VA had planning funds available to start environmental assessments before its 2010 budget authorization and used them for a feasibility study, but let initial design work sit idle for lack of funding and did not award its first environmental assessment contract until ten months after authorization. The agency then spent a year deciding whether to pursue a lighter environmental assessment or a full environmental impact statement, chose the lighter path, and got burned for it: in 2015, the assessment’s own contractor concluded a “finding of no significant impact” was not supportable and warned that proceeding anyway would leave VA exposed to litigation. VA pivoted to the full impact statement, which was not finalized until 2017, by which point a nearby community had already sued to block the project outright, adding roughly three more years of delay before a federal court ruled in VA’s favor.

Seven recommendations came out of this review, and VA concurred with all of them, which is what agencies do when there is no plausible way to disagree. Target completion dates stretch out to May 2027, conveniently just before the hospital itself is supposed to open. The OIG says it will keep the recommendations open until VA proves it actually fixed things. Given that this department was already living through nearly identical GAO findings when ground had barely broken on this project, there is no particular reason to expect the sixth recommendation letter to land any differently than the first.
Fediverse reactions
An Electric Griddle Cost $54 Million, According to the Federal Government

The Federal Bureau of Prisons wants Congress to believe it has a plan for the five billion dollars it just received, three billion of which is earmarked for hiring and retaining staff under Public Law 119-21. To have a plan, an agency needs to know what it owns, what that equipment costs to keep running, and what it will cost to replace. The BOP has a system for tracking exactly that. It is called the Total Maintenance System, and according to a new DOJ Inspector General audit, it once recorded that a single electric griddle, placed into service in 2017, had racked up more than fifty four million dollars in maintenance costs. The actual figure was about four thousand dollars, a rounding error’s rounding error, off by a factor of roughly thirteen thousand. (See “Audit of the Federal Bureau of Prisons’ Acquisition and Life Cycle Management of Major Equipment Supporting Food Services,” Report 26-100, September 2026.)

BOP officials told auditors this was a manual input error, which is technically true in the way that every clerical mistake is technically true. The more interesting question is why nobody caught it. The griddle sat in the system, presumably serene in its fictional status as one of the more expensive appliances in the federal government, until an outside auditor happened to ask.

The System of Record That Nobody Trusted Enough to Use Correctly

TMS exists to give BOP leadership a reliable inventory of the more than 5,700 pieces of major food service equipment spread across 118 institutions, so the agency can plan replacements and budget accordingly. When a new asset is entered, the system automatically builds a maintenance schedule and lets staff log work orders, labor, and material costs against it. In principle this is exactly the kind of system that should make a five billion dollar hiring and infrastructure infusion easier to spend well.

In practice, auditors compared TMS records against physical equipment at two institutions and found the data barely resembles reality. At FMC Lexington, the system listed 58 major food service items; fourteen more were in actual use but never entered at all, meaning no maintenance plan or cost tracking existed for them. Of the items that were listed, the assigned condition codes were wrong across the board; eighteen items were coded as “obsolete or inoperable” when only one actually was, while items genuinely falling apart were logged as merely fair or poor. At FCC Butner, auditors found the reverse problem in miniature; eighteen items on the books could not be located at all, and six more had been quietly replaced or retired without anyone updating the record. Officials blamed manual data entry, thin quality assurance, and a general lack of training on how to use the system, which is a polite way of describing an inventory that functions mostly as folklore.

None of this is abstract. The BOP is currently paying to rent 168 mobile refrigeration units and off-site cold storage across 52 institutions, at a cost of more than nine million dollars over six years, because its own refrigeration units are too often broken to trust with food that inmates are legally entitled to eat safely. At FCC Butner alone, six years of rental and off-site storage cost about $1.93 million, roughly $729,000 more than simply buying new freezer storage would have cost. That is not a rounding error. That is a spreadsheet nobody opened.

A Definition Problem Dressed Up as a Data Problem

The deeper issue, which the griddle merely dramatizes, is that the BOP has never settled on what “major food service equipment” means. A 2012 Central Office memo defines it one way, the 2023 Facilities Operations Manual defines it another way, and institution-level staff apply a third, broader definition that includes ice machines, mixers, and exhaust hoods nobody at headquarters considers major at all. Since the entire replacement-planning apparatus, TMS included, depends on knowing which assets even count, an agency that cannot define its own equipment cannot be expected to track its cost with any precision. The griddle’s fifty four million dollar phantom debt is what happens when a system built on a shaky definitional foundation also lacks the basic supervisory review to catch an extra six zeros.

The Bureau’s official response, dated September 15, 2026, is a tidy stack of bureaucratic present-perfect tense (standards issued, certifications scheduled to begin October 1, training “planned” for fiscal year 2027, a Capital Investment Plan that reaches all the way out to 2031). The BOP requested that the OIG close two of the five recommendations outright. The OIG agreed to close exactly one, the definitional standard, and left the other four open until it sees actual documentation that the certifications happened, the training occurred, and the refrigeration units got replaced rather than merely scheduled. Bureaucracy Times has covered this instinct before; an agency describes its own promises as accomplishments and asks the watchdog to take its word for it. The OIG, to its credit, did not.

Where the Money Actually Goes While Nobody Is Counting

This audit lands squarely inside the piece we have been building on the BOP’s $5 billion supplemental funding under P.L. 119-21, and it sharpens the stakes considerably. Three billion of that money is meant for hiring and retaining Food Services and Facilities staff, the same staff who, according to this report, often lack basic training in the very system meant to track the equipment they are hired to maintain. Auditors found Facilities personnel at FCC Butner who did not know how to enter routine work orders into TMS and instead filled out paper forms for a supervisor to input on their behalf. That is not a training gap so much as a training absence, extending back years, by the Bureau’s own account, due to lack of budget.

Congress is being asked to trust that an agency will spend its new money wisely, on the strength of a system that once believed a griddle cost more to maintain than most small businesses are worth. The BOP says the fix is coming. The OIG’s response, essentially, is: show us the paperwork first, and this time make sure someone checks the math.
Fediverse reactions
The Red Tape Roundup — October 11, 2026
A Note from the Editor

Social media has always befuddled me.

The last social media platform that I really understood was MySpace, and I readily admit that I really don’t know why I got MySpace to begin with. I was a soldier at the time, so it may have been as simply as someone asking,

“Are you on MySpace?”

I didn’t do much with it though. I remember spending a great deal of time figuring out which song I wanted on my profile, and I settled on “So Cold” by Breaking Benjamin. That song defined my life at that time, and by many measures it still does.

But beyond that song, I don’t remember “using” MySpace for anything.

Now, Facebook was different. I used it for only two things: playing Farmville and birthday reminders. But as a social media platform, I didn’t see the point. I mean, people were posting pictures of themselves, or their food, or a restaurant they were about to eat at, or their feet. It all seemed so stupid to me, and I didn’t see the point of it all.

Why would I want to “check in” at an Olive Garden? I didn’t really want anyone to know where I was, except for those people who were with me when I went somewhere. I also didn’t see the point of updating my status whenever I went or did something different than my last status update. It just seemed weird to me.

I haven’t been on MySpace since I updated the song on my profile. And I left Facebook in 2018 after a dead friend of mine sent me a friend request.

I hung out on Twitter for a while, before it was X, but it was just madness. I arrived on the tweeting scene in 2015 and was done with it by 2017. However, it was during that time when I learned about concepts like “posting into the void” and platform algorithms. I had no idea how easy it was to post every single day, spend hours crafting a post that someone might notice, only to go unnoticed in a sea of hundreds of thousands of users. Sure, I didn’t really know how to post things, or what hashtags were for, and when my teenagers would say “hashtag” anything I thought they sounded #stupid.

I figured that maybe someone would be interested in what I was posting or commenting. But, alas, I received almost no responses, except for a bunch of beautiful people who had 0 followers and followed thousands of Tweeters, and who also had made no posts. I didn’t know what people meant by the word “bot”, and it is likely that I had 100% bots in my cozy little circle. So, I left Twitter behind.

Now, you may be asking yourself, “what is the point of all this?” Why am I talking about something that you definitely know more about than I ever will? Well, I’ll tell you.

When I first had the idea for what would become bureaucracy.news, I knew that I wanted to report on the bureaucracy, the machine, the leviathan. I saw that most people were believing and regurgitating whatever their preferred media channel told them to say, and it became easy to determine which talking heads whispered in their ears by the buzz words and phrases they repeated ad nauseum.

Few people, it seemed to me at the time, were not looking for the answers to their questions, or worse, they weren’t asking any questions at all. They believed everything they heard from their trusted news sources, without question. And that bothered me. No longer did we discuss anything, we just yelled berating and unholy epithets at each other from across the social media universes.

So, I decided to just report on the information that the government published about itself, regardless of who was in office, and I certainly don’t care if it’s about good or not so good things. If the government mucks something up, I say it. If they do something positive, I say it. But I wanted more than anything for the people to have the information that they were too lazy to verify. And I don’t mean that as an insult, but just the reality of life.

To gain a wider reach for my articles and investigation, I knew that I would have to return to social media. Bureaucracy Times started with just a website and an X account.

I learned quickly that gaining traction on X was like starting a diesel engine in the arctic…it takes time. And even after months passed, I had gained little forward momentum on X. So, I started looking for other platforms.

I went to Bluesky because I read somewhere that most of the good journalists who left Twitter landed there. It took me a while to figure things out, but it only took a couple weeks before someone actually “liked” one of my posts. That was a good day.

A couple months after landing on Bluesky, I decided to enter a platform at the opposite end of the political spectrum: Truth Social. I’ve been there for nearly two months now, and I still haven’t received one like. And the only upvotes I received were my own…I was just experimenting.

But, I did get banned from Truth Social twice, and that was a hoot and a half! I wasn’t even mad because it gave me a sense of pride in some weird way. I mean, someone, or some bot, had to have read my articles, right? Why else would I get banned shortly after posting something? It doesn’t really matter. It’s just another platform that has a unique algorithm that scores accounts based on what they post, how they engage, and how often they’re on the platform after posting.

So, to bring it full circle, social media is a necessary evil to my mind. I don’t care for it, but it really has become the replacement for the old public square where ideas were shared and debated. And if I’m being honest, I’d rather be in an actual town square surrounded by every type, kind, and age of person, and engage in discussion…in person.

But I will say one thing. I have definitely seen an exponential increase in engagement with my writing over these last few months. When I first launched bureaucracy.news, I may have gotten 2 engagements per week. This past week, we had hundreds. So, there is something to say for being consistent and persistent.

I started reading declassified files, OIG reports, and legislative nonsense simply to put the information out there. Most normal people won’t spend time digging through a Federal Register that consistently exceeds 600 pages, looking for anything interesting. Most Americans don’t subscribe to over 80 newsletters from government agencies, waiting for inspector general reports to tattle on the agencies they overwatch. But I do, and so does the small crew of editors and writers who support this site.

We don’t do it for the money, primarily because we’re not making any. We have other jobs that pay us, which allows us to come together a couple times a week to read and discuss FOIA responses, decide which articles to write, and then edit whatever we can throw together. And all of this happens in our off time!

We’re just happy readers are showing up!

This Week’s Most-Read

The numbers are in. Here’s what you were reading this week:
Coming Up Next Week

A look at what’s heading your way next week:

An Electric Griddle Cost $54 Million, According to the Federal Government

The Bureau of Prisons paid a price tag that would make any home cook weep, and the OIG wants to know how it happened.

The Hospital Built on a Document That Never Existed

A VA construction project moved forward on the authority of paperwork that auditors couldn’t find — because it was never created.

America Runs on Stolen Cooking Oil. The Government Tracks the Fuel, But Who Tracks the Grease?

Used cooking oil has become big money in the renewable fuel market, and someone figured out the oversight gaps before regulators did.

From the Investigative Desk

The Watchdog, the Chatbot, and the Question Nobody Seems to Be Asking

The VA Office of Inspector General has quietly begun integrating AI tools into its investigative and audit workflows. We know this because the OIG said so — briefly, in budget justification language buried in appropriations documents most people never read.

What they haven’t said is much else.

They haven’t said which tools. They haven’t said what data those tools are accessing. They haven’t said whether veterans’ personally identifiable information (medical records, claims data, service histories) is being routed through third-party AI systems. And they haven’t said who approved any of it.

This isn’t a story about AI being bad. It’s a story about a government watchdog adopting a powerful new capability with almost no public accounting for how it’s being used, what guardrails exist, and whether the people it’s supposed to protect have any say in the matter.

We filed a FOIA request with the VA OIG asking for any policies, guidance documents, or memoranda governing the use of AI in audit and investigative work. The clock is running.

In the meantime, we’ve been reviewing what AI governance frameworks exist across the federal government, from OMB’s guidance to agency-specific policies, and comparing them against what the OIG’s own budget language actually implies.

The gap is significant.

What we’re trying to answer: Does the VA OIG have written policies governing its use of AI tools in active investigations. And if so, why haven’t they been made public?

FOIA Watch

A status update on our active FOIA requests:

GSA — AI Procurement Records: Filed September 22. Request covers procurement documents, vendor contracts, and internal communications related to GSA’s acquisition of AI tools for federal agency use. Acknowledged. Awaiting document review.

VA OIG — AI Governance Policies: Filed October 3. Requesting any written policies, directives, or guidance documents governing the use of artificial intelligence in VA OIG audit and investigative operations. Acknowledged. No documents produced.

Richmond VA Medical Center — Patient Safety Incident Reports: Filed September 28. Requesting incident reports and corrective action plans related to environment-of-care deficiencies cited in recent OIG inspection reports. Pending acknowledgment.

DOE — Grid Modernization Contract Communications: Filed October 1. Requesting internal communications related to contract awards under the Grid Resilience and Innovation Partnerships program. Pending acknowledgment.

The government runs on paperwork. So do we. The filing cabinets remain undefeated.

On Our Radar

A few things that haven’t become stories. Yet.

DOT’s Airline Subsidy Math Doesn’t Add Up
The Essential Air Service program subsidizes flights to remote communities. But a growing number of routes are subsidized at rates that exceed the cost of simply flying passengers first class on commercial carriers. Nobody in the department seems to think that’s a problem worth revisiting.

The FTC’s Quiet Warning on Healthcare Pricing
The Federal Trade Commission issued a report last month flagging anti-competitive pricing practices in hospital and pharmaceutical markets. It got almost no coverage. The practices it described are ongoing.

America.gov: Still Worth Watching
We tested it a few weeks ago and it performed better than expected. Since then, we’ve noticed the results getting less consistent. We’re not ready to call it a regression, but we are watching.

Until next week —

hannotek, Editor @ Bureaucracy.News
Amtrak Was Born a Fiction, and Fifty Years Later Nobody Has Fixed It

A For-Profit Company Nobody Believed Would Turn a Profit

Every government corporation in this series has had to pretend, at some level, to be a real business. Amtrak is the only one where the pretending was written into the planning documents. When Congress drafted the Rail Passenger Service Act of 1970, internal analysis explicitly described the new National Railroad Passenger Corporation as a corporation organized for profit.

One of the planners, John McClellan, later admitted what everyone involved already knew: most of the planning team was dubious of the “for profit” claim, but neither the White House nor the more conservative members of Congress were willing to sign off on an entity that was set up from the start to be a perpetual ward of the state, according to an Eno Center for Transportation history of the Act’s drafting.

Amtrak began operating on May 1, 1971, taking over the common carrier obligations of private railroads that had been losing money on passenger service for decades, in exchange for the right to use those railroads’ tracks at incremental cost, according to the Federal Railroad Administration. It has never once turned a profit in fifty five years of operation, and the fight over whose fault that is has been running, essentially unchanged, for almost the entire time.

The Same Question, Asked Since 1979

GAO has been auditing Amtrak’s finances since the agency’s early years, and the title of its 1979 review says everything: Should AMTRAK’s Highly Unprofitable Routes Be Discontinued? By 1995, GAO was still laying out the same three options it always lays out: eliminate the subsidy and privatize the railroad, which GAO itself conceded was unlikely to work because no Amtrak route earns enough revenue to cover its own costs and few private firms would take on that risk; realign the national route network around the most cost effective corridors; or keep funding the whole thing and hope efficiency gains eventually close the gap.

They never have. By 1998, GAO found Amtrak had consumed roughly 21 billion dollars in federal operating and capital funding since 1971 while reducing its annual net loss only marginally, from 834 million dollars in fiscal year 1994 to 762 million in fiscal year 1997, with losses already projected to climb back toward 845 million the following year.

By 2020, cumulative federal subsidies to Amtrak had passed 50 billion dollars, according to a policy analysis from the Cato Institute — a figure that predates the 2021 infrastructure law’s further 66 billion dollars in rail funding, part of it going directly to Amtrak and part to state rail grants. No independent source has published a clean post-2021 cumulative total, in part because the infrastructure law’s Amtrak-specific allocations are disbursed over time and tracked separately from annual operating subsidies.

The 2025 to 2026 reauthorization debate is, structurally, the same conversation GAO was already having in 1979: current testimony from the Department of Transportation cites GAO findings that long-distance routes account for 15 percent of Amtrak’s riders but 80 percent of its financial losses, and calls once again for ending subsidies to underperforming long-distance service and separating Northeast Corridor infrastructure into its own governance structure.

The Ledger That Blames the Trains Nobody in Washington Rides

Here is where it gets genuinely strange, because Amtrak’s own numbers do not agree with themselves. Amtrak’s internal accounting system, called Amtrak Performance Tracking, assigned the Northeast Corridor a 352 million dollar above the rail profit in fiscal year 2025, while attributing a 622 million dollar loss to the long-distance inter-regional routes that serve the rest of the country, the same routes GAO and DOT keep flagging as the problem.

But a Trains Magazine analysis argues this allocation runs essentially backwards, and it quotes two former Amtrak chiefs to make the point. Former CEO Wick Moorman told Congress in writing that eliminating the entire long-distance network would actually increase Amtrak’s total loss and subsidy requirement by 435 million dollars a year, meaning those routes are net contributors once the Northeast Corridor’s fixed costs are honestly allocated rather than parked somewhere else in the ledger.

Former Amtrak President David Gunn reportedly went further, warning that if Congress ever gave Amtrak less than its full subsidy request, the railroad would have to close the Northeast Corridor before it touched the long-distance routes.

Whether or not you buy the full argument, the fact that Amtrak’s own former leadership and Amtrak’s own official accounting cannot agree on which half of the network is actually losing money, after fifty five years and one accounting system built for exactly this purpose, tells you something about how useful that accounting system actually is for anyone trying to make an honest funding decision.

It also tells you who benefits from the current framing. That is, the Northeast Corridor serves the members of Congress who appropriate Amtrak’s budget every year, and an accounting method that quietly shields it from scrutiny while pointing the finger at rural long-distance service is, at minimum, a very convenient place for the numbers to land.

Fifty Billion Dollars and Counting

Even the number Amtrak takes to Congress each year is a chosen number rather than a neutral one. Amtrak requests funding based on what it calls its adjusted operating loss, 598.4 million dollars in fiscal year 2025, a figure that specifically excludes roughly a billion dollars a year in depreciation, 364 million dollars in capital project planning costs, and hundreds of millions more in expenses that sit on the operating side of the ledger under ordinary accounting rules but that Amtrak has decided are not relevant to the number it wants Congress to see.

None of this makes Amtrak unique in wanting to look better on paper than it is. What makes it worth closing this series’ current stretch on is how openly the fiction was built in from day one. TVA and the RFC grew into unaccountable financial structures over time, as the incentives shifted. The FDIC‘s clean design cracked under a genuine stress test nobody had planned for.

Amtrak was chartered as a for-profit corporation by people who wrote down, at the time, that they did not believe it would be profitable, because admitting the truth would have meant admitting they were building a permanent federal dependent. Fifty five years, more than 50 billion dollars in direct subsidies before the 2021 infrastructure law, and one internal accounting system whose own former executives cannot agree with it later, that is exactly what they built.

Next in this series: the Pension Benefit Guaranty Corporation, the quiet federal backstop between millions of workers and the pension promises their employers could not keep.
Fediverse reactions
Fed Minutes Reveal AI Boom Is Becoming a Monetary-Policy Problem
The Federal Reserve once viewed artificial intelligence primarily as a potential productivity engine. Its latest meeting minutes show policymakers confronting another side of the boom: AI investment is contributing to inflationary pressures, enormous borrowing demands and higher costs across the economy.

The artificial-intelligence boom has grown large enough that the Federal Reserve is no longer merely wondering how much more productive it might make the American economy.

Officials are now considering how much inflation it might create along the way.

Minutes from the Federal Open Market Committee’s September 15–16 meeting show artificial-intelligence investment threaded through the Fed’s assessment of inflation, business investment, wages, corporate borrowing and even Treasury yields. Most significantly, some policymakers explicitly connected AI-related demand with the case for higher interest rates.

The committee unanimously raised the federal-funds target range by a quarter percentage point to 3.75 to 4 percent at the September meeting. All participants supported the increase, citing inflation that remained elevated, a labor market near full employment and an economy continuing to expand at a solid pace.

The rate increase itself was already known.

The minutes reveal considerably more about what was happening underneath it.

An AI boom with an inflation bill

Fed staff estimated that headline personal consumption expenditures inflation reached 3.8 percent in August, while core inflation remained at 3.4 percent.

The causes were not confined to the familiar suspects.

Staff attributed the increase largely to previous tariff increases, higher energy and input costs resulting from geopolitical developments and an increase in prices for technology-related consumer goods associated with the AI buildout.

FOMC participants went further.

They said surging AI-related investment was contributing to inflationary pressures and noted that effects from the AI buildout appeared to be increasing in core goods even as the effects of earlier tariff increases faded.

Businesses were also encountering higher transportation and input costs. Some policymakers warned that AI investment could become large enough for aggregate demand to outpace aggregate supply, creating additional upward pressure on prices.

That concern matters because the Fed is confronting an economy that has stubbornly refused to provide the traditional justification for easier monetary policy.

Unemployment fell to 4.1 percent in July and August. Payroll gains accelerated in August. Consumer spending strengthened. Business investment remained robust.

And once again, AI was part of the explanation.

Fed staff said the AI buildout was supporting substantial increases in business investment and fueling imports of high-tech capital equipment.

In other words, the same investment boom promising greater productive capacity tomorrow is adding demand to an already strong economy today.

From productivity story to policy consideration

That tension has become progressively more visible in the Fed’s public record.

Earlier this year, AI frequently appeared in Fed discussions as a source of potential productivity growth and economic disruption. By June, policymakers were discussing strong demand for AI infrastructure as a source of upward pressure on technology and electricity prices and considering whether unusually strong investment could contribute to persistent inflation.

By July, the Fed’s Monetary Policy Report was documenting rising prices for semiconductors and other data-center components alongside growing demand for industrial metals and AI-related manufactured goods.

The September minutes move the discussion another step forward.

Some participants worried that the longer inflation remains above the Fed’s 2 percent target, the greater the possibility that higher inflation becomes embedded in expectations and wage and price decisions. Others were concerned that AI-related demand could produce broader price pressures rather than remaining confined to technology markets.

Then comes perhaps the most consequential passage in the minutes.

A couple of participants said a higher policy rate would help prevent sector-specific price increases caused by energy disruptions and AI-related demand from spreading into more persistent inflation.

That does not mean AI caused the September rate hike. The minutes provide no basis for such a conclusion. Persistent underlying inflation, energy prices, geopolitical instability, tariffs and continued economic strength all figured into the committee’s deliberations.

But the minutes establish something more subtle and potentially more important: Federal Reserve policymakers are now explicitly considering AI-generated demand when determining how restrictive monetary policy needs to be.

AI is competing for capital, too

The effects are not confined to consumer prices.

The Fed’s market discussion points toward another consequence of the enormous sums being spent on AI infrastructure: competition for capital.

Treasury yields rose about 35 basis points across the two- to 10-year portion of the yield curve during the period between meetings. Higher expectations for monetary policy and strong economic data accounted for part of that increase.

But market commentary identified another factor: heavy private-debt issuance being used to finance AI infrastructure.

According to the minutes, that borrowing was contributing to competition for capital and was among the factors associated with higher Treasury term premiums and yields.

The scale is significant enough that the Fed separately discussed the corporate debt issued by AI “hyperscalers.” Yield spreads on that debt remained wide because of the large volume being issued and the relatively long duration of the securities.

At the same time, companies benefiting directly from AI infrastructure investment were outperforming the broader stock market.

The result is an unusual economic feedback loop.

AI companies and their partners spend heavily on data centers, chips, electricity infrastructure and other equipment. That investment supports economic growth and corporate earnings, but also increases demand for goods, skilled labor, energy and capital. Those pressures can raise prices and borrowing costs. Persistent inflation then gives the Federal Reserve reason to keep interest rates higher.

Higher rates, in turn, raise borrowing costs throughout the rest of the economy.

Housing provides a particularly stark contrast. While financing remained broadly available to larger businesses, the Fed described conditions as restrictive for mortgage borrowers and small businesses. Home-purchase borrowing remained depressed.

The AI investment boom, in other words, is occurring in an economy where access to capital is far from uniform.

Pay now, productivity later

None of this means the Federal Reserve believes AI will ultimately be bad for the economy.

Quite the opposite.

Participants generally expect AI investment to increase productivity and potential economic output in coming years. But they also acknowledged considerable uncertainty about the size and timing of those benefits. Some additionally warned about cybersecurity and other risks associated with rapid AI adoption that could offset productivity improvements in certain circumstances.

That creates the central paradox buried in the September minutes.

The American economy may eventually receive a substantial productivity dividend from artificial intelligence. But building the infrastructure necessary to produce that dividend requires enormous amounts of capital, equipment, energy and skilled labor today.

And the Fed has to conduct monetary policy in today’s economy, not the economy AI proponents expect several years from now.

Fed staff now expects inflation to decline gradually and finally reach the central bank’s 2 percent objective in 2029. Its inflation forecast for 2026 through 2028 was revised upward from July, while its outlook for economic activity and the labor market strengthened. Staff also concluded that inflation risks remained tilted to the upside.

Most FOMC participants consequently believed another rate increase would probably be appropriate before the end of the year, although they emphasized that future decisions would depend on incoming economic data.

The committee’s September statement summarized the situation much more simply: economic activity remained solid, capital investment was robust and inflation remained elevated.

The minutes released weeks later supply a detail missing from that abbreviated public account.

Artificial intelligence is no longer sitting somewhere off in the Fed’s economic forecast as a hypothetical future productivity revolution.

It is already showing up in prices, investment, corporate borrowing and financial markets.

And now it is showing up in the interest-rate discussion.

Sources
- FOMC Minutes — September 15–16, 2026 Meeting, Federal Reserve
- Federal Reserve — Monetary Policy, Federal Reserve
- Gov. Cook — An Update on AI and the Economy, Federal Reserve, Sep. 28, 2026
Fediverse reactions
Twenty Two Years, Three Audits, One Excuse.

The Social Security Administration runs a program that pays benefits to the teenage children of dead, disabled, and retired workers, provided those teenagers are still in high school. The mechanism that decides whether the checks keep coming is a single form, filled out by the student, certified by a school official, and reviewed by an SSA employee who is trusting both of them to be right. It is not a complicated system. It has also failed the same audit three separate times since 2004, for the same three reasons, with SSA agreeing to fix it on all three occasions.

A Teenager’s Signature Is Still the Control

Under the Social Security Act, a minor child of an insured worker loses benefits at 18 unless they qualify as a full time student, in which case payments continue until they graduate or turn 19, whichever comes first (42 U.S.C. §§ 402, 423). The instrument that governs this is Form SSA-1372, Advance Notice of Termination of Child’s Benefits. The student states their school, their attendance dates, and their expected graduation date; a school official signs off; SSA takes it from there.

There is no automated feed from any school system telling SSA when a kid drops out, transfers, or graduates a semester early. There is no real time check against enrollment records. There is a piece of paper, filled out months in advance, describing a future the student is predicting rather than reporting. The Office of the Inspector General’s newest audit (report 022515, released September 2026) exists because that paper, and the employees who process it, keep getting it wrong the same three ways, and this is the third time OIG has documented it happening.

2004: The Original Diagnosis

In an August 2004 review titled School Attendance by Student Beneficiaries over Age 18 (A-09-04-14013), OIG sampled 300 students out of a population of 254,121 and found $202,917 in incorrect payments and $56,065 in unsupported payments among them. Projected to the full population, that came to about $70 million in incorrect payments to 32,839 students and $39.5 million in unsupported payments to 10,312 students. The stated causes were that students and schools did not promptly report attendance changes, and that SSA did not retain the documentation needed to prove eligibility either way. SSA’s response was to promise additional employee training and a systems modification to stop paying benefits past the maximum age of entitlement, a related failure mode significant enough that OIG had already given it a separate audit of its own the same year.

2014: The Same Chart, Bigger Numbers

A decade later, OIG returned with Payments to Student Beneficiaries (A-09-13-13059, December 2014), sampling 275 students out of 1,539,078 who had received student benefits between 2007 and 2013. The estimate had grown to $225.3 million in overpayments to about 106,000 beneficiaries and $968 million in unsupported payments to roughly 246,000. The trade press covered it as a program in disarray, and the underlying diagnosis had not moved an inch from 2004. Students and schools were still not reporting attendance changes. SSA employees were still failing to retain evidence, and the agency’s own systems still weren’t recording graduation dates on the Master Beneficiary Record where an employee could see them. SSA’s corrective action, according to the background section of this year’s report, was to notify schools and organizations about the importance of timely reporting and remind its own staff to keep the paperwork. In practice, that was a memo.

2026: Reading the Same Homework Back to Itself

The current audit sampled 100 of 521,393 beneficiaries entitled to student benefits from January 2022 through December 2024. SSA correctly paid 71 of them. It got 17 wrong and could not document eligibility at all for 12 others, a documentation gap that on its own accounts for more projected dollars than the confirmed errors sitting next to it, an estimated $342 million in unsupported payments to 63,000 beneficiaries against $211 million in confirmed improper payments to 89,000.

Split the 17 error cases and the causes fall into the same two buckets OIG has now written up three times. Nine cases trace back to students or schools handing SSA outdated or simply wrong attendance information, the kind of error where a beneficiary reports an expected June graduation and then quietly leaves school the previous January, collecting five months of benefits nobody was still entitled to. The other eight trace back to SSA itself. In one, an employee typed a graduation date into the Master Beneficiary Record a full year earlier than what the student had actually reported, cutting off seven months of benefits the student should have received. In another, a beneficiary attending a full year school got their benefits terminated a month early because an employee applied the rules for a quarterly academic calendar instead, a distinction the agency’s own manual spells out clearly enough (SSA, POMS, RS 00205.325, C). In a third, SSA received written notice from a school that a student had graduated a month ahead of schedule and simply never acted on it.

The report closes with three recommendations. Fix the eight remaining attendance error cases. Fix the six remaining duration miscalculations. Identify why any of this keeps happening at all. SSA’s Chief Risk Officer replied that the agency agrees. That sentence, or one close enough to it, is now sitting in the file from 2004, from 2014, and from 2026.

What has never been sitting in that file, across three audits and twenty two years, is a system that checks a school’s actual enrollment against what a form predicted six months earlier, or a Master Beneficiary Record built so a graduation date gets flagged rather than typed in by hand and trusted. The dollar figures keep climbing because the beneficiary population keeps climbing, not because anyone at SSA found a new and interesting way to get this wrong. The agency has spent over two decades photographing the same crack in the same wall, filing the photograph, and calling the filing a corrective action plan.
Fediverse reactions
The VA Has a Three Day Rule for Specialty Care. Mental Health Waited Ten.

There is a certain bureaucratic poetry to the fact that the Veterans Health Administration’s own guidebook sets a three business day deadline for deciding whether a veteran can get more specialty care, and that the specialty most likely to blow past that deadline by the widest margin is mental health.

A new VA Office of Inspector General audit of “requests for services,” the paperwork mechanism community providers use to ask VHA for authorization beyond a veteran’s original referral, found that mental health requests took an average of ten days to decide, missing the three day standard 68 percent of the time.

Neurosurgery came in at nine days, missing the mark 49 percent of the time.

Cardiology averaged six days and missed 50 percent of the time.

These are not edge cases. They are three of the specialties where the cost of delay is measured in more than inconvenience.

The audit examined 2.6 million requests for services filed between October 2024 and January 2026 and found VHA met its own three-day standard just 17 percent of the time nationally. Buried inside that number, though, is a distribution that should worry anyone who thinks a national average tells the whole story.

A veteran waiting on an oil change delayed by a week is an inconvenience. A veteran waiting on a decision about a psychiatric hospitalization step down, a tumor resection, or a cardiac procedure delayed by a week or more is something else entirely, and OIG’s report does not shy from saying so.

The Ten Day Wait for a Mental Health Decision

Mental health’s ten day average and 68 percent miss rate are the worst of any specialty category OIG broke out in the report. That is worth sitting with, because “requests for services” in mental health typically means a provider has already begun treating a veteran and determined the original authorization does not cover what the veteran now needs, additional therapy sessions, an extended course of medication management, a step up in care intensity.

The request is not hypothetical. It describes a clinician, in the middle of active treatment, saying this patient needs more, now.

OIG’s report notes that delayed decisions on requests for services can result in delayed diagnoses, interrupted treatment, and worse health outcomes, and flags that three specific cases identified during the audit were serious enough to be referred to OIG’s Office of Healthcare Inspections for a dedicated review of potential clinical harm.

The report does not specify which specialties those three cases fell under, which is its own kind of answer. When the agency conducting the audit will not tell you, you are left to guess whether they involve the specialty averaging ten days and missing the standard on two out of every three requests, or one of the others. None of the options are comforting.

Neurosurgery and Cardiology Are Not Exactly Forgiving Specialties Either

Neurosurgery’s nine day average and 49 percent miss rate deserve the same scrutiny, if for different reasons. A request for services in a neurosurgical context typically means a provider needs authorization to proceed with something time sensitive, additional imaging following a concerning finding, a follow up procedure, an extended course of post-operative care. Waiting nine days on average for a paperwork decision, in a specialty where the cost of delay is frequently irreversible, is not a rounding error.

Cardiology’s numbers look almost better by comparison, six days on average and a coin flip miss rate, until you remember that cardiology is a specialty where “we will get back to you within the week” is not a phrase most clinicians would want said out loud to a patient with an active cardiac concern. VHA’s own field guidebook does not carve out faster timelines for these specialties.

The three day standard is the three day standard, mental health, neurosurgery, cardiology, or otherwise, and the audit found VHA cannot reliably meet it in any of them, with the categories carrying the highest clinical stakes performing among the worst.

What Happens Between the Request and the Decision

It is worth being precise about what a delayed decision actually means for a veteran in these specialties, because “administrative delay” undersells it. Until VHA authorizes the additional care, the community provider is in an uncomfortable position: continue treating the veteran without confirmed authorization, at the provider’s own financial risk, or pause care and wait.

OIG’s report notes that when these decisions and their notifications go missing or delayed, providers may keep delivering care that ultimately goes unauthorized and unpaid, which creates a disincentive to keep treating veterans through the gap rather than an incentive.

For a veteran in an active mental health crisis, a nine day wait for a neurosurgical follow up, or a cardiology patient hoping for a swift answer, that gap is not an abstraction. It is the interval in which a provider has to decide, unilaterally, whether to keep going and hope VHA eventually pays for it, or whether to pull back until the request clears. Neither option was supposed to exist. The three day standard exists specifically so this decision never has to be made by a provider guessing at VHA’s intentions.

Nothing in VHA’s response to this audit proposes a faster track for high acuity specialties. The agency concurred with all six of OIG’s recommendations, which is the standard bureaucratic gesture of agreement that commits the institution to eventually building better tracking and reporting tools, on a timeline stretching into July 2027.

There is no recommendation, and no indication in VHA’s response, that mental health, neurosurgery, and cardiology requests should be prioritized differently than a routine referral for physical therapy. The three day clock runs the same for all of them. It is simply ignored more often, and for longer, in the specialties where ignoring it costs the most.

A national average of 17 percent compliance is bad enough to justify an audit on its own. A breakdown showing that the worst performing categories happen to be the ones where a delayed decision can mean a missed diagnosis, an unmanaged psychiatric crisis, or a postponed cardiac intervention is the sort of detail that should reorder VHA’s priorities rather than simply add another line item to a corrective action plan.

Instead, the plan treats every specialty as interchangeable, a queue to be cleared eventually, with no acknowledgment that some queues carry more risk per day of delay than others. The veterans waiting in those three specialties are not waiting on a bureaucracy that does not know it has a problem.

They are waiting on one that knows precisely which categories are failing worst and has scheduled the fix for a year from now.
Fediverse reactions
The Agreement Washington Won’t Let Anyone Update

There is a particular kind of bureaucratic failure that doesn’t require anyone to be corrupt, lazy, or even wrong. It only requires two offices that disagree about who is allowed to fix something. The State Department’s Inspector General found exactly that arrangement sitting inside Embassy Guatemala City, in a report that spends most of its pages on the usual inventory of a mismanaged outpost (unregistered networks, overdue travel advances, a warehouse full of furniture nobody can account for) before landing on something more interesting.

An agreement the United States signed with a foreign government sits frozen because nobody in Washington will let anyone update it, alongside a set of legally required evaluations that nobody at post even knew they were supposed to conduct.

A Regional Hub Built From the Wreckage

Guatemala’s embassy was never a quiet posting. It sits on a 9.4 acre compound, serves a community of roughly 50,000 US citizens, and functions as a category 4 embassy, the State Department’s own term for a post carrying outsized political and economic weight in its region.

When USAID stopped implementing foreign assistance on July 1, 2025, following the Trump administration’s foreign aid review, the Bureau of Western Hemisphere Affairs designated Guatemala City as the regional assistance hub for Central America. The embassy inherited 18 legacy USAID projects worth $120.6 million and staffed the transition with three US direct-hire employees and five locally employed staff, a skeleton crew for a portfolio that size.

The report is candid about what that transition actually felt like from inside the building. Staff described incomplete and shifting guidance, unclear expectations about what a “regional hub” was even supposed to do, travel restrictions, and a steadily rising pile of administrative approvals. The OIG’s own prior work found that the Department’s Assistance Transition Working Group never built a strategic workforce plan to figure out how many positions the new arrangement actually needed, following the same key practices the Government Accountability Office has been recommending for years.

The Department’s last workforce strategic plan expired in 2023 and has not been replaced. So the hub was staffed by instinct rather than by plan, which is one way to run a $120 million portfolio, just not a durable one.

The Letter Nobody Is Allowed to Fix

Buried in the foreign assistance section is the finding that should worry anyone who cares about how the United States keeps its word. The Bureau of International Narcotics and Law Enforcement Affairs operates in Guatemala under a 2015 Letter of Agreement that still commits the US government to sectors, including community policing and justice sector reform, that INL quietly stopped funding years ago. Embassy staff told OIG they started drafting an update. Then, in January 2025, INL Washington told them to stop, pending further guidance that never arrived.

INL’s official response to this finding is a small masterpiece of institutional confidence. The bureau maintains its current activities technically fall within the scope of the old agreement and its modifications, even while conceding the document needs modernizing, and says it will renegotiate “at an appropriate time,” citing Guatemala’s 2027 general elections as a scheduling consideration. OIG’s reply does not buy the premise.

As the report notes, the agreement commits the US to activities INL no longer supports, which is precisely the risk the finding describes, and the embassy already did the preparatory work before Washington told it to sit down. The recommendation stays open until the Department produces an actual updated agreement, not a plan to eventually consider producing one.

The companion finding is worse, because it is a repeat offense. INL Guatemala never conducted the joint program evaluations required by that same 2015 agreement and its subsequent amendments, evaluations meant to happen annually, then quarterly, then biannually as the agreement was modified. Embassy staff simply didn’t know the requirement existed.

This is not INL’s first time getting caught here. OIG flagged the identical failure in a 2023 inspection, and the bureau’s fix at the time was a February 2024 cable instructing embassies to meet with counterparts and file an annual summary. Two years later, Guatemala’s INL staff still hadn’t produced documentation of a single formal joint evaluation, offering instead a description of regular but informal meetings under the High-Level Security Dialogue.

Regular conversation is not the same thing as a written evaluation measured against agreed metrics, and the Department’s own instruments say so in writing, which makes this less a lapse than a pattern the bureau has now failed to correct twice.

The Ledger of Small Failures

Once you get past foreign assistance, the report reads like a checklist of an embassy running on staff who are stretched too thin to double check anything. Twenty nine of 140 residential properties never received the seismic safety evaluation required for a country OBO itself rates as very high risk for earthquakes, a gap the embassy blames on management oversight rather than resources. Property management fared no better.

Some $315,000 in nonexpendable equipment, including $267,000 of IT hardware, moved from warehouse to office without the required transaction paperwork, while the furniture and appliance pool sat at nearly double the Department’s stock cap, with $89,000 in assets misclassified, including baby cribs and vacuums somehow coded as program furniture.

Fourteen chauffeurs blew past the 10 hour daily duty limit on 34 occasions across ten pay periods, a driver safety violation the embassy attributes to poor trip planning rather than any shortage of drivers.

INL itself ran up $115,000 in overdue travel advances, nearly all of it tied to an internal 90-day repayment habit that directly contradicts the Department’s 30-day standard, the same section that couldn’t produce its evaluation paperwork running its own informal exception to a different rule entirely.

The most quietly damning number in the whole report involves money the Department didn’t lose so much as fail to notice. Only one of the embassy’s five US direct-hire Diplomatic Technology positions was funded through International Cooperative Administrative Support Services, the mechanism that splits IT costs across the agencies who actually use the service, despite the embassy’s own estimate that a second position spends more than half its time on ICASS work.

The Department had been quietly absorbing costs that other agencies were supposed to share, to the tune of an estimated $219,000 over three years, not because anyone hid it, but because nobody at post knew the requirement to check existed.

It is the same root cause running through half the findings in this report: not fraud, not negligence in any dramatic sense, just an institution that never told the people doing the work what the rules actually required of them.

What the Concurrence Actually Buys You

Embassy Guatemala City concurred, or partially concurred, with all 11 recommendations, and OIG considers every one of them resolved, which in the audit world is a term of art meaning the parties agree on what should happen next, not that it has happened yet. The seismic assessments are still eight properties short of complete.

The FAP stock reduction target is still short of the Department’s cap, aimed for the end of September. The updated Letter of Agreement is not yet negotiated, and INL’s own timeline explicitly runs it past a foreign election it hasn’t happened yet.

Resolved, in other words, is a status the Department assigns to problems it has agreed to eventually stop having, which is a useful thing to remember the next time an agency’s press office announces that an inspector general’s findings have been addressed.

Sources: U.S. Department of State Office of Inspector General, Inspection of Embassy Guatemala City, Guatemala (ESP-25-01, 2026); Executive Order 14169, Reevaluating and Realigning United States Foreign Aid (January 2025).
Federal Register Watch: October 9, 2026
An executive order defers diesel fuel taxes by invoking a law written for hurricanes and terrorist attacks, not fuel-price spikes. That’s the most notable document in today’s 89-document Federal Register, and it’s one of six that cleared our bar for institutional or anomaly significance.
- Executive Office of the President — Executive Order 14435, signed October 5 and published today, invokes 26 U.S.C. 7508A, the law Treasury normally uses to push back tax deadlines after a hurricane, wildfire, or terrorist attack, to defer certain diesel fuel excise taxes through the end of the year because, in the order’s own words, “restricted global diesel supply has led to rising prices.” It also tells the IRS not to penalize truckers for burning dyed diesel on public roads through December 31. Dyed diesel is untaxed fuel meant only for farm equipment and generators, and running it through a highway truck normally triggers a separate penalty for dodging the federal highway tax, so this waiver is what actually puts the cheaper fuel within legal reach for truckers before the relief period ends. Reaching for a disaster-relief statute over a price problem, with no disaster declaration cited anywhere in the order, is a different kind of trigger than the law is usually built for. Read the order.
- Interior Department / Bureau of Ocean Energy Management — BOEM published the proposed notice of sale for Gulf of America Outer Continental Shelf Oil and Gas Lease Sale 4, the third sale held under the renamed program and the first whose specific terms, including size, timing, minimum bids, and royalty rates, are locked in by Section 50102 of the One Big Beautiful Bill Act rather than left to Interior’s ordinary rulemaking discretion. Under Section 19 of the Outer Continental Shelf Lands Act, affected states’ governors get a chance to comment on those terms before the final sale notice issues, which is effectively the public’s only formal input, through their governors, before the terms are set. Writing specific lease terms into a budget-reconciliation statute, instead of Interior’s standard five-year offshore leasing plan, moves that decision from agency rulemaking to a one-time congressional mandate. Read the notice.
- Nuclear Regulatory Commission — The NRC released a draft Environmental Impact Statement for Fermi America’s Combined License application to build four AP1000 reactors at its Project Matador campus in Texas, a complex envisioned as combined nuclear generation and an AI data center. A Combined License folds the construction permit and the operating license into one approval, so this comment period is essentially the public’s only chance to weigh in before both building and running the reactors are approved together. The NRC opened scoping on this project in March, so a draft EIS seven months later is a notably fast pace for four-reactor licensing, and a sign of how quickly the AI buildout is pulling new nuclear capacity through the federal licensing pipeline. Read the notice.
- Department of the Air Force — The Air Force will prepare a Supplemental Environmental Impact Statement to its 2023 review of the Sentinel intercontinental ballistic missile program, which is replacing the 1970s-era Minuteman III fleet at three Air Force bases and missile fields across five states. A supplemental EIS is required when an agency changes the “proposed action” a prior environmental review already covered, and today’s notice doesn’t say what changed, only that something did. Sentinel has already gone through one major statutory cost-and-schedule reset, so a second round of environmental review this far into the program is consistent with further changes to its scope, cost, or footprint. Read the notice.
- Interior Department — Interior finalized a new categorical exclusion covering “wintertime oil and gas exploration” in the National Petroleum Reserve in Alaska, adding it to the department’s internal NEPA handbook after the May proposal drew exactly one public comment. A categorical exclusion is a standing exemption: once it’s on the books, individual seismic-survey and exploratory-drilling projects that fit the category skip the normal environmental assessment or full impact statement process entirely, so that single comment was effectively the only outside scrutiny this category of Arctic drilling activity will get before project-level approvals start moving. Read the notice.
- Drug Enforcement Administration — DEA corrected its August order temporarily placing O-desmethyltramadol in Schedule I, saying the original text “inadvertently omitted” language extending the control to the drug’s salts and isomers. Temporary scheduling orders take effect immediately and carry criminal penalties for unauthorized possession, so a roughly two-month gap between what the order’s summary described and what its regulatory text actually controlled isn’t cosmetic. It’s the kind of drafting error that could have mattered to anyone handling one of the chemical’s salt or isomer forms before today’s fix. Read the correction.
Today’s edition reviewed all 89 documents published in the October 9, 2026 Federal Register. Excluded as routine: 12 Paperwork Reduction Act information-collection notices, 9 SEC self-regulatory-organization fee and rule filings, 11 advisory-committee and closed-meeting notices, 5 Sunshine Act meeting notices, 5 Foreign-Trade Zone production and subzone notices, 4 antidumping/countervailing duty administrative reviews, 7 routine FDA drug-approval and withdrawal notices, 3 medical-device classification notices, 3 Federal Reserve bank-holding-company notices, 3 DEA practitioner enforcement orders, 2 International Trade Commission case dispositions, 4 FERC filing notices, and 14 additional single-agency notices that raised no institutional or anomaly flag. We also reviewed, but did not include, a Treasury/IRS notice canceling a hearing on a pending proposed rule that would treat refunded tax credits as a federal public benefit restricted from non-qualified aliens, since the cancellation itself was procedural.
Fediverse reactions
Forty Six Percent of Alaska’s Village Water Systems Have Nobody Watching Them

Somewhere in Alaska in 2025, tribal members turned on a tap and got water contaminated with E. coli, a bacterium capable of causing gastrointestinal illness serious enough, in vulnerable people, to become life threatening. The cause was not a burst pipe or a natural disaster.

According to a new Government Accountability Office report on tribal water infrastructure, it happened because the utility did not have enough qualified personnel on staff to make sure its chlorination equipment was actually working (Government Accountability Office, GAO-26-107178).

This was not an isolated incident. It happened twice in 2025 alone, and it fits inside a much larger, quietly alarming statistic buried in the same report, that nearly half of Alaska Native village drinking water systems had no primary certified operator on staff during that same fiscal year.

The Job Nobody Explains Until Something Breaks

Water operators are, in the most literal sense, the reason a water system does what it is supposed to do after the ribbon-cutting ends. GAO’s report spells out exactly what that job entails, running the equipment, controlling the treatment processes, and monitoring the plants that make water safe to drink, while wastewater operators do the equivalent work removing pollutants before water is released back into the environment.

These are not entry level positions filled on a whim; operators need specialized training and must earn and maintain certifications tied to the specific complexity of the system they run, certifications that exist precisely because getting this work wrong has direct public health consequences.

A water system without a certified operator is not simply understaffed in the abstract sense that any workplace might be short a hand. It is a facility that treats and delivers drinking water without anyone certified to confirm it is doing so correctly.

That is the exact condition GAO found across a huge share of Alaska Native villages. Citing State of Alaska data, GAO reports that about 46 percent of Alaska Native village drinking water systems, 73 out of 157, did not have a primary water operator certified to the level required for that system on staff in fiscal year 2025.

That figure applies specifically to systems that were required to have a certified primary operator in the first place, meaning it is not padded by facilities too small to need one. Nearly half of the systems that were supposed to have a qualified person running them did not.

Why Nobody Stays

GAO and the State of Alaska both point to the same root cause, and it is not a mystery requiring further study. Rural utilities in Alaska experience high operator turnover, and IHS senior officials attributed that turnover directly to a lack of tribal funding for water operator salaries.

This is not a story about a shortage of qualified people willing to do specialized technical work in remote communities; it is a story about tribal water systems that, once built, frequently lack the money to pay the specialized staff needed to keep them running, so operators leave for jobs that pay better, and the system cycles through vacancy after vacancy. One utility, unable to afford the energy costs required to run its wastewater aeration system, simply stopped aerating its wastewater, a direct, documented consequence of an operating budget too thin to cover routine costs.

This turnover and funding problem sits at the center of one of the report’s core findings, that IHS generally does not fund routine operations and maintenance for the water systems it helps build.

IHS pays to construct the plant. It largely does not pay to keep qualified people running it afterward. The system gets built, the ribbon gets cut, and then the ongoing cost of the one thing that actually keeps water safe, namely a trained person watching the equipment, becomes the tribe’s problem alone, in communities that GAO’s own broader report describes as chronically underfunded relative to the tax base and financing options available to non tribal communities.

What an Empty Operator Position Actually Costs

GAO does not let this stay abstract. In 2025, two tribes experienced E. coli contamination in their water systems specifically because they lacked adequate operations and maintenance capacity, including not having enough qualified personnel on hand to ensure chlorination equipment was functioning properly.

E. coli contamination in a drinking water system is not a paperwork violation; it is a direct threat of gastrointestinal illness and, in vulnerable populations, more serious health outcomes. In a separate 2024 incident, a different tribe lacked enough wastewater utility operators to perform routine maintenance on a lift station, and when the pump inevitably failed, the result was prolonged sewage overflow.

These are not edge cases dredged up to make a point. They are what GAO explicitly identifies as the predictable consequence of a system where nearly half of a state’s tribal water utilities cannot keep a certified operator on staff, wired directly to a funding structure that pays for construction but not for the ongoing salaries needed to run what gets built.

The connection between the abstract 46 percent figure and an actual gastrointestinal illness outbreak is not speculative; it is the same causal chain GAO lays out explicitly, funding gap, operator turnover, unmonitored equipment, contamination event.

A Pilot Program, Finally Proposed

GAO’s response here goes further than most of its recommendations elsewhere in the report, because this is the one place where GAO does not simply ask an agency to fix its own paperwork. GAO suggests Congress consider authorizing and directing IHS, working with tribes and in collaboration with EPA, to establish a pilot program that would actually help fund tribes’ routine operations and maintenance costs, specifically things like water operator salaries and the energy costs needed to run treatment equipment.

It is worth noting what this recommendation implicitly concedes, that the current system, in which the federal government funds construction but not the staffing needed to safely operate what it built, is not working, and IHS itself has acknowledged its statutory authority does not currently extend to covering routine operations and maintenance costs at all.

A pilot program is a modest first step relative to the scale of the problem GAO documents. Forty six percent is not a rounding error or a temporary staffing hiccup; it is essentially a coin flip on whether any given Alaska Native village’s water system currently has a certified professional watching over it. Every one of those vacant positions is a system running, or not running, on borrowed time, waiting for the next equipment failure nobody catches until people start getting sick.

Source: U.S. Government Accountability Office, Tribal Water Infrastructure: Federal Agencies Should Better Track and Coordinate Their Assistance to Alaska Native Villages (GAO-26-107178, September 2026). The staffing gap is one of three structural failures in the same report. Tribes also contend with a forty-year statutory prohibition that bars IHS from connecting water to homes built with HUD housing funds, leaving communities to choose between homes without water or fewer homes. And when multiple agencies try to fund projects together, the absence of a standardized USDA-IHS interagency agreement adds nearly $100,000 in overhead per project — overhead that produces no water, no pipe, and no certified operator.
Fediverse reactions