Bureaucracy Times

All the news fit to be declassified.

  • Cyber Command’s Website Is a Ghost Town. The Command Itself Is Not.

    The Command That Talks For A Living, And Says Almost Nothing

    Type “cybercom.mil” into a browser in late August 2026 and you meet a curious vacuum. The official press release page, the place where the Pentagon usually hangs its official verbs, carries a single line: “No Items”.

    The homepage news carousel shuffles through items from multiple years with no obvious chronology. Links that promise congressional testimony route to 2023 hearings. The @US_CYBERCOM and @CNMF_CyberAlert accounts on X exist, but they function as occasional bulletin boards, not as real time operational feeds. This is the public face of United States Cyber Command in August 2026.

    The gap between what cybercom.mil communicates and what has actually been happening inside the command over the past eighteen months is not subtle. It is structural.

    Over that period, U.S. Cyber Command has navigated a year long leadership gap at the top, announced the most sweeping reorganization in its history, watched a president sign a National Security Presidential Memorandum (NSPM) that invites private companies into offensive cyber operations, and confronted a cluster of deaths by suicide in its ranks.

    The website that belongs to the command at the center of these events has, by design or neglect, remained nearly silent. For an institution that writes doctrine about the fight over information, that silence is not incidental. It is evidence.

    A Command Built To Act, Not To Hide

    U.S. Cyber Command did not appear by accident. It came into existence through a Secretary of Defense directive on June 23, 2009, and became a unified combatant command in 2018.

    From the start, the structure carried weight. The commander serves in a dual hat arrangement as Director of the National Security Agency. The command oversees the Cyber Mission Force, the units that defend Department of Defense networks, support other combatant commanders, and conduct offensive cyber operations when ordered.

    This is not a sleepy support shop. It sits inside the same tier of authority as U.S. Central Command or U.S. European Command, with the added friction of NSA on the other side of the wall. Its operators run hunt forward missions, execute offensive campaigns against foreign military targets, and defend critical infrastructure in coordination with domestic agencies.

    In raw operational tempo, it is one of the busiest commands in the federal government. In public, at least as reflected on cybercom.mil, you would never know it.

    A Year Without A Confirmed Commander

    In April 2025, the dual hat office at Fort Meade emptied out. The previous commander departed, and the role of acting commander fell to Lieutenant General William Hartman, long time chief of the Cyber National Mission Force. His official Defense Department biography notes that he assumed the job as acting commander in spring 2025. He would hold it for nearly a year.

    The Senate finally confirmed General Joshua M. Rudd on March 10, 2026, as reported by the Washington Post.

    According to his NSA leadership biography, he assumed the dual hat command on March 20, 2026.

    A year long vacancy at the top of one of the country’s most sensitive combatant commands, during an active period of cyber conflict and heightened tension with peer adversaries, is not a routine personnel wrinkle. It is a governance failure with operational implications. Yet the command’s own public affairs machinery offered no sustained public accounting of the gap, its causes, or its effects.

    The absence is itself a choice.

    “CYBERCOM 2.0” Without A Home Page

    On August 14, 2026, the Pentagon tried to turn the page. In a news release posted to the Department of Defense site, Secretary of Defense Pete Hegseth announced what the department styled as “CYBERCOM 2.0”.

    The release describes the largest transformation of the command since its creation. It establishes a Revised Cyber Force Generation Model and creates three new enabling organizations: a Cyber Talent Management Organization, an Advanced Cyber Training and Education Center, and a Cyber Innovation Warfare Center.

    In his June 5, 2026 posture statement posted on cybercom.mil, General Rudd framed the goals in the expected confident language of a new commander talking about readiness and modernization. The force generation overhaul, the talent management reforms, the new training and innovation hubs, all appear in his prepared testimony and in the Pentagon press release.

    What does not appear, at least as of late summer, is a matching narrative on the command’s own press release page. The most sweeping structural change in the command’s sixteen year history was announced through the Pentagon’s general press apparatus and the national security press corps. Cybercom.mil, the digital front door of the institution being transformed, did not carry a corresponding press release.

    For a command that spends its working life advising others on how to shape information environments, this is a remarkable failure to shape its own.

    Inviting Cyber Privateers Into The Fight

    The same day Secretary Hegseth rolled out CYBERCOM 2.0, the White House released a National Security Presidential Memorandum titled “Expanding Capabilities to Combat Transnational Cyber-Enabled Crime”.

    This was not an executive order. It was an NSPM that quietly authorized vetted private U.S. companies, under federal oversight and control, to conduct cyber surveillance and cyber effects operations against foreign transnational criminal organizations engaged in cyber enabled crime. The memorandum established a National Coordination Center to supervise the effort.

    The Washington Post described the move as a first of its kind opening for private sector offensive cyber operations in a space that had largely belonged to U.S. Cyber Command and the NSA.

    Federal News Network highlighted fresh questions about Computer Fraud and Abuse Act exposure, Fourth Amendment constraints, and oversight architectures for companies now invited to conduct state authorized hacking abroad.

    A legal analysis by Mayer Brown walked through potential liability shields and diplomatic friction points created by unleashing commercial actors in foreign networks.

    In other words, the White House used a national security instrument to redraw, at least at the margins, the exclusive domain of USCYBERCOM and NSA.

    It created a new class of state supervised cyber privateers. The command whose remit is closest to the new authorities did not, as of this writing, see fit to explain or contextualize any of this on its own website. Outsiders are left to read between the lines of others’ reporting, while cybercom.mil maintains the fiction that nothing especially novel happened in mid-August.

    A Cluster Of Deaths, And A Public Silence

    On August 6 and 7, Bloomberg reported that U.S. Cyber Command was confronting an unusually high number of deaths by suicide among its personnel over a roughly month long period in early summer 2026, describing as many as five deaths between early June and early July, based on unnamed sources.

    Breaking Defense followed with a report describing the pattern as a cluster significant enough to merit intervention from senior Pentagon leadership.

    The facts as reported are grave, and they sit in a context that is already hard on human beings.

    Cyber operators work under unusually dense classification, chronic shift work, and the psychological weight of offensive missions conducted far from any visible battlefield. A cluster of deaths by suicide inside that community is a personnel welfare and institutional accountability story of the first order.

    Yet the command’s news feed and press release page, as visible to the public, carry no notice, no statement of condolence, no description of resources, no acknowledgement that Congress is asking questions. The command is talking, or preparing to talk, to lawmakers behind closed doors. It is not talking to the public about what is, at bottom, a human crisis within its ranks.

    The Doctrine Of Information, Ignored At Home

    Cyber Command’s own doctrine, strategy documents, and posture statements are fond of reminding everyone that information is a contested domain, that perception shapes deterrence, and that adversaries exploit every vacuum.

    The command publishes a public affairs contact line, USCYBERCOM Public Affairs, reachable at uscybercom_pao@cybercom.mil.

    It maintains a presence on the Defense Visual Information Distribution Service.

    It runs two branded X accounts.

    These are not the hallmarks of a command that lacks public communications infrastructure. They are the footprints of a command that has built the tools and then chosen, for some combination of operational security caution, resource constraints, and leadership priorities, to let its own primary website sit in a state that resembles abandonment.

    OPSEC concerns in this space are real. So are classification rules. No one expects live targeting updates on cybercom.mil. But it does not require revealing sources and methods to acknowledge a prolonged leadership vacancy, to summarize a publicly announced institutional reorganization, to explain what a presidential memorandum does or does not change for the command, or to recognize publicly that multiple members of the workforce have died by suicide and that the institution takes that seriously.

    Those are choices about accountability, not about secrecy.

    “No Items” In A Very Busy Year

    The front door to U.S. Cyber Command’s public presence still insists that it has no press releases. Its carousel still spins news items from assorted years with all the coherence of a forgotten bulletin board. Its homepage still sends readers to 2023 testimony while 2026 hearings unfold elsewhere.

    In the same span of months, the command has gained a new dual hat commander, undergone a sweeping reorganization, watched a presidential memorandum invite private actors into offensive cyber operations, and begun fielding congressional scrutiny over a cluster of deaths by suicide in its workforce.

    The information is not hidden.

    Bloomberg has it.

    The Washington Post has it.

    Breaking Defense has it.

    Specialty legal analysts have it.

    Congress has it.

    USCYBERCOM Public Affairs, whose email address sits quietly on cybercom.mil, appears content to let others tell the story.

    For a command built on the premise that information is power, there may be no sharper indictment than its own decision to leave its primary window to the public marked “No Items.”

    CYBERCOM’s accountability gap has a parallel in the conventional defense world. The Navy’s attack submarine fleet — another category of high-stakes military capability where public accountability has lagged operational reality — is the subject of our $3.4 billion submarine maintenance report. Both cases show the same pattern: an institution managing a crisis internally while its public face insists everything is on schedule.

  • $3.4 Billion Sitting at the Pier: The Navy’s Submarine Maintenance Crisis, Quantified

    Fifteen Thousand Lost Days: The Submarine Fleet That Waited at the Pier

    USS Boise was supposed to be a workhorse, not a case study. Commissioned in 1992, the Los Angeles class attack submarine spent much of the last decade not hunting adversary submarines, not collecting intelligence, but waiting. First she waited for an overhaul that slipped year after year while the public shipyards had no room for her. Then she waited for a solution that never arrived.

    In February 2024, the Navy finally awarded a $1.2 billion contract to Huntington Ingalls Industries to perform Boise’s long delayed refueling overhaul, nine years after it should have begun, as Defense News reported. The message was simple enough: late, but at least the boat would return to the fleet. Then, in April 2026, the Navy quietly announced Boise’s inactivation, closing the books on a submarine that never received the overhaul taxpayers had just funded on paper.

    Boise has become the most expensive illustration of a problem the Government Accountability Office has now quantified in GAO 26 109256, released publicly on August 27, 2026. Over the past decade, the Navy’s attack submarines have lost more than 15,000 operational days because the service could not get them into, through, and out of depot maintenance on time. The bill for that failure, according to GAO’s public report and coverage by Defense News and Breaking Defense, is roughly $3.4 billion. From fiscal 2016 through 2025, only about 11 percent of depot maintenance availabilities at the Navy’s public shipyards finished on schedule.

    Boise is a cautionary tale. GAO’s numbers show it is also a preview.

    The Numbers Behind the Pier

    GAO 26 109256 dissects the problem in terms that leave little room for creative interpretation. Lost time falls into two main buckets. First, maintenance delays, when a submarine is in the shipyard longer than planned. Second, inactive idle time, when a submarine sits pier side waiting for a dry dock or shipyard slot that is not available.

    Neither bucket is theoretical. Over the past ten years, attack submarines accumulated more than 15,000 lost operational days in these two categories, GAO found. That is more than forty years of submarine availability erased from the fleet’s usable inventory. Breaking Defense reported GAO’s estimate that the resulting cost to the government is about $3.4 billion over that period, with Defense News underscoring the scale of the time loss.

    The report does not publish detailed figures on National Reconnaissance Office or National Geospatial Intelligence Agency spending related to submarine operations. Those numbers sit behind the classification wall. The attack submarine maintenance figures do not. GAO lays out a future in which the problem gets worse before it gets better. Between fiscal 2026 and 2030, the watchdog projects that 15 attack submarines will enter inactive idle time, generating more than 14,000 additional idle days and about $3.1 billion in associated costs.

    In theory, a growing fleet could absorb some of that dead time. In practice, the fleet is not growing at the rate Navy leaders have advertised. As USNI News reported in May 2026, the Virginia class production line was turning out about one submarine per year as of mid 2025, half the Navy’s stated goal of two per year. Chief of Naval Operations Adm. Daryl Caudle projected that the two per year build rate would not be achieved until the 2030s. When the industrial base delivers new hulls at half speed while existing boats stack up in maintenance queues, the arithmetic does not favor operational commanders.

    How a Submarine Ends Up Waiting for Years

    The structural cause is not mysterious. Four public naval shipyards perform depot level maintenance on nuclear powered submarines and carriers. Portsmouth Naval Shipyard in Maine, Norfolk Naval Shipyard in Virginia, Puget Sound Naval Shipyard in Washington, and Pearl Harbor Naval Shipyard in Hawaii each have fixed dry dock capacity and infrastructure that was old when many of the current crews were in elementary school.

    When a major availability runs long, the queue behind it does not disappear. The next submarine in line waits at the pier, crew embarked, reactor shut down, systems aging instead of operating. That wait can stretch for months or years, as with Boise. During that time, the Navy pays operating and support costs for a submarine that is not operating and cannot be supported back to readiness because there is no place to put it.

    The Shipyard Infrastructure Optimization Program, or SIOP, is the Navy’s answer on paper. SIOP is the multi decade effort to modernize and expand dry docks, facilities, and equipment at the four public yards. GAO’s 2026 report acknowledges SIOP’s role but also points out a simple fact of civil engineering. Dry docks take years to design, years to build, and years more to bring fully online. They are not a quick reaction capability.

    Workforce is the other half of the problem. Nuclear qualified shipyard workers are not interchangeable with generic labor. They take years to recruit, clear, train, and season. The shipyards have struggled to retain experienced personnel while competing with private industry and facing demographic headwinds. GAO identifies these capacity constraints in both infrastructure and workforce as root causes of missed maintenance schedules and rising idle time.

    None of this is new information inside the Navy. In GAO 19 229, published in 2019, the watchdog documented that attack submarines had lost more than 10,000 days of availability between 2008 and 2018 due to maintenance backlogs and idle time at the public shipyards. The 2026 report does not reveal a surprise. It simply updates the score, and the score has worsened.

    From Boise to a Fleet Wide Condition

    It is tempting to file Boise under tragic one off mismanagement. GAO’s data argues the opposite. Boise is an extreme case, but not an outlier. She illustrates what happens when inactive idle time stops being the rare exception and becomes a routine phase in a submarine’s life cycle.

    The projection that 15 attack submarines will enter inactive idle time through fiscal 2030 is more than a statistic. Each hull represents a crew that must either sit and wait or be reassigned, an operational commitment that slips into the future, and a maintenance bill that grows with every idle day. Systems do not age gracefully while sitting unused in salt air.

    These numbers intersect badly with the strategic commitments the United States has made. Under the AUKUS agreement with Australia and the United Kingdom, the United States has pledged to support Australian acquisition of nuclear powered submarines and to host rotational deployments of Virginia class boats at HMAS Stirling in Western Australia. The joint statement from AUKUS defence ministers in May 2026 reaffirmed those ambitions. They rest on an assumption that the United States will have enough attack submarines in working order to rotate through these deployments while still meeting U.S. Indo Pacific Command and other combatant commanders’ needs. GAO’s maintenance and idle time projections invite a hard look at that assumption.

    GAO’s Workarounds and the Navy’s Shrug

    GAO 26 109256 does more than add up days and dollars. The watchdog recommends that the Navy evaluate options for managing submarines that are approaching inactive idle time so that the fleet can squeeze more utility out of constrained shipyard capacity.

    The options GAO lists will sound familiar to anyone who has listened to maintenance planners for more than five minutes. Pier side defueling, where a submarine’s nuclear fuel is removed at a pier rather than in a dry dock, could free up scarce dry dock space for other work. Reduced crewing arrangements could cut the cost of keeping a submarine idle while still preserving the core cadre needed for eventual return to service or inactivation. Service life extensions, when technically sound, could keep boats in the fleet longer while newer construction lags.

    These are not elegant fixes. They are triage plans for a system that cannot be expanded quickly. GAO’s recommendations read like the bureaucratic equivalent of telling the Navy to stop leaving fully crewed submarines parked at the pier out of habit when cheaper, more rational options exist.

    The Navy’s formal response, as summarized in the public report, was to verbally concur with GAO’s recommendations and provide no written comments. Readers of GAO reports know what that phrase means. It is the institutional version of nodding politely at a briefing and then walking back to the office to keep doing things the old way. GAO issued the report in classified form on July 16, 2026; the public version arrived six weeks later, on August 27, a normal interval. The seven year gap between GAO 19 229 and GAO 26 109256, with the same core findings and larger numbers, is harder to categorize as normal.

    Why the Lost Days Matter

    Attack submarines are the Navy’s most strategically versatile conventional assets. They hunt adversary submarines and surface ships, collect intelligence, support special operations forces, launch cruise missiles, and complicate the planning of any potential adversary. They are the quiet part of American power that foreign naval officers worry about when they look at a map.

    Every day an attack submarine sits at a pier waiting for a dry dock that is not available is a day it is not doing any of those things. The 15,000 lost operational days GAO tallies over the past decade are not abstract bookkeeping. They represent patrols that never sailed, signals that were never intercepted, exercises that relied on fewer submarines than planned, and allied navies that saw less American presence than they were told to expect.

    The report arrives at a moment when the Navy is juggling multiple pressures. AUKUS commitments require more available attack submarines, not fewer. The Virginia class construction line is below the desired production rate, as senior leaders acknowledge. The surface fleet has its own readiness and maintenance problems that compete for shipyard resources and political attention. The submarine maintenance crisis does not sit apart from this picture. It lives at the center of a maritime strategy that depends on stealthy, persistent undersea presence.

    GAO has now spent more than a decade documenting, in public, that the Navy’s ability to maintain that presence is constrained by shipyards and processes the service controls. USS Boise’s lost overhaul and quiet inactivation are not merely an unfortunate footnote in that record. They are a warning of what happens when an institution learns to live with failure at scale and calls it a scheduling problem.

    The submarine maintenance crisis is not the only place where a U.S. military command’s public accountability has failed to keep pace with what’s actually happening inside the institution. Our coverage of CYBERCOM’s ghost town website documents a command that underwent its largest reorganization in history, absorbed a suicide cluster among its personnel, and watched a presidential memorandum redraw its operational domain — all without a single press release on its own site. Both cases point to institutions that have learned to manage their public narrative by simply not having one.

  • Paper Workflows and Empty Corridors: The VA’s Mountain Home Problem

    Mountain Home Has Been Here Since 1903. It Still Needs Written Instructions To Call You Back.

    VA Mountain Home Healthcare System sits on a historic campus that opened around 1903 as the Mountain Branch of the National Home for Disabled Volunteer Soldiers. A century and change later, the institution that learned how to treat trench lung and mustard gas injuries just received a formal reminder from its own watchdog that staff should have written instructions for telling patients their test results. Not how to interpret the results. Not how to treat the disease. How to pick up the phone.

    On August 28, 2026, the VA Office of Inspector General released an inspection of the VA Mountain Home Healthcare System in Johnson City, Tennessee, also known as the James H. Quillen VA Medical Center. The system serves veterans across a 32 county patch of northeastern Tennessee, southwestern Virginia, and southeastern Kentucky. After examining quality, leadership, and patient care, the OIG landed on a single recommendation: the facility must create written, service level workflows for communicating test results, consistent with Veterans Health Administration Directive 1088(1), Communicating Test Results to Providers and Patients.

    In plainer English, the oldest veteran campus in the system needed Washington to tell it to write down who calls whom, when, and how, after a lab machine finishes humming. The OIG closed that recommendation the same day the report came out. Which raises a blunt question. If the paperwork looks fixed in a single afternoon, how long have the patients been living with the gap?

    What VHA Directive 1088(1) Actually Demands

    VHA Directive 1088(1), issued July 11, 2023, is not exactly beach reading. It sets requirements for timely, traceable communication of test results to both providers and patients. The directive spells out responsibilities, time frames, and documentation so there is a clear trail from the lab to the chart to the patient. The whole point is to stop test results from vanishing into the electronic equivalent of a desk drawer.

    When the OIG tells Mountain Home to develop written, service level workflows, it is saying that each clinic and service line needs a step by step process that matches the directive. Who reviews the result. How quickly. How abnormal findings reach the treating clinician. How and when the patient gets notified. How the contact gets documented so supervisors and inspectors can verify that someone actually did the job.

    That may sound bureaucratic. It is also the difference between a caught tumor and a missed one. Directive 1088(1) exists because the system has a long history of test results that fell through cracks wide enough to swallow an entire oncology ward.

    Staffing Shortages Meet Paper Thin Workflows

    The inspection of Mountain Home does not land in a vacuum. In the VA OIG’s fiscal year 2023 staffing shortages report, the same system shows up in Table C.58 with shortages across a familiar roster of jobs. Social workers. Nurse anesthetists. Practical nurses. Nursing assistants. Custodial workers. Food service workers. In other words, the people who stabilize a patient, keep the operating room moving, and make sure the place does not literally fall apart.

    Short staffing does not just mean longer waits in the lobby. It means that nurses race between beds, clerks juggle phones and inboxes, and supervisors quietly accept that some tasks will not get done. When there is no clear, written workflow for test result communication, the missing tasks often involve calls that no one can see. A lab result comes back. The ordering provider is off, or already drowning in alerts. A nurse means to follow up after the next medication round. A reminder gets buried. No policy pins responsibility on a specific role, within a specific time frame, with a specific way to document closure. The patient never hears a word.

    The scheduling breakdown at Mountain Home is not isolated. As covered in our report on the VA community mental health system, 128 out of 133 VA healthcare systems failed to meet the department’s own seven-day standard for scheduling mental health consults in FY2025 — a pattern that begins with the same undocumented, untracked workflow gaps visible at Mountain Home.

    That is the context in which the Mountain Home inspection tells leaders to put workflows on paper. Not because veterans need more binders. Because in an understaffed system, anything that is not written, tracked, and measured will be the first thing to disappear.

    Mountain Home Is Not An Outlier

    The OIG did not invent concern about test result communication for Mountain Home. It has been walking this same trail across the country. At the VA Dublin Healthcare System in Georgia, an April 2024 root cause analysis documented 25 patient safety events tied to failures in communicating test results. The OIG’s March 2025 report on Dublin tied those events directly to gaps in how results moved from lab to provider to patient.

    In February 2025, the OIG reported on the VA Salem Healthcare System in Virginia and found problems with communication of urgent and noncritical test results, again citing VHA Directive 1088(1). In December 2024, the OIG’s review of VA Durham in North Carolina concluded that leaders lacked hospital wide oversight to validate whether providers followed requirements for communicating test results. That is the same directive number haunting multiple campuses from Georgia to North Carolina to Virginia to Tennessee.

    Meanwhile, Mountain Home has drawn attention for issues well beyond lab results. In 2024, the House Committee on Veterans Affairs announced an investigation into allegations of workplace misconduct at the Quillen VA Medical Center. The same campus that now needs to formalize how it tells patients their test results was already on the congressional radar for broader cultural and management concerns.

    Layer on top of that a broader federal critique. A Government Accountability Office report, GAO 26 107528, examines how VA reviews and reports providers with clinical care concerns and calls for better training and oversight. Different investigators. Different document numbers. Same theme. The system struggles to consistently identify, track, and respond when patient care depends on staff following through.

    What A Missed Test Result Really Means

    The phrase “test result communication failure” sounds like something you fix with a software patch. The reality is uglier. A missed pathology report can mean a cancer that moves from treatable to terminal. A lab value that never reaches a clinician can mean sepsis that runs unchecked. An imaging finding that sits unreviewed can turn a manageable condition into a permanent disability.

    Every inspection and directive cited above exists because somewhere, a veteran sat at home waiting for a call that never came. Families do not sue over high level policy memos. They sue, and grieve, over the scan that no one followed up.

    This is why the timing in the Mountain Home report deserves scrutiny. The OIG issued the recommendation on August 28, 2026 and closed it the same day. On paper, that means the facility responded quickly and accepted the requirement to create those written workflows. In practice, the same day closure tells the public very little about whether the new procedures exist on the ground, whether staff know them, or whether anyone will check compliance three months from now.

    When a watchdog closes a recommendation the day it appears, it signals trust in leadership promises and in the documentation provided. It does not tell us how many veterans experienced delayed or missed results before the paperwork caught up. It does not tell us whether the same staffing shortages that drove the problem will sabotage the solution.

    So the question practically asks itself. In a system that needed a 2023 directive to spell out how to communicate test results, a string of OIG reports from Dublin to Durham to Mountain Home, a congressional investigation, and a GAO warning about weak oversight of problematic providers, how confident should a veteran feel that a normal lab result and a life changing one will both trigger the right call, at the right time, from the right person?

    Mountain Home has stood for veterans since 1903. Its history is carved in stone on a National Historic Landmark campus. The real test now is written somewhere else. In the workflows, checklists, and audit trails that show whether a twenty first century veteran will hear about a dangerous test result before it is too late.

    The deeper context for these failures is documented in our coverage of the $1.7 billion blind spot in VHA eligibility determinations — a systemic audit of how the VA’s internal guidance, broken scheduling software, and phantom wait times combine to fail veterans at every step of the care access chain.

    Fediverse reactions

  • The Loneliest Job in Federal Oversight: Congress Finally Moves on NOAA Observer Harassment

    Congress Discovers NOAA Observers Are Human After All

    Alone On The Boat With Everyone Pretending Nothing Is Wrong

    The federal government calls them observers. In practice, they are one unarmed person with a clipboard, a tablet, and a mandate, dropped onto a commercial fishing vessel for days or weeks at a time. They count every fish, record every discarded catch, and document anything that smells like a violation of the Magnuson Stevens Act. They share cramped bunks with the crew they may later help prosecute. Their presence can shave thousands of dollars off a haul if what they write down does not match what the captain wants to land.

    Observers, at sea monitors, and catch monitors are the federal government’s eyes and ears on the water. They supply the data NOAA Fisheries uses to set catch limits, justify management decisions, and defend them in court. According to NOAA’s own materials on observer safety and harassment, they do all this while facing a steady risk of verbal abuse, intimidation, and worse. NOAA has highlighted a North Pacific case where harassment of an observer led to a Notice of Violation and Assessment of tens of thousands of dollars against a vessel. That incident made it into an enforcement action. Many others, as NOAA sponsored research has shown, never make it into any official record at all.

    Peer reviewed work in journals such as Frontiers in Marine Science, along with NOAA funded studies on the Alaska maritime workplace, has described systematic underreporting of harassment and obstruction of observers. The pattern is not subtle. One worker, often the youngest and least powerful person on board, lives and works in close quarters with the very people whose behavior they are supposed to document. Federal policy historically told them that if something happens, they should report it through channels designed for office parks and research labs instead of rolling decks and hostile wheelhouses.

    What H.R. 2406 Actually Does, Behind The Branding

    Enter H.R. 2406, the National Oceanic and Atmospheric Administration Sexual Harassment and Assault Prevention Improvements Act of 2025. The title reads like a committee staffer tried to squeeze every relevant noun into one line. The substance, laid out in House Report 119-761 and in the bill text on GovInfo, is more focused.

    The bill, introduced by Representative Suzanne Bonamici with bipartisan cosponsors including Representatives Maria Salazar, Jared Huffman, and Brian Fitzpatrick, starts with a simple admission that took Congress far too long to articulate. NOAA’s existing sexual harassment and assault policies did not explicitly protect the people the agency sends onto boats to enforce federal fisheries law. H.R. 2406 expands those policies to cover observers, at sea monitors, catch monitors, and staff of the regional fishery management councils.

    The bill also creates a restricted reporting option so that observers and other covered personnel can make confidential disclosures without automatically triggering a full investigation. That kind of option already exists in other federal contexts. Here, it is treated as a novel improvement for people who have been filing incident reports from the middle of the ocean for years.

    H.R. 2406 requires NOAA to refer vessel related incidents of sexual harassment and assault to the Coast Guard, along with the names of the individuals involved, the vessel, and the time and location of the incident. It directs the agency to strip out older “forcible” qualifiers in policy language so that non stranger sexual assaults and a wider range of coercive conduct clearly fall within the rules. It expands the annual report to Congress so that lawmakers stop receiving glossy aggregate counts and instead see case synopses, information on disciplinary actions, and breakdowns across observer categories.

    One more provision speaks volumes about how literally Congress expects NOAA to take all this. The bill prohibits individuals with certain sexual offense convictions from joining the NOAA Corps. The fact that this needed to be spelled out in legislative text tells its own quiet story about gaps the system had tolerated.

    According to House Report 119-761, the Natural Resources Committee reported the bill favorably on August 20, 2026, with bipartisan support and no meaningful opposition. For a Congress that can turn a routine reauthorization into a multi year culture war, that level of consensus is its own data point.

    How A “Success Story” Managed To Leave Observers Exposed

    The backstory, documented in GAO reports and NOAA’s own studies, will not reassure anyone who thought federal workplace protections were already universal. In 2021, the Government Accountability Office released GAO 21 560 on NOAA’s sexual harassment and assault prevention efforts. The report concluded that NOAA had made “substantial progress” on prevention and response. In Washington, that phrase functions as both praise and warning. It begs the question of what conditions looked like before the progress and what still sat outside the frame.

    NOAA’s public facing materials on observer safety acknowledge that harassment incidents have been significantly underreported. Its summary of a new study on harassment in the Alaska maritime workplace describes observers who did not come forward at all or waited until long after returning from deployments. A paper in Frontiers in Marine Science details harassment and obstruction of observers in multiple fisheries, reinforcing the same pattern. Observers described behavior that would violate any modern harassment policy. The problem was that the policy did not clearly reach them.

    The gap was not abstract. The North Pacific Observer Program has highlighted specific enforcement actions, including a Notice of Violation and Assessment of about fifty five thousand dollars against a vessel following harassment of an observer. That case, plastered on NOAA’s own website as an example of seriousness, stands out precisely because it is an exception. The agency’s own research says the incident iceberg is larger than the visible tip.

    Yet for years, as observers lived and worked in this environment, NOAA’s sexual harassment policies focused on employees and settings that looked much more like traditional offices. Observers contracted through providers, at sea monitors, and some council staff sat in a gray zone that could leave them without the same protections or clear reporting paths. According to the committee report and bill text, H.R. 2406 is meant to close that gap. The timeline raises an obvious question. If the problem is so plain now that both parties agreed to plug it, why did everyone tolerate the hole for so long.

    Why Observer Safety Is Not Just A Human Resources Issue

    Fisheries observers illustrate a basic truth about federal oversight. The government often relies on a single individual to stand in for the public interest in places that are hard to reach and easy to ignore. Under the Magnuson Stevens Act, observer coverage helps set catch limits, trigger enforcement, and defend management decisions in court. The accuracy of those data feeds depends on observers who feel safe enough to record what they actually see and report it without fear that the next deployment will become punishment.

    NOAA’s own messaging about observer harassment admits that underreporting and lack of confidential reporting options have distorted the picture. Before H.R. 2406, whole categories of people who were central to fisheries management sat outside the strongest protections. That is not just a workplace policy oversight. It is a structural flaw in the way the government manages the nation’s fisheries.

    The bill will not repair every weak joint in that structure. H.R. 2406 does not rewrite deployment practices that place a lone observer on vessels for weeks at a time. It does not change vessel culture or the basic power imbalance between an observer whose contract depends on successful deployments and a captain whose income depends on how much catch gets recorded. It does not guarantee that every retaliation risk disappears just because reporting options have better labels.

    What the bill does, according to the committee report and supporting documents from sponsors such as Representative Huffman, is drag observer safety and harassment out of the gray zone where it has sat for too long. It pulls observers, at sea monitors, catch monitors, and council staff clearly into NOAA’s harassment and assault framework, insists on Coast Guard notification when incidents happen on vessels, and forces more detailed information into Congress’s hands.

    For a rare bipartisan effort in a polarized Congress, the most damning part is how modest it is. None of this should be innovative. Confidential reporting, clear coverage of contract like workers, basic screening of Corps officers, and transparent case reporting are the floor of any credible harassment regime. In this sector, that floor took years of reports, studies, and one too many horror stories at sea before lawmakers finally bothered to pour the concrete.

    H.R. 2406 is the kind of bipartisan accomplishment that rarely makes news because it fixes something that should never have been broken. The Chuck Edwards censure recommendation — also cleared by a bipartisan Ethics Committee that same August — is another rare instance of the institution applying its own rules with consistency. That case involves a different congressional power structure, but the same underlying question: what it takes to make federal workplace protections mean something for people who lack the power to enforce them on their own.

  • 128 Out of 133 VA Medical Centers Can’t Schedule a Mental Health Appointment Within Seven Days

    Seven Days, Five Systems, and a Community Care Promise Still on Paper

    The Department of Veterans Affairs has a seven day standard for one very specific step in mental health care. When a VA clinician refers a veteran to the community care program for mental health services, the consult is supposed to be scheduled within seven days. In fiscal year 2025, according to the VA Office of Inspector General, five of 133 VA healthcare systems met that standard. The other 128 did not.

    The community care program exists because the VA concluded, years ago, that it could not meet all veterans health care needs inside its own walls. Congress passed the VA MISSION Act to formalize that decision and to expand veterans access to care through outside providers.

    The model is straightforward: when VA cannot provide timely or appropriate care, it buys that care from the community through contracted administrators. The premise is sound. The execution, as laid out in VA OIG Report 25 03623 147 covering October 2024 through September 2025, is lagging behind the VA standard the department set for itself.

    How community care mental health scheduling is supposed to work

    The referral chain on paper is not that complicated. A VA provider decides a veteran needs mental health care that is better delivered outside the VA system. That may be because of local capacity, specialty needs, or geography. The provider enters a community care consult in the VA system. From there, the case routes to one of two third party administrators that manage the VA Community Care Network. Veterans in Regions 4 and 5 go to TriWest Healthcare Alliance, while veterans in Regions 1 through 3 go to Optum Public Sector Solutions.

    The contractor is responsible for taking that consult and turning it into an appointment with a community mental health provider. The job sounds mundane: 1) reach the veteran, 2) confirm preferences, 3) find an in network provider with capacity, and 4) schedule a date and time.

    The VA tracks two separate metrics for this process. The first is the seven day standard for how quickly the consult is scheduled. The second is a 30 day contract metric for when the appointment itself is supposed to occur.

    Those are different thresholds that measure different parts of the pipeline, but both matter. If the consult stalls before it is scheduled, the clock on the 30 day metric never really starts from the veteran point of view.

    The OIG review found that the system frequently slowed down or stopped at the scheduling step, where staff tried to reach veterans, confirm provider availability, and reconcile preferences with real world options.

    What the OIG actually found

    The headline number in the August 10, 2026 report is blunt. One hundred twenty-eight of 133 VA healthcare systems averaged more than seven days to schedule community mental health consults in fiscal 2025. Five systems met the standard. That is not a near miss. It is a system wide miss on a metric the VA defined as its own expectation for timely scheduling.

    The picture is more mixed on the 30 day contract metric for when appointments occurred. The OIG found that approximately 80 percent of community mental health appointments happened within 30 days. For the remaining 20 percent or so that did not meet that benchmark, veterans waited an average of 56 days for the actual appointment. That 56 day figure does not describe all community mental health visits. It describes the subset where the system already failed the 30 day standard.

    The OIG did not attribute that gap to a single dramatic breakdown. It pointed instead to a cluster of mundane but consequential problems. First, VA staff and contractors relied heavily on phone calls and postal mail to reach veterans. In many cases, they did not use more efficient or reliable digital contact methods that could shorten back and forth.

    Second, community providers did not always offer appointment types that matched what veterans wanted or needed. Preferences about in person visits versus telehealth, or about certain modalities, were not consistently captured in systems in a way that schedulers could act on. That mismatch produced more calls, more rescheduling, and more delay.

    Third, schedulers reported difficulty getting timely responses from community providers to confirm availability and lock in appointment slots. Unreturned calls, limited office hours, and fragmented communication channels all translated into longer waits between referral and scheduled date.

    A fourth problem sat on top of that. Some community providers insisted on duplicate documentation that the VA had already included in the original referral package. That meant more requests back to VA facilities for forms and records the system had already sent once.

    None of this would impress a management consultant. There is no exotic algorithmic failure here. The VA set a seven day standard for scheduling. The system repeatedly tripped over phone tag, partial preference data, hard to reach providers, and redundant paperwork.

    The structural problem behind the scheduling problem

    The OIG findings land in a landscape that was already crowded with warnings about the VA community mental health network. In November 2024, the Government Accountability Office reported in GAO 24 106410 that the VA assessment of its community care network adequacy for mental health needed improvement. GAO highlighted gaps in how VA evaluated whether the network had enough providers to meet demand.

    An April 2024 VA OIG audit on network adequacy and contractor performance came to a similar conclusion. It found that oversight of the community care network and of contractor performance needed strengthening, including how VA evaluated whether contractors met access standards. On paper, VA relies on TriWest and Optum to maintain a network that can actually deliver the care veterans are referred to receive.

    The provider directories that veterans and schedulers depend on have their own problems. A 2022 GAO report, GAO 23 105290, found that veterans sometimes could not book appointments with providers who appeared in the Community Care Network directory as available. Inaccurate entries, providers who were not accepting new patients, and outdated information all contributed.

    Viewed against that backdrop, the FY2025 scheduling failures are not a stand alone surprise. They are downstream of a network with thin provider supply in some regions, directories that do not always match reality, and oversight that has not kept pace with the size and importance of the community care program. You can streamline the scheduling workflow, and the OIG suggests ways to do that. You still cannot schedule an appointment with a provider who is not actually available.

    The six recommendations and the scorecard so far

    The August 2026 OIG report made six recommendations to the Under Secretary for Health. Two have already been closed as implemented. One directed VA to consider contractual adjustments with third party administrators to improve timeliness of community mental health scheduling. The other required the department to issue standardized guidance that makes clear community providers should not request documentation that VA already includes in referral packets.

    Four recommendations remain open. The first calls for VA to identify and share best practices for contacting veterans in ways that actually reach them quickly. The second focuses on ensuring scheduling systems capture and use the full range of veteran preferences when matching to appointments. The third directs VA to evaluate whether TPA network adequacy standards are sufficient for both in person and telehealth mental health providers, given demand. The fourth urges a review of ways to increase community provider use of VA systems so that communication and documentation flow through consistent channels instead of scattered faxes and phone calls.

    The two closed recommendations nibble at the edges of process friction. The four that remain open go to the structure of how VA, its contractors, and its provider networks actually operate. Whether those structural fixes move from recommendation to enforcement before the next oversight report arrives is an open question.

    Why the delay metrics matter

    Mental health care for veterans who reach the point of a community referral is not elective. A VA clinician has already determined that care is needed and that the department cannot provide it internally in the required way or time frame. For the roughly one in five community mental health appointments that missed the 30 day contract metric in FY2025, the average 56 day wait was not a trivial inconvenience. It represented weeks in which needed care did not occur.

    The veteran population relying on these services carries a documented and elevated risk of suicide and other serious mental health outcomes. That is part of the reason the VA adopted a seven day scheduling standard in the first place. It reflects an institutional understanding that long gaps between referral and first appointment are dangerous.

    The VA, GAO, and the OIG have been writing versions of this story for years. Reports on scheduling, network adequacy, directory accuracy, and contractor oversight repeat the same themes with new data and new report numbers.

    The 25 03623 147 review does not reveal a hidden crisis. It documents, again, a pattern of missed standards, modest corrective steps, and partial follow through. Meanwhile, the metric on the books remains seven days. Five out of 133 systems met it.

    The scheduling crisis documented here is one thread in a larger pattern of VA care access failures. The $1.7 billion blind spot in VHA eligibility determinations shows how the same system sends hundreds of thousands of veterans to outside providers they’re ineligible for, while simultaneously failing to inform eligible veterans they have any outside option at all. The Mountain Home test result crisis illustrates what happens inside the facilities where veterans land when those referrals don’t materialize. And for veterans whose caregivers depend on the VA’s program stability, the 2028 caregiver sunset is the next cliff approaching.

  • The SEC’s Most Brazen Impostor: How “WealthTutor” Forged Its Way Into Your Portfolio

    Three Names, One Scam: How WealthTutor Played Adviser Dress Up While Regulators Napped

    You have read the press release. Some plucky staff in gray suits finally noticed that a company calling itself WealthTutor Corp was about as real as a late night trading bot on Telegram. The irony is not that the firm lied. Of course it lied. The irony is that it lied in public, on government forms, on a government website, for months, while the same government now congratulates itself for spotting the forgery it had been hosting.

    The Form ADV That Lived in Fantasy Land

    The Securities and Exchange Commission complaint against Ichcoin Tech Corp, later renamed WealthTutor Corp, reads like a parody of the agency’s own disclosure system. According to the civil complaint and the matching litigation release, the firm filed a Form ADV that claimed it was a registered investment adviser when it was not even close to eligible.

    They did not stop at lying about status. The form listed a CRD number that belonged to an entirely unrelated individual, phone numbers that rang into the void, and a principal office address that the company did not actually occupy. In other words, the very fields the public is told to trust as objective, verifiable data turned out to be performance art.

    The fake registration still shows its ghost in the SEC’s own investment adviser database. The adviserinfo page for firm number 323744 is right there on IAPD, with the status marked as withdrawn. It reads less like a regulator’s proud archive and more like a crime scene left intact for tourism.

    From Indicator Global to Ichcoin to WealthTutor

    Corporate shape shifting is not a new trick, but Ichcoin Tech Corp turned it into something close to performance art. The SEC describes the company as having been known at various points as Indicator Global Inc, Ichcoin Tech Corp, and finally WealthTutor Corp. Three corporate identities, one scheme, and a trail of paperwork that should have lit up every system that claims to monitor registration risk.

    This was not some back alley operation hiding in the shadows. The company used its evolving set of names to present itself as a sophisticated technology driven adviser. They did what every fraudster with a Canva account now does. Glossy website. Sleek branding. And in this case, the pièce de résistance, a forged SEC registration certificate proudly displayed online. The complaint spells it out. WealthTutor’s operators posted a counterfeit certificate to convince investors the SEC had blessed their act.

    The App That Was Really a Funnel

    The company did not just lie on paper. It built a trading fantasy for your phone. According to the SEC, Ichcoin Tech Corp rolled out a phony mobile trading application. Investors believed they were watching real positions and real balances. Behind the interface, the app was not routing trades. It was routing cash. Money in, nothing out, except to the people running the scheme.

    At least three investors fell for it. One lost nearly two million dollars. Think about the kind of trust it takes to move that much money into a brand new app from a little known firm with a churning name history. Then remember that the investor could look up the firm on a government website and see what looked like a real registration. The trust did not come out of nowhere. It was manufactured, with a generous assist from the illusion of regulatory vetting.

    Red Flags in the Wild, Silence in the Temple

    While officialdom slept, the people it loves to lecture were already sounding alarms. In December 2024, the Washington State Department of Financial Institutions quietly dropped an alert about alleged crypto related scams incorporating in the state. Among the usual menagerie of shell companies and blockchain flavored hallucinations sat Ichcoin Tech Corp. State regulators saw enough smoke to warn the public long before the SEC took federal action.

    Go lower down the hierarchy and the picture gets more damning. Users on Reddit’s r/CryptoScams were posting victim reports tied to the scheme as early as June 2024. Screenshots of fake app balances. Stories of withdrawal delays that turned into black holes. The usual pattern of online fraud, narrated in real time by the people living it. No subpoena necessary. No forensic data pull. Just a browser and a search bar.

    Yet according to the federal docket, the SEC did not file its case in the Northern District of New York until August 27, 2026, in SEC v. Ichcoin Tech Corp, now known as WealthTutor Corp, Case No. 1:2026cv01648. The litigation release followed a day later. By then, the money was long gone and the only thing left to protect was the narrative.

    The System That Believes Its Own Forms

    This case matters less for its cast of characters and more for what it reveals about the machinery around them. The SEC did not just get fooled by a clever fraud. It built the stage set. The Form ADV, with its air of bureaucratic precision, became a prop. The adviserinfo database, marketed as a safe public gateway to adviser credentials, became an unwitting recommendation engine. A forged certificate uploaded to a website completed the Holy Trinity of official looking fiction.

    Everyone is told to check registrations, verify CRD numbers, and read public filings. In this case, doing all that due diligence would have walked a careful investor straight into the trap. The official data did not counter the scam. It amplified it. When the same agency later announces that it has sprung into action to protect investors, it leaves out the awkward part where its own systems served as character witnesses for the defendant.

    What You Are Supposed to Forget

    None of this absolves WealthTutor or whatever name its operators are using this quarter. They built a phony trading app, forged credentials, and siphoned cash from at least three investors, including one seven figure victim. That belongs in court and, ideally, in prison. But if you stop the story there, you have accepted the comforting version. Rogue actors, vigilant regulators, problem solved.

    Look again at the timeline. Retail investors on a subreddit spotted smoke in mid 2024. A state regulator flagged the corporate shell in December 2024. The SEC’s own database showed suspicious registration details paired with unreachable phone numbers and a borrowed CRD number. A counterfeit SEC certificate sat in plain sight on the firm’s website. The federal enforcement machine caught up in late 2026, after the damage.

    The lesson is not that you should distrust every press release. You already do. The sharper lesson is that the symbols you are told to trust (registrations, certificates, public filings) are only as honest as the people who feed data into them and the people who are meant to check that data. In the WealthTutor case, the con artists did their part with unusual enthusiasm. The system did not.

    Next time you pull up an adviser record on a government site and feel the warm glow of institutional reassurance, remember Ichcoin Tech Corp. Remember Indicator Global, WealthTutor, and whichever alias comes next. The file may say registered. The certificate may look official. The only thing you can safely assume is that if the story ever collapses, the same people who built the stage will appear at the end to tell you they were heroes all along.

    WealthTutor represents one end of the federal regulatory spectrum “,” an agency so passive it hosted its own fraudsters’ credentials. The other end is worth examining too. Our coverage of the FTC’s breakroom panopticon documents what happens when a regulator overcorrects: a ten-year consent decree, a government-installed monitor paid by the companies he watches, and a forced asset transfer over a 70% share of the office kiosk market. The SEC’s WealthTutor failure and the FTC’s micromarket overreach are two ends of the same broken dial.

    Sources

    Fediverse reactions

  • Poetry Is Not Sexual Misconduct, and Other Arguments That Did Not Save Chuck Edwards

    When the House Ethics Committee Actually Uses Its Teeth

    The House Ethics Committee does not often recommend censure. It prefers the soft touch of confidential investigations, delayed reports, and sternly worded letters that vanish into the Congressional Record. Yet Rep. Chuck Edwards, Republican of North Carolina’s 11th District, managed to clear that high bar. After reviewing nearly 1,500 pages of evidence and interviewing 16 witnesses, the bipartisan committee concluded that Edwards engaged in what it called persistent unprofessional and inappropriate conduct toward two young female staffers. Faced with that judgment, Edwards produced a 22 page letter arguing, among other things, that poetry is not sexual misconduct and that an affectionate friendship is not a sexual proposition. Those lines will outlast his time in Congress, which suddenly has an expiration date.

    What the Committee Actually Found

    The Ethics Committee’s report in H. Rept. 119 756 reads less like a misunderstanding and more like a pattern. According to the report, Edwards showered the two aides with repeated and lavish gifts, commented on their appearance and dress, invited them to what the committee described as intimate dinners and vacations, and wrote effusive handwritten notes that went well beyond professional appreciation. The committee did not find evidence of explicit sexual propositions or sexual activity. That absence did not save him.

    Instead, the investigators stepped back and asked how a reasonable observer would read the whole picture. Their answer, laid out in the report, was that the pattern of gifts, comments, invitations, and personal notes would reasonably be interpreted as romantic or sexual in nature and that both women were made uncomfortable. The committee emphasized that the aides were not peers or friends in a vacuum. They were subordinates whose careers depended on the approval of the man writing the notes and paying for the trips.

    That power imbalance is what pushed the case out of the familiar gray zone of Capitol Hill gossip and into the territory of official misconduct. The committee found that Edwards violated the House Code of Official Conduct by failing to live up to the spirit of chamber rules that prohibit sexual harassment. On July 22, 2026, the committee voted to adopt its report, and on August 3, 2026, it transmitted the findings publicly. The punishment it recommended was not a slap on the wrist. It urged the full House to censure Edwards, a penalty one step below expulsion that requires a majority vote and forces the member to stand in the well of the House while the resolution is read aloud.

    Committee leaders underscored the gravity in their joint statement. The Republican chair and Democratic ranking member issued a rare united front, describing the process and the findings in careful but unmistakably serious terms. Their public statement reinforced what the report already conveyed: this was not casual or partisan.

    The Defense: Poetry, Friendship, and a Vanishing Campaign

    Two days after the report dropped, Edwards ended his reelection bid for North Carolina’s 11th District, as first reported by outlets including the Washington Post. Reporting from the Post and others noted that House Republicans had privately encouraged him to step aside. That timing was not subtle. A member under threat of censure for sexual harassment findings is a heavy lift even for a party accustomed to weathering scandal.

    Edwards did not go quietly. According to Axios and NC Newsline, he circulated a 22 page letter to colleagues, along with a one page fact sheet titled 15 Questions Members Should Ask Before Accepting the Ethics Report. In those materials, Edwards asserted that the committee had made what he called an extraordinary leap in classifying his behavior as sexual harassment. The now famous line poetry is not sexual misconduct appeared there, along with his insistence that what he described as affectionate friendship was not a sexual proposition.

    Reporters at the Associated Press, Washington Post, Roll Call, and WUNC all chronicled the same pattern. Rather than accept the bipartisan findings and the proposed censure, Edwards spent the August recess trying to persuade colleagues to reject the report. He framed his conduct as misread sentimentality, the committee’s reasoning as prosecutorial overreach, and the sanction as unjust.

    The House was expected to vote on the censure recommendation when it returned from recess on August 31, 2026. While the committee report spoke in the formal idiom of congressional discipline, Edwards’s public and private pushback gave the case a catchphrase. Poetry is not sexual misconduct became shorthand not just for his defense but for its blind spot. The factual record described a workplace dominated by a member’s personal attention. His letter described hurt feelings and misunderstood verse.

    Why This Case Breaks the Pattern

    Congressional ethics cases are usually studies in inertia. The House created a process that is slow, secretive, and highly resistant to public punishment. Complaints often vanish into confidential referrals or are resolved with negotiated admonishments that only surface years later. A bipartisan committee that unanimously recommends censure breaks that pattern. It signals conduct that was serious enough to clear the institution’s own hurdles, not just a partisan skirmish or a fleeting news cycle.

    The Edwards matter is also a textbook workplace power story. The two women at the center of the report worked for him. According to H. Rept. 119 756, they experienced his attention as uncomfortable and untenable, precisely because he controlled their assignments and their futures. The committee did not need an explicit proposition to see a problem. It looked at the gifts, the comments about their appearance, the invitations to intimate dinners and vacations, and the handwritten notes, then weighed those against the simple fact that they were junior staffers in a congressional office.

    Edwards’s poetry defense tries to recast that story as one about tone policing or cultural misunderstanding. The report reads differently. It reads like a rare official acknowledgment that the problem in Congress has never been a lack of policy on paper. The problem has been a culture that treats persistent, unwanted attention from a powerful boss as something less than misconduct unless it escalates to outright solicitation.

    Here, the committee drew the line earlier. It said that sustained, personal attention from a member of Congress to two subordinate employees, accompanied by gifts, personal comments, and intimate invitations, violated the House’s own standard of conduct. That conclusion did not come from a political opponent or an outside activist. It came from a committee evenly split between Republicans and Democrats, working inside a system built to bend over backward for incumbents.

    The Edwards case shows what it looks like when that system finally says no. Whether the full House will reinforce that judgment with a censure vote is a live question. The report already exists, archived on Congress.gov and GovInfo, along with the statement from the committee leadership. Edwards’s own quoted lines now stand beside them. Long after he leaves the House floor, one sentence will still explain how he chose to answer a finding that his conduct crossed the line: poetry is not sexual misconduct.

    The Edwards case sits alongside another rare act of congressional self-regulation from the same period. H.R. 2406 — the NOAA observer harassment bill that cleared the House Natural Resources Committee with bipartisan support in August 2026 — addresses a different but structurally similar problem: workers whose safety depends on institutions that had every incentive not to look too closely. That story and this one share the same uncomfortable premise — that federal workplaces required an act of Congress to extend basic protections to people who were already supposed to have them.

    Fediverse reactions

  • The August Docket: Murder Inside the Wire, a Veteran’s Identity Stolen, and a Gun in a Drug Deal Gone Federal

    Three Indictments, One Press Release, Zero Coherence

    The Southern District of Georgia just announced a murder in a federal prison, a veteran benefits scam, and a felon with a gun in a drug case, all in one neatly stapled press release. It reads less like a sober summary of public safety work and more like a clearance rack of federal sin. One document, three separate universes of misconduct, presented as if they belong on the same shelf. They do, but not for the reason the government thinks.

    The Man Who Was Supposed To Be Neutralized

    Start with Robert Kye Sturdy, 67 years old, already buried alive in a federal sentence. In 1998, a jury convicted him of methamphetamine distribution, marijuana distribution, carrying a firearm during a drug trafficking offense, and being a felon in possession of a firearm for conduct in 1995. A federal judge handed him 600 months in prison, fifty calendar years. The Eighth Circuit signed off in 2000, in United States v. Sturdy, 207 F.3d 448, and the system congratulated itself on removing a dangerous man from the streets for good.

    The Department of Justice later had a chance to reconsider. In December 2023, when clemency requests landed on the same desks that now trumpet his new indictment, the department denied his commutation bid, as recorded in its published list of commutation denials. The message was clear. Sturdy stays in federal custody until the clock or his heart gives out.

    Except the story did not end with effective incapacitation. According to the August 24, 2026 press release from the U.S. Attorney for the Southern District of Georgia, a federal grand jury has now indicted Sturdy for first degree murder while he is an inmate at the Federal Correctional Institution in Jesup, Georgia. The allegation is simple and horrifying. A man the system promised to neutralize for half a century allegedly killed again inside the very institution that was supposed to contain him.

    FCI Jesup is a medium security facility. That label suggests structure, staffing, and supervision that should at least keep homicide from becoming a recurring hobby. Yet here we are. Federal prison violence has long been a national embarrassment, with chronic understaffing and contraband problems documented across the Bureau of Prisons. Sturdy is not a policy paper. He is a living rebuttal to the fantasy that you can lock a person away for fifty years and assume the risk has been safely warehoused.

    Stealing From The People Who Wore The Uniform

    Next on the announcement carousel is Perry Patalano, 63, of Augusta, Georgia. His alleged crime is not physical violence. It is something quieter and, in its own way, corrosive. According to the same DOJ release, a federal grand jury indicted him for healthcare fraud, theft of government money, property, or records, and aggravated identity theft.

    The investigation came from the Department of Veterans Affairs Office of Inspector General, one of the more muscular watchdogs in the federal menagerie. Its public investigative updates show a steady stream of cases targeting people who siphon benefits meant for veterans. That is the context for Patalano. The allegation is that someone stole identities and defrauded the VA, an agency that exists on paper to care for the people who served.

    Augusta sits in a district that includes Fort Eisenhower, home to major military and cyber operations. You cannot throw a rock without hitting a veteran or someone who works in support of them. In that landscape, veteran benefit fraud is not a technocratic crime. It is an attack on the social contract the country keeps promising soldiers in television ads. When the VA OIG shows up, it is usually because that contract has been quietly looted from within.

    The vulnerability of veteran benefit systems to fraud is one symptom of broader accountability gaps across the VA. The same VA OIG whose investigators caught Patalano has also documented — in repeated facility inspections and system-wide audits — that the VA’s internal processes fail veterans in quieter ways every single day.

    The Federal Hammer For A Familiar Street Crime

    The third defendant in the same press packet is Lenard Lorenzo Kearse, 38, of Rincon, Georgia. Local outlet WRDW notes that he had been booked in Chatham County in January 2026. The federal charges that now appear in the DOJ release are the standard issue federal drug and gun combination. Possession of a firearm by a convicted felon, possession with intent to distribute marijuana, and carrying a firearm during and in relation to a drug trafficking crime.

    This is the classic federal trifecta. Drugs, a gun, and a prior felony record. You see it in every district. The crucial point is not novelty. It is scale. Turning a state level drug case into a federal prosecution multiplies the sentencing exposure by design. Congress wrote the felon in possession statute and the drug firearm enhancement to give prosecutors a heavier hammer when they decide a particular defendant is worth the paperwork.

    Kearse is not accused of running an international cartel. He is, according to the indictment summary, a man with marijuana, a gun, and a record who caught the attention of federal authorities in a district already saturated with overlapping local, state, and federal law enforcement. The system reserves its harshest statutory tools for people like him, not because the conduct is rare, but because the structure makes it easy to charge and hard to defend.

    What These Three Stories Share

    So why package these three men together in one press release. The U.S. Attorney for the Southern District of Georgia oversees a jurisdiction heavy with military installations, federal prisons, and ports. That geography produces a steady diet of veteran benefit fraud, in custody violence, and drug firearm cases. From a bureaucratic perspective, the announcement is routine. From a policy perspective, it reads like a confession.

    Sturdy represents the failure point of long sentences as a public safety strategy. He was removed from society for half a century, denied clemency, and still allegedly committed a murder under direct federal control. Patalano reflects the vulnerability of veteran benefit systems that require aggressive inspector general work simply to stay ahead of fraud. Kearse illustrates how quickly a local arrest can turn into a federal case carrying years of additional prison time because of statutory design, not because his conduct is uniquely monstrous.

    The common thread is federal power deployed in three very different arenas with uneven competence. The same government that could not prevent a homicide in its own medium security facility now touts its vigilance in chasing down a benefits fraud scheme and upgrading a street level drug and gun case into a federal prosecution.

    What The System Gets Right, And What It Refuses To See

    To be fair, these indictments are not proof of failure across the board. The VA OIG exists, is funded, and is active enough that people who treat veteran benefits like a personal ATM face consequences. The Southern District of Georgia, sitting on top of Fort Eisenhower and a large veteran population, treats that fraud as a priority. That is how it should be.

    The Kearse case also reflects a choice that many voters say they want. When a person with a prior felony packs a gun while dealing drugs, the federal toolkit is unmistakable. The statutes are clear, the penalties are serious, and the government is not shy about using them. You can argue with the policy, but you cannot accuse the system of being timid there.

    The blind spot lies behind the razor wire. The Sturdy indictment sits uneasily next to fifty years of supposed incapacitation and a recent clemency denial. If the government cannot stop someone already in its physical custody from allegedly committing first degree murder inside a medium security facility, then the claim that longer sentences automatically translate into greater safety outside the walls deserves more skepticism than any press release will ever admit.

    The documents tell the story plainly enough. The August 24, 2026 DOJ release, the 2000 Eighth Circuit opinion in Sturdy, the December 2023 clemency denial list, VA OIG public updates on benefit fraud, WRDW coverage in Augusta, and local reporting from Lanier County News all align on the facts. A man already sentenced to die in prison allegedly kills again inside. A sixty three year old in a military heavy town stands accused of looting veteran benefits. A thirty eight year old with marijuana and a gun now faces federal sentencing multipliers.

    No one needs a sweeping theory to read those together. They are a snapshot of what federal criminal justice in the Southern District of Georgia really does on an ordinary day. It protects some people, fails others, and presents the whole package as a triumph. The job of the public is to read past the headlines and decide which parts look like justice and which parts look like a system congratulating itself for putting out fires it helped start.

    Fediverse reactions

  • Warheads to Watts: The Administrative State’s Multi-Billion Dollar Gamble on Privatized Plutonium

    Plutonium-239: From Waste Liability to “National Asset”

    For decades, the Department of Energy (DOE) treated the United States’ surplus of weapons-grade plutonium as a toxic ledger entry—a multi-billion dollar waste liability destined for dilution and burial in the salt beds of New Mexico.

    This “dilute and dispose” model at the Waste Isolation Pilot Plant (WIPP) was the established fallback, chosen specifically because it was a cheaper and simpler security path.

    However, a sudden strategic pivot has rebranded this Cold War legacy. Following a May 2025 executive order, the administrative state unveiled the Surplus Plutonium Utilization Program, effectively abandoning the simpler security model to transform 19.7 metric tons of plutonium from a “taxpayer drain” into an energy asset.

    This reclassification, marketed as a visionary move toward a “circular energy economy,” is characterized by the DOE as a pivot from management to innovation.

    Deputy Assistant Secretary for the Nuclear Fuel Cycle Josh Jarrell framed the shift as follows:

    “Surplus plutonium was once viewed solely as a nuclear liability and a multi-billion-dollar financial drain on taxpayers—but it doesn’t have to remain one. Thanks to President Trump’s leadership, we are redirecting this Cold War legacy to serve as a vital energy asset, powering the next generation of American nuclear innovation.”

    Beneath the rhetoric of “American energy dominance” lies a classic bureaucratic maneuver: the offloading of a multi-billion dollar liability onto the private sector. By “unlocking private sector funding,” the DOE is attempting to hide the immense long-term costs and security risks of 19.7 tons of high-level nuclear material.

    This investigative report attempts to determine whether the federal leviathan is truly innovating or merely abdicating responsibility to a small circle of startups.

    The Private Gatekeepers: Analyzing the Five-Company “Renaissance”

    The delegation of high-stakes nuclear security to private entities represents a radical departure from the status quo. Management of weapons-grade plutonium, traditionally the exclusive domain of government-run laboratories, is being outsourced to five startups.

    While the DOE touts this as a competitive “renaissance,” the selection process is shrouded in opacity.

    CompanyRole & Operational StatusKnown Operations/Testing
    OkloDeveloping “Aurora” liquid metal-cooled fast reactors.Active plutonium testing at Los Alamos National Laboratory (LANL); utilizing material as “bridge fuel.”
    Exodys EnergyAdvanced negotiations for material allocation and recycling.No specific operational details; status relies on “proprietary processes.”
    Flibe EnergyFocused on molten salt/advanced reactor development.No specific operational details; status relies on “proprietary processes.”
    SHINE TechnologiesSpecialized in plutonium processing and fuel cycle tech.No specific operational details; status relies on “proprietary processes.”
    Standard NuclearNegotiations for conversion of national energy assets.No specific operational details; status relies on “proprietary processes.”

    The lack of operational data for Exodys, Flibe, SHINE, and Standard Nuclear serves as a significant transparency red flag.

    Apart from Oklo’s work at Los Alamos National Laboratory, these entities appear as “paper-based” contenders in a high-stakes negotiation.

    This unprecedented paradigm places the entire administrative and financial burden (the design, funding, construction, and decommissioning) onto companies with unproven infrastructure. By shifting end-to-end facility management to the private sector, the DOE effectively bypasses traditional oversight, creating a scenario ripe for regulatory capture.

    The Fast Reactor Mirage: Engineering Realities vs. Bureaucratic Hype

    The Surplus Plutonium Utilization Program is a bet on “fast reactors,” a technology that offers elegant physics but has historically proven to be an engineering quagmire.

    The U.S. is asking startups to succeed where the federal government failed with the Clinch River Breeder Reactor and where global powers like France (Superphénix) and Japan (Monju) retreated due to high costs and outages.

    Persistent Engineering Realities:

    • The Coolant Dilemma:  Fast reactors generally rely on liquid sodium, which reacts violently with air and water. Sodium is also opaque, which complicates visual inspections of internal components.
    • Sodium-24 Activation:  Liquid sodium is subject to Sodium-24 activation, creating severe radiation handling challenges that add significant complexity to maintenance and repairs.
    • Material Stress:  High temperatures and high-energy neutron bombardment lead to “irradiation swelling” and “cladding corrosion,” punishing reactor components far beyond the limits of standard commercial plants.
    • Safety Dynamics:  Many designs possess a “positive void coefficient.” If the coolant boils or voids, the reactor’s power can dangerously increase, necessitating near-perfect safety systems to prevent core reconfiguration.

    The DOE’s promotion of “elegant physics” ignores the track record of leaks and fires that have historically plagued these systems. The engineering burden placed on these startups is immense, contrasting sharply with the bureaucratic optimism driving the current privatization effort.

    The Proliferation Gamble: Security in the Age of Privatization

    Plutonium-239 is an attractive target for theft and diversion, as it is inherently weapons-usable. The 1974 India nuclear test, which utilized plutonium from a “peaceful” reactor, serves as the historical trigger for modern U.S. proliferation fears. Distributing 19.7 metric tons of this material to private startups is an unprecedented move that heightens global security risks.

    Logistical and Security Challenges:

    1. Direct Weapons Use:  Unlike standard commercial fuel, weapons-grade plutonium oxide and metal can be used directly for nuclear explosives, requiring security measures far beyond standard commercial protocols.
    2. Logistical Chains:  Safe transport requires armed convoys and absolute logistical integrity. Any failure in stabilization or packaging could have catastrophic consequences.
    3. Oversight Limitations:  Providing continuous, independent oversight for five separate private facilities—each guarding “proprietary processes”—will likely overwhelm the IAEA and domestic regulators.

    This program risks significant “mission creep” within the DOE as it attempts to monitor material it no longer directly controls. 

    Whether a private startup can maintain the security standards of a national defense laboratory remains an unanswered, multi-billion dollar question.

    The Shadow of Savannah River: A History of Costly Failures

    The current initiative follows the spectacular collapse of the Mixed Oxide (MOX) Fuel Fabrication Facility at the Savannah River Site. That failure is precisely why “dilute and dispose” became the fallback in the first place, creating a circular loop of bureaucratic and nuclear waste.

    Economic Reality Check:

    • Fiscal Obfuscation:  The Savannah River project was initially estimated at $1-2 billion but ballooned to over $50 billion before its 2018 cancellation.
    • The Cost of Fuel:  Historical data shows that plutonium-based fuels are 3 to 9 times more expensive than standard fuel due to specialized fabrication and licensing.
    • Sunk-Cost Fallacies:  By framing this as a private-sector endeavor, the administrative state attempts to shield itself from future cost overruns, yet the taxpayer remains the ultimate guarantor of the material’s security.

    This pivot appears less like a technological fix and more like a strategy to obscure the inevitable costs associated with a fuel cycle that has historically burned through federal budgets with zero commercial output.

    Global Divergence: The French and Russian Benchmarks

    The U.S. strategy of relying on startups to leapfrog established technology stands in stark contrast to the state-led models of France and Russia.

    CategoryThe French ModelThe Russian Model
    FocusMOX fuel for light-water reactors (LWRs).Advanced fast reactor integration (BN-600/800).
    Proven SuccessMOX provides ~5% of new nuclear fuel globally; France has utilized 7,500+ MOX assemblies.Only nation to successfully commercialize fast reactor technology.
    StrategyGovernment-delivered public good; MOX generates 10% of France’s electricity.High-energy neutron focus for breeding fuel and burning transuranic waste.

    France’s model proves that plutonium utilization can work at scale, but only with massive, centralized government backing. Russia has commercialized the very technology the West views as experimental.

    The U.S. startup gamble ignores these benchmarks, choosing instead a path of maximum complexity and minimal transparency.

    Accountability, Liberty, and the Path Forward

    The DOE’s pivot from “waste” to “asset” is a calculated gamble that shifts risk from federal ledgers to private balance sheets while keeping the inherent dangers of Plutonium-239 very much alive.

    While the potential for energy independence is high, the narrative is riddled with technical gaps and historical failures. The physics of fast reactors may be sound, but the engineering and economic realities remain formidable barriers that have defeated better-funded national programs.

    Whether this program represents a genuine nuclear renaissance or a convenient way for the administrative state to hide an expensive liability depends on the transparency of the upcoming negotiations.

    Lingering Questions for the Regulatory Apparatus:

    1. Fiscal Transparency:  What mechanisms are in place to prevent the DOE from quietly issuing federal subsidies if these “private” projects begin to suffer from the same cost-bloat seen at Savannah River?
    2. Insolvency Safeguards:  What specific, liquid assets do these five startups hold to guarantee the immediate re-securing of weapons-grade material by the state in the event of a Chapter 11 filing?
    3. Verifiable Milestones:  Given the $50 billion failure at Savannah River, what objective, non-proprietary milestones have been established to ensure this program does not become a decades-long financial drain?
    Fediverse reactions

  • The Model Bureaucracy: Inside the PBGC’s Efficiency Engine and the Pension “De-Risking” Trap

    The Paradox of Perfect Transparency

    In the labyrinthine corridors of Washington, the Pension Benefit Guaranty Corporation (PBGC) is a rare bird, in that it claims to have solved the “Red Tape” problem.

    While most federal entities languish under mounting backlogs and decades of administrative decay, the PBGC boasts an 11-year streak of zero FOIA backlogs. It presents itself as a paragon of “model” transparency.

    Yet, this bureaucratic perfection operates as the gatekeeper for the retirement security of 33 million American workers and the $3 trillion in benefits that underwrite their future. For the specialized auditor, this efficiency raises a chilling tension:

    Is a lightning-fast disclosure office a sign of genuine openness, or is it a high-speed machine designed to manage public perception while the “Federal Backstop” is systematically dismantled?

    Beneath the gloss of 12-day response times lies a high-stakes reality where corporate maneuvers and massive taxpayer infusions are reshaping the American social contract. To understand the future of retirement, one must first look through the high-tech lens of the agency’s disclosure engine to see what, and who, is being left behind.

    The Anatomy of a “Model” Program (FOIA by the Numbers)

    The Freedom of Information Act (FOIA) is the primary weapon against government opacity. But in the hands of a master bureaucracy, it can also become a tool for “High-Speed Opacity.”

    The PBGC has integrated FOIA into its core strategic plan, not merely as a legal requirement, but as a performance metric to be optimized. According to the 2025 Chief FOIA Officer Report, the agency’s Disclosure Division operates with a corporate-level efficiency that effectively silences critics of government sluggishness.

    PBGC FOIA Performance (FY 2024)

    MetricStatutory RequirementPBGC Performance (FY 2024)
    Median Response Time (Complex)20 Working Days12 Working Days
    Median Response Time (Simple)20 Working Days10.28 Working Days
    Backlogged Requests/AppealsN/A0 (11 consecutive years)
    Expedited Adjudication10 Calendar Days6.52 Days (average)

    This administrative “perfection” is powered by a technological arms race. The agency utilizes sophisticated AI and machine learning tools that serve as high-tech filters, allowing the bureaucracy to process and redact massive volumes of data at a scale manual reviewers could never match.

    • Veritone Redact:  An AI-enabled cognitive engine that automates redaction in audio and video files, extracting text to ensure the agency’s narrative remains tightly controlled even in multimedia formats.
    • FOIAXpress EDR & Relativity:  Automated platforms that sift through voluminous email caches to “identify” (and exclude) duplicative or non-responsive content.
    • Rapid Redact:  Predictive coding software that the agency claims has saved 50% of review time for bulk records.

    While the PBGC prides itself on these tools, the auditor must ask:

    “Is the speed of the response a service to the requester, or a method of quickly sanitizing the record of the billion-dollar shifts occurring within the Special Financial Assistance program?”

    The Billion-Dollar General Fund Infusion (SFA Transparency)

    The American Rescue Plan’s Special Financial Assistance (SFA) program represents a tectonic shift in the PBGC’s DNA. Historically, the agency was a self-sustaining insurer funded by premiums and investments.

    Today, it has become a conduit for the Treasury’s General Fund. The SFA is “funded entirely by an appropriation from the General Fund,” moving the burden of multiemployer plan sustainability directly onto the taxpayer.

    The SFA is intended to keep insolvent plans afloat through 2051, but the “proactive disclosures” the agency touts are heavily managed. The Disclosure Division reviews every SFA application for “PII and confidential commercial information” before publication.

    This “transparency” serves a dual purpose. First it provides the public with a glimpse of the payouts. Second, it shields the specific financial vulnerabilities and “commercial” secrets of the troubled plans being bailed out.

    As the PBGC manages the optics of these taxpayer-funded lifelines, it oversees a simultaneous and opposite trend on the corporate side, which is the total abandonment of the federal safety net.

    The ERISA Shield and the Verizon Precedent

    While the government bails out multi-employer plans with taxpayer cash, corporations are executing a strategic exit through “Pension Risk Transfers” (PRTs). By offloading liabilities to private insurers, companies effectively dismantle the federal backstop for their retirees, trading ERISA protections for a variable patchwork of state guaranty associations.

    The litigation context of Dempsey v. Verizon (dismissed Jan. 8, 2026) exposes the “ERISA Shield” protecting these maneuvers. In 2024, Verizon transferred $5.7 billion in liabilities for 56,000 retirees to Prudential and RGA Reinsurance.

    The “Core Grievances” were clear:

    • Total Loss of PBGC Backstop:  The federal guarantee vanishes the moment the transfer is signed.
    • Regulatory Fragility:  Retirees are moved from federal safeguards to state associations with varying solvency standards.
    • “Cheapest vs. Safest”:  Allegations that fiduciaries ignored DOL Interpretive Bulletin 95-1 by prioritizing corporate accounting gains over provider safety.

    Judge Alvin K. Hellerstein’s dismissal of the case “with prejudice” highlights a judicial dead-end for workers.

    By ruling that retirees lacked “Article III Standing” because their benefits were not currently reduced, the court labeled the risk of insurer insolvency as “speculative harm.”

    This creates a legal shield, of sorts, where retirees cannot sue until the private insurer fails, at which point the PBGC backstop they once relied upon is already gone.

    The Mechanics of Power—Exemptions and Gaps

    The PBGC’s “Model” status is a carefully constructed outlier. A recent GAO audit of 117 agencies found that many federal entities lack even basic backlog reduction plans, leading the GAO to issue specific recommendations to 16 agencies just to develop them. The PBGC uses this contrast to frame itself as a leader in transparency, yet it leverages the same statutory “gears of secrecy” as its less efficient peers.

    Beyond the standard use of PII and Confidential Business Info exemptions, a significant transparency gap exists. While the agency claims a “customer service” model, it refuses to post FOIA logs in a machine-readable CSV format. The PBGC cites “requester privacy” as the justification, but the effect is the prevention of systemic oversight.

    Without CSV logs, independent auditors cannot track who is requesting information about PRTs or SFA payouts across agencies, effectively creating a “black box” around the influencers of pension policy.

    Accountability vs. Efficiency

    The PBGC has mastered the art of the fast answer.

    A zero-backlog office in a town defined by delay is a legitimate administrative feat. However, we must not mistake a fast response for a secure benefit. Efficiency in disclosure does not equate to security in retirement.

    The PBGC is presiding over a landscape where the “Federal Promise” is being bifurcated: one half is sustained by taxpayer bailouts (SFA), and the other is being sold off to the private market (Verizon).

    The “Model Agency” is effectively the high-speed clerk of a dismantling process, ensuring the paperwork for the erosion of the federal safety net is filed perfectly and on time.

    Open Questions for the Taxpayer:

    • Is a FOIA program truly “transparent” if it hides its request logs behind a privacy shield to prevent systemic, cross-agency oversight?
    • Does the “Article III Standing” hurdle mean that the federal government has effectively licensed corporations to offload pension risks with zero legal accountability to the workers?
    • As the PBGC shifts from a premium-based insurer to a manager of General Fund appropriations, has its primary mission become that of a taxpayer-funded bailout manager for a failing system?

    The PBGC’s erosion of the federal promise to retirees has a parallel in how the VA has handled its promises to veterans and their caregivers. The Caregiver Sunset investigation documents how the VA used the language of ‘equity’ and ‘administrability’ to phase out grandfathered protections for families who built their lives around a benefit that was quietly being restructured beneath them. Different agencies, same mechanism: settled commitments traded for administrative convenience, and the courts declining to intervene.

    Fediverse reactions