Skip to content
Hugin
A single stack of bound ledgers standing on a polished stone floor in a vast, empty columned hall.
Public recordOpen file027D83E7

Public record case file · Latest recorded event Oct 19, 2026

Public Spending Misuse

Accountability file

A public-record case file for reviewing federal awards, Treasury outlay context, Inspector General reports, pandemic-spending oversight, and recipient-integrity records. It separates official spending records, audit findings, and credential-gated exclusion checks from claims about waste, fraud, abuse, or misuse.

Original editorial artwork generated for Hugin.

Latest recorded event
Oct 19, 2026
Source Anchors
40 verified · 176 leads
Timeline
32 events
Roles
7 public-record
Fingerprint
027D 83E7 AE2E
Saved reading0In this browser

Keep roles, events, and source records here to pick up later. Your list stays in this browser and can be lost if you clear site data. Copy your saved links to keep a backup in your notes.

Your reading list is empty. Use a save button on an event, source, or role dossier to add it here.

Start reading

32 events · 7 roles · 40 sources

Recent developments in the record

The latest dated events in this file. Open an event for its cited sources and evidence limits.

  1. OPM's administrative-leave rule prints at 91 FR 65924 effective November 18, with the leave still booked in the same undifferentiated category GAO asked OPM to split →records release · 3 source records
    Read summary and limits

    The final rule OPM filed for public inspection on October 16 printed in the Federal Register of Monday, October 19, 2026 at 91 FR 65924-65940, and its DATES line now names November 18, 2026 as the effective date - the date this desk had counted from the inspection copy's unfilled bracket, now stated by the document itself. The printed text carries the same substance: leave given in connection with deferred resignation programs and other workforce realignment initiatives is listed among the acceptable uses of administrative leave, an agency may but need not place a reduction-in-force-affected employee on administrative leave during the notice period, and an employee's acceptance of deferred-resignation benefits is added to the nonexclusive list of valid reasons an agency may decline a resignation withdrawal, with avoidance of adverse action proceedings still not a valid reason. What the printed rule does not add is any new accounting: its Paperwork Reduction Act section states it imposes no reporting or recordkeeping requirements, and the only tracking it discusses puts the leave in agency timekeeping and payroll systems as administrative leave - the same undifferentiated category that led GAO, in its September audit putting 2025 paid administrative leave at $9.5 billion with about $6.7 billion tied to the deferred resignation program, to report that OPM cannot state the cost of workforce-reduction leave and to recommend a separate category for it. This desk compared the inspection copy against the printed text word for word and found no substantive difference other than the filled DATES line; nothing in the printed rule closes GAO's recommendation.

    Evidence limits. A printed rule and an audit, not a finding of improper payment, waste or misconduct by any agency, official or employee. That the rule adds no recordkeeping is read from its own Paperwork Reduction Act statement, and that it does not address GAO's recommendation is an observation about this document's text, not a statement about what OPM has done elsewhere or about the recommendation's status in GAO's database, which this desk did not check. GAO's dollar figures are payroll-derived estimates with its own stated limits. Whether the leave this rule codifies is lawful is contested in the comments and settled by neither document, and publication does not settle it. The agreement between this desk's computed November 18 and the printed November 18 is recorded as agreement on this one document only.

  2. OPM files a final rule codifying deferred-resignation administrative leave, and states in the same document that it adds no reporting or recordkeeping →records release · 2 source records
    Read summary and limits

    OPM's final rule amends 5 CFR part 630 subpart N and the related reduction-in-force and resignation rules to list leave given under a deferred resignation program or another workforce realignment initiative among the acceptable uses of administrative leave under 5 U.S.C. 6329a, and to give an agency sole and exclusive discretion over a request to withdraw a resignation, with receipt of deferred-resignation benefits a valid reason to refuse. OPM says it is codifying policies already in effect, including a Governmentwide cap of 12 weeks per instance for workforce-realignment leave from calendar year 2026 absent joint OPM and OMB approval of more - a 6-month threshold was approved for fiscal 2026 agreements - and for that reason projects no incremental cost, putting 2025 deferred-resignation separations at over 6 percent of the workforce and the leave's one-time cost at under 3 percent of basic payroll. Of 30 comments, several argued the leave routes around reduction-in-force safeguards and the statutory caps on voluntary separation incentives; OPM disagreed, declined to withdraw the provisions, and said a retrospective accounting of the 2025 programs was beyond this rulemaking's scope. This desk reads the rule against GAO's September audit on the same leave, which put 2025 paid administrative leave at $9.5 billion with about $6.7 billion tied to the deferred resignation program, reported that OPM cannot state the cost of workforce-reduction leave because it sits in the same category as ordinary administrative leave, and left open a recommendation that OPM create a separate category for it. The rule's Paperwork Reduction Act section states that it 'does not impose any reporting or recordkeeping requirements', and where it does discuss tracking - leave under a settlement agreement - it says the usage 'will be tracked as administrative leave in agency timekeeping and payroll systems', the same undifferentiated category. The rule does not address GAO's recommendation and nothing read here closes it.

    Evidence limits. A rule and an audit, not a finding of improper payment, waste or misconduct by any agency, official or employee: employees on this leave were placed on it under a program OPM directed, and GAO's figures are payroll-derived estimates with its own stated limits. Whether the leave this rule codifies is lawful is contested in the comments and settled by neither document. That the rule adds no recordkeeping is read from its own Paperwork Reduction Act statement; the status of GAO's recommendation is GAO's to record, and this desk did not check its recommendations database.

  3. GAO: CMS has put $10 billion of a $50 billion rural health program out to all 50 states, and most of the oversight GAO measured is still a plan →audit report · 1 source record
    Read summary and limits

    GAO reported on the first year of the Rural Health Transformation program, created by Public Law 119-21 in July 2025 and run by CMS as cooperative agreements with states. CMS released a notice of funding opportunity in September 2025, created an Office of Rural Health Transformation in December 2025 that, according to CMS officials, had onboarded 24 of 30 planned staff as of July 2026, and awarded $10 billion for the program's first budget period, which runs to October 30, 2026. Every state received $100 million in baseline funding, half the $10 billion, with the rest scored on rural characteristics and a technical score that counted the strength of proposed initiatives, Medicaid data quality and dual-eligible integration, and whether a state had adopted or would commit to policy actions CMS selected — among them restricting SNAP benefits on non-nutritious foods, adding nutrition to physicians' continuing medical education, and reestablishing the Presidential Fitness Test in schools. Allotments ranged from $147 million for New Jersey to $281 million for Texas. GAO found CMS's planned post-award monitoring generally consistent with selected requirements in 2 C.F.R. part 200, and said in the same breath that it is too early to know whether the implementation will meet them: as of July 2026 CMS had held bimonthly meetings and completed 21 site visits, but had reviewed no state reports, was still finalising the reporting forms and seeking OMB approval for them, and did not plan to begin auditing states' use of funds until 2027. The remaining $40 billion is to be allotted over four years on numerical scores CMS derives from states' own progress reporting; the first annual report was due August 31, 2026, covering December 29, 2025 through July 31, 2026, while the report's endnote 9 puts the first quarterly report due November 29, 2026. CMS may withhold, reduce or recover funding for unallowable costs, unapproved changes to initiatives, failure to finalise a committed policy action by its deadline, or improper management of funds, after giving a state 90 days to address the violation — and the statute bars administrative or judicial review of allotments, withholdings, reductions and recoveries, with CMS still deciding whether the HHS Departmental Appeals Board has any role. Three stakeholder groups GAO interviewed said states had too little time to show progress before budget period 2 scoring. GAO made no recommendations and HHS offered technical comments only.

    Evidence limits. A program-implementation report, not a finding of waste, fraud, abuse or misuse by CMS or any state, and not an audit of any state's spending. GAO's consistency finding is about plans against selected requirements, and GAO itself says it is too early to judge the implementation. The counts attributed to CMS officials are CMS's, not GAO's measurements. Nothing here says any dollar was improperly spent.

