Author: Hugh Jass

Hugh Jass is WOYJO’s investigative unit in a trench coat that has never seen daylight. He brings unusual heft to small print, government forms, procurement records, court filings, budgets, contracts, committee minutes, and any document that looks boring enough to hide a crime. Jass writes with the calm menace of a man who has read the appendix and found a second appendix lying about the first. He treats corruption less like lightning and more like plumbing: hidden behind walls, expensive to repair, and usually installed by someone who insists the smell is normal. Where others chase the loudest quote, Jass follows the quiet signature. He wants to know who paid, who signed, who benefited, who buried the memo, and who suddenly discovered ethics after the invoice cleared. His presence in a records room is large, patient, and difficult to move. Categories: Investigations, Politics, Justice, Business, U.S.
  • |

    The Interior Secretary’s AI Investments Meet Public Land

    When the form is broad and the policy is public

    A disclosure may satisfy filing rules and still leave the public asking what, exactly, is in the room. Interior Secretary Doug Burgum’s reported financial interests overlap with his role in advancing data-center development on federal lands. That overlap does not establish improper influence. It does make the paperwork worth reading slowly, preferably with a lamp and the uneasy feeling that a filing cabinet has just cleared its throat.

    What the estimate does—and does not—say

    ProPublica reports that Burgum’s 2026 financial disclosure lists interests in Arthur Ventures, the investment firm he co-founded. ProPublica estimates that $18.1 million to $64.4 million of those investments are in AI companies. That estimate is based on Save Our Parks research, which examined company marketing materials; it is not a precise amount stated on the disclosure form. The form gives broad value ranges. Those are meaningfully different things: a disclosed range is not an itemized account, and an outside estimate is not independently verified accounting.

    The distinction matters because a large-looking estimate can travel farther than the qualifications attached to it. The available record, as described in the reporting, does not turn that range into an exact inventory of Burgum’s AI holdings. The point is not to pretend the estimate says nothing; it is to keep clear what kind of number it is and where it came from.

    The public-interest overlap

    The policy question is concrete even if the financial picture is not exact. Burgum leads the Interior Department as it advances data-center development on federal lands, while the reporting identifies investment interests connected to AI companies. Interior says Burgum complied with ethics and disclosure requirements and that his decisions were not driven by personal investments. That response matters. So does the distinction between compliance and confidence: the department’s position does not, by itself, answer every public question about how decisions affecting public land are reviewed.

    A USGS report on data centers and Bureau of Land Management lands discusses considerations including energy, transmission and water. Those are practical land-management issues, not proof of a conflict. They are also reasons the public may reasonably want to understand what is proposed and how the agency weighs competing considerations. The review process should be legible in the records, not left to inference from a reassuring paragraph or a broad financial-disclosure category.

    The next document matters

    On November 6, Sen. Martin Heinrich sent BLM a letter seeking information about the agency’s authority, proposals, locations, acreage, and plans for environmental review or public comment. That is an oversight request, not a finding of wrongdoing—and it is not evidence that any proposal has become a completed project. It puts a practical accountability question on the record: what information will BLM make available about proposed data centers and the process for reviewing them?

    Public land belongs to the public in more than a ceremonial sense. People should be able to see what is proposed, what is being weighed, and how decisions will be made. The disclosure and Interior’s response are part of the record; so is the senator’s request for more detail. At this stage, the important question is what information the agency provides next.

    Key sources

  • |

    Iran Removal Contacts and the Court’s Notice Process

    Deportation plans have acquired a paper trail with an international address. The Associated Press reported on November 5 that newly unsealed records describe administration contacts with Iran during the war about travel documents and possible routes for removals. AP also reported that a judge required advance notice of finalized deportation plans and written notice before a deportation was carried out. That is a narrow set of facts, but it raises a consequential question: what process governs removals when the destination is Iran and events are unfolding in wartime?

    Contacts, routes, and a notice requirement

    According to AP’s account of the records, the contacts concerned practical removal logistics, including obtaining travel documents and discussing possible routes. AP says the judge required the government to give the court advance notice of finalized deportation plans, as well as written notice before a deportation was carried out. The available account does not establish that the judge ruled on every dispute in the lawsuit, and the notice requirements should not be read as a finding that anyone unlawfully shared information.

    Here the filing cabinet clears its throat. Removal logistics can sound like clerical plumbing—forms, routes, a document that lets someone board a plane—but the consequences land on people, not folders. Advance notice gives the court a chance to know that a finalized removal plan is in place before a deportation occurs. AP describes that process; its report does not, by itself, answer every question about what information, if any, was shared or what protections applied to the people involved.

    The allegation is not the finding

    The separate information-sharing claim comes from the plaintiffs in IALDF v. Rubio. Their complaint alleges that confidential information about Iranian asylum seekers was shared. DHS denies sharing asylum application records. Those are opposing positions, not an established court finding. A complaint records what plaintiffs say happened and what relief they seek; it is not proof merely because it has a case caption and the solemn posture of a document that owns a small desk.

    That distinction is the whole administrative fog bank. The contacts described in AP’s account concern removal logistics, while the court’s notice requirements concern advance warning about planned deportations. The lawsuit’s claim about confidential information is a different issue, and the government’s denial remains part of the public account. Keeping those matters separate is not legal hair-splitting. It prevents a procedural order from being mistaken for a verdict—and prevents a serious allegation from being quietly filed under “already proved.”

    For the public, the useful takeaway is modest but important: AP reports a paper trail of contacts with Iran and a court-imposed notice process, alongside a disputed allegation about information sharing. The reporting makes parts of the process more visible; it does not settle every underlying question. In public life, that is often what records do first: they give the fog a folder number.

  • |

    DOJ’s Informant Rulebook: Recommendations Agreed to, Reforms Still Pending

    The federal bureaucracy has a phrase for the moment when everyone agrees the paperwork should change: “recommendation concurred with.” It is not the same phrase as “change completed,” though the two can look cozy in a status table. In an audit released October 28, 2026, the Justice Department’s Office of Inspector General reviewed confidential-informant policies at ATF, DEA, the FBI and the U.S. Marshals Service. The report’s central lesson is a small but sturdy one: agreement is a promise; evidence is the receipt.

    Policies reviewed, not every operation

    The OIG found the four components were in substantial compliance with applicable guidance. That is important context, not a footnote to be hurried past. The audit reviewed policy content and related controls; it did not establish that every field operation followed or violated policy, and it did not make a broad finding of operational misconduct. The document is careful about its boundaries. The filing cabinet cleared its throat, then stayed inside the lines.

    Within that generally compliant picture, the auditors identified areas needing attention: policies should account for emerging risks, internal controls were not consistent across components, and guidance needed to address electronic payments. The report also highlighted the monitoring of informants authorized to engage in otherwise illegal activity. Those are policy and oversight concerns—not a finding that agents or informants broke the rules. The distinction matters when the subject is confidential sources and the public record can easily grow more dramatic than the evidence.

    Concurrence is not closure

    The OIG made five recommendations, and DOJ and all four components concurred with them. The recommendations address the report’s identified policy and control gaps, including emerging risks, inconsistent controls, electronic payments and oversight of informants authorized to engage in otherwise illegal activity. The agencies’ agreement is not evidence that the reforms are already finished.

    That is where the administrative fog tends to gather. The OIG describes the report as resolved, but that status is not the same as closing the recommendations. The OIG says it will close them only after receiving evidence that the specified changes were made. “We agree” is a useful first entry in the ledger. It is not the final stamped page.

    For the public, this is the unglamorous part of accountability that actually counts. A policy can be sensible on paper, and an agency can accept an auditor’s advice, but oversight still needs proof of implementation. The audit does not claim the informant system broadly failed. It identifies places where rules and controls need strengthening, then leaves the recommendations open to the evidence-and-closure test. That distinction keeps a promise from being mistaken for a completed repair. In government, the document coughed. The next question is whether anyone brings the receipt.

  • |

    The Pentagon Watchdog Sends the Starlink Question to Another Desk

    The Pentagon inspector general received a request to investigate reported Starlink and Starshield disruptions affecting Ukraine and pointed the senators toward the Air Force. The watchdog did not take up the requested investigation. It was a procedural handoff, not a finding about who caused anything. Still, the paperwork has moved: AP reported the response on October 28, and a separate Senate inquiry is seeking information from both the Defense Department and SpaceX.

    What the senators want examined

    The bipartisan request, led by Senators Jeanne Shaheen and Thom Tillis, asked the inspector general to examine a precise and consequential question: whether U.S. officials directed, authorized, approved, or knew in advance about changes affecting Ukraine’s access to Starlink. Those are questions for an investigation, not established facts. The distinction matters. A question printed on congressional letterhead remains a question, even when the letterhead is very good at making paper look like it knows something.

    According to AP, the inspector general said the concerns were better addressed by the Air Force and declined the requested investigation. That referral does not establish that the Air Force made or approved changes, nor does it answer what U.S. officials knew. It tells us where the watchdog thinks the issue should be handled next. In the records room, that is movement—but not resolution. The file has changed desks; the contents have not magically become findings.

    A separate inquiry, with a deadline

    Senator Richard Blumenthal announced a separate inquiry seeking information from the Defense Department and SpaceX. His announcement sets November 5, 2026, as the deadline for written responses. As of November 2, that deadline is still ahead. The inquiry therefore represents a request for records and answers, not evidence that either recipient has responded or that the questions have been settled.

    The two efforts should not be folded into one grand investigative machine. Shaheen and Tillis asked the Pentagon inspector general to investigate; that office declined and referred the concerns to the Air Force. Blumenthal’s inquiry is separately seeking information from the department and the company. The Senate releases document what lawmakers asked for, while AP reports the watchdog’s response. None of that, on its own, tells the public who made the relevant decisions, what authority applied, or whether anyone had advance knowledge.

    That is the uncomfortable center of the story: the unresolved issue is not merely which office owns the folder, but how decisions affecting access to a privately operated communications service were made and what government officials knew. Oversight is supposed to make that chain visible to the public. For now, the record establishes a referral, two congressional efforts, and a deadline approaching. The document coughed. The answer has not.

  • |

    GSA’s Google Drive Had 116 Sensitive Files Shared Agency-Wide

    The filing cabinet has cleared its throat: a General Services Administration inspector general audit found 116 files containing controlled unclassified information shared with all GSA users. That means agency-wide access—not public access on the internet. The distinction matters. So does the fact that the audit found information that should have had tighter controls where it did not belong.

    A search, not a census

    The GSA Office of Inspector General examined a drive containing about 2.5 million documents. Its search used 39 keywords and judgmental sampling, and it looked only at documents shared with all users. The team tested nine of 23 controlled unclassified information categories. The report explicitly says its results cannot be projected to the full drive. In other words, 116 is a documented finding in a limited search, not a measured exposure rate for millions of files. The paperwork has numbers; it does not have permission to pretend they mean more than they do.

    The alarm system had gaps

    The audit also found weaknesses in GSA’s ability to detect this kind of improper sharing. The agency had not completed a review of search terms, and an optical-character-recognition feature—which can help find text inside scanned documents—had not been implemented. Those are not proof that more files were exposed. They are reasons the search-and-detection process may not have been as dependable as it needed to be. A security tool that is still waiting to be implemented is less a guard dog than a very formal memo about a future guard dog.

    This was not the OIG’s first visit to the subject. The report describes earlier oversight concerns dating to 2014, findings in 2015 through 2017, and another in 2025. It makes seven recommendations. GSA’s chief information officer concurred with them, according to the report. Concurrence is a useful entry in the record; implementation and effective controls are the part that has to survive contact with daily operations.

    What the finding does—and does not—say

    The OIG’s finding of improper agency-wide access should not be blurred into a claim that the files were exposed outside the agency. FedScoop separately reported GSA’s statement that its review found no indication of external exposure or malicious intent. The OIG audit does not establish that anyone accessed, stole, or misused the files. It does identify files containing personal information and sensitive building-security material, which gives the access-control failure a human edge without proving that anyone suffered a specific harm.

    People whose information or safety depends on federal records handling do not need every document to be public for a control failure to matter. Agency-wide sharing is a real access problem even when there is no evidence of outside access. The audit gives readers a bounded warning and a paper trail: a limited search, gaps in detection, a history of oversight concerns, and seven recommendations accepted by the CIO. The next accountability question is whether GSA puts those controls in place—and whether they work. Hugh will be in the records room, listening for the filing cabinet to answer.

  • Medicare Drug Claims Met a Code Check With No Guard at the Door

    Medicare claims can encounter many checks on their way through the system. One relevant check, it turns out, was missing: a system edit to verify that the procedure code billed alongside a drug matched the codes associated with that drug in CMS crosswalk files. The HHS Office of Inspector General has now put that gap on paper, where it sits with the stillness of a form that knows it has been noticed.

    OIG reviewed Medicare Part B outpatient drug claims from April 1, 2024, through March 31, 2025. It identified 160,918 claim lines with procedure-code and drug-code mismatches when compared with the CMS crosswalk files. A mismatch is a flag for review, not proof that a provider used the wrong code or that Medicare paid incorrectly. The crosswalk is a reference; the finding says the codes did not line up with it.

    Medicare paid $27.6 million for those claim lines. That figure needs its own guardrail: OIG did not determine whether the mismatches caused overpayments or underpayments across the 160,918 lines. So this is not a report establishing $27.6 million in losses, recoverable money, or improper payments. It is the amount paid on claims that met the report’s mismatch criteria. The number is large; the conclusion is narrower.

    OIG also examined a nonstatistical sample of 30 claim lines. In that sample, it found incorrect procedure codes on 24 lines. Eleven of those 24 were paid under a system in which the errors could have resulted in improper payments. Those are sample findings, not a projection about all 160,918 lines. The sample shows why the mismatch deserved scrutiny; it does not calculate the overall financial effect.

    The report identifies two control weaknesses. CMS and its contractors lacked system edits to check the relevant code matches, and provider education did not specifically address those mismatches. In bureaucratic terms, the paperwork could identify a pairing worth checking, but the routine gate did not perform that check—and the guidance did not put the issue plainly in front of providers. The filing coughed; the controls remained seated.

    For patients and taxpayers, the useful takeaway is not that every flagged claim was wrong. It is that a national oversight system had an identified code-matching risk without a specific automated check or targeted education, while the report could not establish the payment impact across the full set. That distinction matters. Accountability begins with finding the missing check, then measuring what it actually allowed through—not turning a flagged total into a verdict the audit did not reach.

  • EPA’s Q3 Fine Ledger: 183 Settlements, and a Lot of Paperwork

    EHSLeaders’ October 16 roundup reports that the EPA finalized 183 settlement agreements in the third quarter of 2026, resulting in $18,806,353 in fines. That is a crisp national tally: three digits for settlements, eight for dollars, and the pleasing sensation that somebody has made the filing cabinet sit still long enough to count.

    One important label belongs on the number before it walks out of the records room: this is EHSLeaders’ compilation, not an EPA-published quarterly report. The EPA pages available for checking enforcement activity do not independently confirm the roundup’s combined Q3 totals. The figures should be read as a trade outlet’s account of the quarter, not as an official EPA aggregate.

    A tally with several kinds of paperwork

    The roundup’s examples span different compliance problems, including pesticide labeling, emissions controls, leak inspections and permits. That range is the useful part of the headline. “Environmental enforcement” can sound like one large agency stamp descending from the clouds; the reported examples point instead to distinct rules and records, each with its own small administrative weather system.

    The EPA’s civil and cleanup enforcement case listings let readers examine cases and settlements individually. Its ECHO tool provides facility-level information, including inspection, violation and enforcement records. The agency’s enforcement data and results page also directs users toward enforcement information and related tools. These public resources give the national number somewhere to be examined—but they are not a second source confirming EHSLeaders’ quarterly arithmetic.

    What the headline can—and cannot—tell us

    A compiled total is useful because it gives readers a quick view of reported enforcement activity across a crowded landscape. It is also a summary, and summaries leave details behind. A reader looking at the EPA listings or ECHO is looking at underlying case- or facility-level records, not at a ready-made confirmation of this particular quarterly count. The tally and the records serve related but different purposes.

    The figure of 183 should not be mistaken for 183 unique facilities, and the reported fine total should not be treated as money collected. The case-level records are where the particulars live; the headline is only the index card. Without treating the roundup as an agency-certified count, readers can still use it as a prompt to look at the records and ask what sits beneath a national summary.

    That distinction matters to anyone trying to understand how environmental rules are enforced, rather than merely admire a large number wearing a badge. The roundup offers a timely snapshot and a range of examples. EPA’s databases offer ways to inspect underlying records, but they do not turn this particular compilation into an agency-certified quarterly count. The paperwork has cleared its throat. The responsible next step is to keep the source of the tally attached to the tally.

  • |

    GoPro’s Books Needed a Second Take

    The filing blinked first

    At GoPro, correcting the books did not stay confined to the books. In an October 16 Form 8-K filed with the SEC, the company said previously issued financial statements should no longer be relied upon. Three days later, GoPro filed an amended 2025 annual report describing the accounting errors and their effects across multiple periods. The paperwork has the measured tone of a filing cabinet clearing its throat, followed by the less measured realization that financing agreements are also in the room.

    Warrants, discounts and a restatement

    The amended report traced the errors to accounting for certain warrants and related debt discounts. GoPro restated financial information for affected periods, including reported net loss and other items. That is a meaningful correction even without a dramatic change to the top line: the company said the errors did not affect revenue or total operating cash flows. A restatement is not one universal red pencil sweeping every number off the page; here, the filing identifies what changed and what did not.

    The consequences crossed departments

    GoPro also disclosed a material weakness in internal control over financial reporting. That is a statement about controls, not proof of intentional misconduct. But controls matter because complicated accounting has to travel safely from the people recording transactions into financial statements that investors and lenders rely on. When the route has a weak point, the error can acquire paperwork of its own—and, in this case, the company reported consequences under financing agreements.

    Defaults, with waivers

    The company said the accounting errors resulted in defaults under certain financing agreements. It also said it obtained waivers on October 16. Both facts belong in the same sentence: the filings disclose defaults, and they disclose waivers. They do not establish that the defaults remained uncured, nor do they describe consequences beyond what GoPro reported. The distinction matters. A technical accounting correction can have contractual implications even when revenue and total operating cash flows are unchanged, but the documents do not invite readers to fill in missing outcomes with ominous guesses.

    Paperwork is part of accountability

    GoPro’s proposed transaction with Starman Optical appears in separate proxy paperwork as context; the filings do not say it caused the accounting errors. The more useful lesson is less cinematic and more important: financial controls have to catch complex accounting before errors show up in statements and financing agreements. The amended annual report gives investors a clearer record of what was corrected, what remained unchanged, and where GoPro identified a control weakness. In corporate life, “technical” is not another word for “irrelevant.” Sometimes it is where the obligations are hiding.

  • The Massage-Therapy Placement Rate That Fell From 83% to 3%

    On October 13, the Education Department’s inspector general issued a report on National Holistic Institute’s Advanced Neuromuscular Massage Therapy program. For the 2023–2024 award year, the institute reported that 83% of graduates were placed. The OIG recalculated the rate at 3. Somewhere between the first percentage and the second, the filing cabinet cleared its throat.

    The denominator stayed put

    The calculation involved 29 graduates. The institute counted 24 placements; the OIG found that 23 of those 24 did not qualify under its analysis. That left one qualifying placement among 29 graduates, producing the report’s 3% rate. This is not a finding that every counted placement was invalid, or that every program at the school had the same problem. It concerns this program and this award year.

    A placement percentage is not simply a tally of people who appear to have found work. To count toward the federal eligibility test, placements must meet the applicable rules. The OIG found that the program met nine of the ten short-term-program eligibility requirements but failed the requirement that at least 70% of graduates be placed. The institute’s reported 83% was above that line; the OIG’s recalculated 3% was not.

    Recommendations are not completed actions

    The report says the program became ineligible for Direct Loans beginning with the 2024–2025 award year. The OIG also recommended that Federal Student Aid require improved procedures, seek the return of Direct Loan funds awarded to students enrolled after the 2023–2024 award year, and review the program’s Title IV eligibility for later award years.

    Those are recommendations, not a list of actions the report says have already been completed. The report does not establish that Federal Student Aid has recovered funds, put new procedures in place, or completed a later-year eligibility review. Paperwork has a way of making future tense look official, but it remains future tense.

    For students and families weighing a short-term program, the practical question is what a published placement rate counts—and whether those placements meet the rules tied to federal aid eligibility. This report does not settle the quality or outcomes of every massage-therapy course, and it is not a review of every short-term program. It shows how one program’s reported number changed when the supporting placements were checked against the eligibility standard.

    That is the unglamorous work of oversight: not merely reading the percentage, but opening the folder underneath it. When federal loan eligibility depends on a documented result, the documentation is not a footnote. It is the result’s pulse.

  • |

    The Supreme Court Takes Up the Question of Who Gets to See DOGE’s Records

    On October 13, 2026, the Supreme Court agreed to hear the administration’s challenge to discovery in a case over records sought from the U.S. DOGE Service. That is a real procedural step. It is not a ruling that DOGE must answer FOIA requests, and it is not an order to release the records. The docket has opened a door to argument; it has not sent a records clerk sprinting toward the copier.

    The request and the refusal

    Citizens for Responsibility and Ethics in Washington, or CREW, sought DOGE records that included organizational information and financial disclosures. The government declined to process the request, saying DOGE was not subject to the Freedom of Information Act. CREW then sued. In its filing opposing Supreme Court review, CREW describes seeking discovery—information gathered during litigation—to help establish whether DOGE falls within FOIA’s reach.

    The administration is challenging the discovery allowed in the lower-court litigation. The dispute matters because information gathered there could help the parties address whether DOGE qualifies as an entity covered by FOIA. CREW’s filing gives its account of the request and the discovery dispute; it is a party’s argument, not a final judicial finding about DOGE’s status.

    What the Court has—and has not—done

    The Supreme Court docket records that the Court granted review on October 13. The case before the justices concerns discovery relevant to CREW’s FOIA case and DOGE’s status under the law. Discovery is a process for gathering information in a lawsuit. It is separate from deciding the ultimate legal question, and separate again from ordering an agency or other entity to disclose records to the public.

    That distinction is the whole machine. The Court has not decided whether DOGE is covered by FOIA. Nor does agreeing to hear the administration’s challenge mean the justices have endorsed the administration’s position or CREW’s. The grant concerns what information may be gathered as the case proceeds; it does not resolve what the requested records ultimately must reveal, or whether they must be released.

    For people trying to understand how a powerful government operation is organized and financed, the dispute matters because access rules determine what can be examined in public. But the development now is about the process for testing DOGE’s legal status, not a completed transparency ruling. A case can advance to the Supreme Court while the records remain undisclosed and the central FOIA question remains open. Paperwork can travel a long way while disclosure stays in the waiting room, holding a numbered ticket.

    Sources

End of content

End of content