Read the full timeline →
Read the case scope: what is included and excluded

Included in this file

  • Official federal award rows and recipient identifiers from USAspending.
  • Treasury Fiscal Data outlay rows that provide program and fiscal context.
  • Inspector General and PRAC/Pandemic Oversight report sources for findings, recommendations, recoveries, and open oversight questions.
  • SAM.gov exclusion status once a server-side key is configured.
  • A source-backed review queue that asks whether award, outlay, audit, and recipient-integrity records can be joined.

Outside this file’s scope

  • Calling a recipient fraudulent, corrupt, wasteful, or abusive from an award record alone.
  • Publishing private taxpayer, employee, beneficiary, whistleblower, or victim-identifying information.
  • Treating a news claim, political statement, or timing overlap as an official misuse finding.

What remains unresolved

These questions stay open in the case file.

  • Which award recipients, UEIs, agencies, and dates can be normalized across USAspending and SAM.gov?
  • Which Treasury MTS line codes are most useful for program-level spending context?
Read all 17 open questions →
Connection map

How the public record connects

Graph JSON

This view starts with the roles that have the most source-record links in this file. Explore Role Web and Timeline for the full set. A line represents a shared source record; it does not establish conduct or a direct relationship.

Publishing limits

These are the standards every anchor on this file must clear.

Minimum source tier
  • spending record
  • audit report
  • oversight report
  • recipient integrity record
  • official record
Living people
For living officials, employees, or recipients, publish only source-backed roles and record relationships; do not infer intent or misconduct.
Victim protection
Do not publish private taxpayer, beneficiary, whistleblower, employee, or victim-identifying details unless an official source makes them necessary and public.
Social leads
Social posts and articles can start a review queue, but spending-misuse claims require official award, audit, legal, or exclusion records.

No guilt by proximity

A recipient, agency, or program appearing in a spending record is a public-record relationship only and does not imply misuse.

Filed
Hugin · public social evidence reports
License
Text and data are shared under the terms noted at hugin.studio/support · attribution appreciated.
Fingerprint
027D 83E7 AE2E
For researchers & contributorsSource desk, research joins & machine-readable exportsEverything Hugin uses to grow and audit this file — connection detail, review posture, scout queue, and every export.
Connection map

How the public record is joined

Graph JSON
timeline backed32
source links46
role links9
open queues2
Source groups
15 sourcesaudit report15 linked recordsOversight.gov Inspector General reports / GAO Reports Feed / GAO federal award and payment eligibility data interoperability report
11 sourcesofficial record11 linked recordsDOJ Trade Fraud Task Force aggregate enforcement milestone / DOJ Seafood Supply Co. Lacey Act sentencing record / DOJ Census Bureau procurement-bribery sentencing record
Timeline joins
Jun 30, 2026 / officialHugin opens public-spending source pack8 linked recordsA source pack is infrastructure for review; it is not a claim that any spending was misused.
Jun 30, 2026 / officialUSAspending award import remains live1 linked recordAn award row is a public spending record, not evidence of misuse by itself.
Role joins
spending record publisherTreasury Bureau of the Fiscal Service2 linked recordsTreasury publication confirms public spending records, not whether a payment was improper.
audit authorityOversight.gov / Inspector General community1 linked recordEach report must be cited directly; portal presence alone is not a finding.

Connections are navigation aids. They show where a record, event, or role is sourced; they do not convert association, correspondence, testimony requests, or document appearance into misconduct findings.

source leads176
automated probes264
verified anchors40
review backlog117
scout targets240
first-pass scout216
credential queue16
connectors30
keyless APIs72
free-key targets16
public search136
official pages8
POST templates8
CourtListener Search API / keyless apiGDELT DOC API / keyless apiFederal Register API / keyless apiGovInfo public document search / public searchRegulations.gov public search / public searcheCFR public search / public searchDOJ News API / keyless apiFOIA.gov government website search / public searchFBI Vault search / public searchNational Archives Catalog API / free key requiredData.gov CKAN catalog API / free key requiredCongress.gov public search / public search

Public-money source desk for award, payment, audit, exclusion, and oversight joins that need identity confidence before promotion.

Source lanespublic-spending-oversight, public-record-discovery, regulatory-anchors, civic-influence
Sharing stateautomatic sharing disabled
Next actionBuild recipient-level packets only after award, payment, audit, and eligibility rows agree on identity and legal posture.
keyless apiCourtListener Search APIUSAspending award and recipient deltasLegal search across opinions, dockets, RECAP data, judges, and arguments.
keyless apiGDELT DOC APIUSAspending award and recipient deltasCoverage-index discovery for fresh public reporting rows.
keyless apiFederal Register APIUSAspending award and recipient deltasOfficial rule, notice, and agency-document discovery.
public searchGovInfo public document searchUSAspending award and recipient deltasFree public search across official publications from all three branches of the U.S. federal government.
USAspending award and recipient deltasTreasury payment and monthly statement joinsGAO and inspector-general report updatesSAM exclusions, OFAC list matches, and recipient identity checksOversight.gov, DOJ, and agency inspector-general spending findingsFederal Register notices tied to awards, eligibility, and program controlsOFAC, SAM, and recipient exclusion source checksSEC EDGAR and recipient entity-reference joins

Source leads and automated probes are review inventory. They become verified anchors only after Hugin can attach the public record, legal posture, and no-allegation guardrails.

Join board

Public-record joins are wired into exports

These are not loose TODOs anymore. Each lane below is computed from the case file's source tiers, then joined to matching sources, timeline events, role nodes, and release-roadmap requests.

wired lanes4
review lanes2
source joins40
release joins0
Wired lanes4Computed from the source tiers and joined to live records, roles, and releases.
WiredIG report issue index
17 sources

Index report number, agency, findings, questioned costs, recommendations, and management response.

timeline16
roles4
release asks0
Connected roles
Oversight.gov / Inspector General communityU.S. Government Accountability OfficePandemic Response Accountability Committee
Release requests
No release request is attached to this lane yet.
PublishesReport metadata, finding posture, recommendations, and follow-up status.
BlockedExtending report findings to recipients, officials, or programs outside the cited report scope.
WiredAward and recipient normalization
2 sources

Normalize award ID, recipient name, UEI, agency, dates, and amount before any contractor or program review.

timeline3
roles1
release asks0
Connected roles
Treasury Bureau of the Fiscal Service
Release requests
No release request is attached to this lane yet.
PublishesAward metadata, recipient identifiers, agencies, amounts, and source URLs.
BlockedCalling an award suspicious, wasteful, or improper without a cited audit, legal, or oversight record.
WiredOFAC sanctions identity resolution
2 sources

Join OFAC rows only through strong identifiers, aliases, addresses, list IDs, and update dates before displaying recipient, issuer, donor, or person relationships.

timeline2
roles2
release asks0
Connected roles
SAM.gov exclusions registryOFAC Sanctions List Service
Release requests
No release request is attached to this lane yet.
PublishesExact-match sanctions-list status, unresolved identity-match gaps, list metadata, and source URLs.
BlockedTreating a name-only sanctions match as a confirmed identity or evidence of public-spending misuse.
WiredTreasury outlay context
2 sources

Join MTS line codes and classification descriptions to program/agency review questions.

timeline3
roles1
release asks0
Connected roles
Treasury Bureau of the Fiscal Service
Release requests
No release request is attached to this lane yet.
PublishesOutlay context, fiscal-period comparisons, and review questions.
BlockedPresenting large outlays as misuse without agency, award, and oversight evidence.
Needs review2Sources have landed but the lane is not promoted to wired yet.
Needs reviewSingle Audit joins
15 sources

Configure FAC_API_KEY and join auditee UEI/EIN, audit year, ALN/program, finding reference, and questioned-cost rows to award recipients.

timeline15
roles3
release asks0
Connected roles
Oversight.gov / Inspector General communityU.S. Government Accountability OfficeFederal Audit Clearinghouse
Release requests
No release request is attached to this lane yet.
PublishesSingle Audit metadata, finding scope, report package links, and unresolved recipient joins.
BlockedTreating a Single Audit finding as proof of fraud, waste, abuse, or misconduct outside the cited audit scope.
Needs reviewSAM.gov exclusion checks
2 sources

Configure a server-side SAM_GOV_API_KEY before importing exclusion records.

timeline2
roles2
release asks0
Connected roles
SAM.gov exclusions registryOFAC Sanctions List Service
Release requests
No release request is attached to this lane yet.
PublishesCredential gap status and manual SAM.gov source links.
BlockedInferring exclusion or debarment status from names, articles, or unverified third-party lists.
Public utility

Help grow the source queue

Hugin accepts public records, not accusations. A submitted URL lands in a review lane, gets source-validated, and only becomes a case anchor after the evidence rules and privacy gates are satisfied.

Review posture

What this case can prove right now

Fact-check desk
publishable claims29
source repair0
known anchors40
lead quarantine0
scout targets240
first-pass scout216
credential queue16
scout connectors30
rankhigh471 priority score
readyReady for first-pass public review29 publishable claim rows / 40 source anchors / 216 first-pass source rows
actions6 start-here rows9 total workbench action rows
blockers2 launch checks16 source-scout rows require free operator keys

Fact-check status is a review posture, not a verdict. Source-scout rows are leads until a reviewer joins them to publishable anchors; claim-ledger rows are timeline-derived and still require source validation plus no-allegation guardrails before promotion.

Source intake

Queue a public record

Public queue

Paste an official or public-record URL. Hugin classifies the lane first, keeps lead-only material quarantined, and requires source validation before anything reaches the case file.

Use an official or public-record page. Local, private, leaked, or credentialed URLs are rejected.
Queue a public source for review.
Visible queue

Latest submitted public URLs

Sanitized queue view: Hugin shows the public URL, lane, status, and why a source has not been promoted. Submitter identifiers are not shown.

Public queue loaded.Live queue connectedQueue hash d731c0cdc68d
No public submissions in this snapshot.When someone submits a source, this board will show the URL, lane, status, hold reason, and next review step before anything can become part of the case file.
known sources40
publishable anchors32
atlas sources8
keyless feeds6
release asks7
document jobs40
privacy triage4
lead quarantine0
01Submit URLPublic URL, label, and context enter the source queue.
02Classify laneOfficial, court, legislative, civil, state, repository, or lead quarantine.
03Validate sourcePublisher, date, scope, privacy, and duplicate checks run before promotion.
04Promote anchorOnly source-backed, privacy-cleared records can join timeline or role surfaces.
Contribution guide

Submit sources, not claims

A source is a public URL someone else can inspect. A claim is an interpretation. Hugin queues sources first and keeps claims out until a reviewed public record supports the exact wording.

Accepted

Official agency pages, court dockets, congressional releases, civil records, state updates, and public repositories with source URLs.

Publisher, date, record family, and why the URL belongs in this file.

Source URLs first. Context is welcome, but claims do not publish from submissions alone.

Not accepted

Private tips, survivor identifiers, sealed or leaked material, graphic details, and private contact data.

Screenshots or social posts without a public source URL.

Misconduct labels for living people unless the exact cited public record supports that exact statement.

What changed

Case change ledger

Audit feed for source anchors, queue decisions, privacy-review jobs, and hashes. It explains the process without turning leads into claims.

Change ledger loaded.Ledger hash 95e8edeec6f7Case hash 027d83e7ae2e
Oct 19, 2026source added

OPM final rule, Administrative Leave for Workforce Realignment and Other Purposes, as printed at 91 FR 65924 (October 19, 2026; FR Doc. 2026-21320)

Status
source anchor in case file
Evidence state
case anchor
Lane
official record

The printed text, read today from the Register's own text endpoint; the citation and page range are the Register's. The effective date here replaces this desk's arithmetic with the document's own statement, and the two agree - that agreement is recorded, not treated as confirmation of any other computed date. This desk compared the October 16 inspection copy it saved against this printed text and found no substantive difference beyond the filled DATES line; the remaining differences are typesetting, and the comparison is this desk's own. The rule is still the agency's account of its own authority and of the policies it says it is codifying, the commenters' positions are theirs and OPM's responses are OPM's, and no court or board has ruled on any of it. Nothing here is a finding of improper payment, waste or misconduct by any agency or employee, and nothing in it resolves whether the leave it codifies is lawful.

Next: Keep source-linked timeline and role claims limited to the extracted facts.8131963b3de8
Safety posture

Locked to public records and bounded intake

Post throttleSource intake is DB-rate-limited to 6 submissions per minute per network key before a record is written.
Public URL onlyLocalhost, private networks, URL credentials, unsupported protocols, malformed URLs, and overlong fields are rejected.
No paid callsThe data export links render deterministic public-record payloads. They do not call LLMs or paid upstream APIs.
Identity minimizedSubmitter material is converted to a server-side HMAC hash, and the public queue does not return raw IPs or user agents.