Official GSA API documentation for SAM.gov exclusion records, used to check recipient eligibility/status when a server-side key is configured.
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.
- Updated
- Jul 18, 2026
- Source Anchors
- 14 verified · 176 leads
- Timeline
- 10 events
- Roles
- 7 public-record
- Fingerprint
EBC7 ADB2 9770
How the public record connects
This shows the case file's most significant public-record connections only — see the Role Web and Timeline tabs for the full set. A line means a record connects two points; it is not a finding about conduct.
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.
People, institutions, and the records between them
Every public-record role in this file, grouped by kind. Open a role to read its dossier — its public-record status, what it is, and the exact records that name it. A shared record naming two roles is not a finding about conduct beyond that record.
Every public-record role
Pick a role to see its public-record status, what it is, and the exact records that name it. A shared record is not a finding about conduct.
No single record names more than one role in this file yet.
Official Monthly Treasury Statement table API for outlay rows, fiscal classifications, and period amounts.
Official API documentation for searching federal award records by recipient, agency, amount, award type, and dates.
Official FAC API for submitted Single Audit data, available with a free Data.gov key.
GAO report on congressional action needed to improve interoperability of federal award and payment eligibility data.
Official GAO feed for reports and testimony summaries that can add oversight findings, recommendations, and program-review context.
Timeline
- public document repository / official#Hugin opens public-spending source packHugin adds USAspending, Treasury Fiscal Data, Oversight.gov, GAO, Pandemic Oversight, FAC, SAM.gov exclusions, and OFAC sanctions-list context to the public-spending review lane.A source pack is infrastructure for review; it is not a claim that any spending was misused.
- award record / official#USAspending award import remains liveThe civic import plan can query award records through the official USAspending API without a credential.An award row is a public spending record, not evidence of misuse by itself.
- spending outlay / official#Treasury MTS outlay context addedThe civic scanner adds bounded Monthly Treasury Statement outlay signals to help compare award rows with official fiscal context.Fiscal outlay context does not establish program misuse without audit or legal findings.
- audit report / official#GAO flags award and eligibility data interoperability as a prevention issueGAO's June 2026 federal-data report adds a system-level source-quality anchor for Hugin's public-spending case: award, payment, and eligibility rows need stronger joins before misuse narratives can be responsibly published.A federal-data interoperability problem is a control and source-quality issue, not a finding that a recipient misused funds.
- recipient integrity check / medium#SAM.gov exclusion checks marked key-gatedThe source plan exposes SAM.gov exclusions as a credential-gated recipient-integrity check rather than a fabricated data join.Missing exclusion data must stay visible as a gap and cannot be filled from inference.
- records release review / official#DOJ reports a mixed-category Trade Fraud Task Force milestoneDOJ reports that its Trade Fraud Task Force surpassed $1 billion across civil and criminal recoveries, penalties, forfeitures, and publicly charged losses, and announces a new enforcement section and resource guide.The $1 billion figure is a combined DOJ category, not a recovery-only total, audit finding, or allegation against any recipient not named in a cited matter.
- civil settlement / official#DOJ announces a customs-duty False Claims Act settlementDOJ announces that Redi-Bag USA and its CEO agreed to pay $7.3 million to resolve allegations that they misrepresented the country of origin of polyethylene retail carrier bags on customs entry forms, evading antidumping duties on Chinese-made goods transshipped through Hong Kong.This is a settlement of a qui tam lawsuit; the claims resolved are allegations only with no determination of liability, and the record cannot be restated as a fraud finding or criminal outcome.
- sentence / official#Former Census Bureau program manager sentenced for procurement briberyA federal court sentences a former Census Bureau program manager to two years in prison, one year of supervised release, and forfeiture after she admitted conspiring to receive $790,000 in kickbacks from a relative-owned subcontractor on a steered employee-assistance contract.The sentence rests on admitted conduct within the counts of conviction; the co-conspirator is awaiting sentencing, and this record makes no claim about her eventual sentence.
Public sources ready to ingest
Import sources create source-run packets, document inventories, and review tokens. They do not publish accusations or graph relationships until the case-file evidence rules are satisfied.
Source anchors
Official API documentation for searching federal award records by recipient, agency, amount, award type, and dates.
Award records establish public spending context; they do not establish waste, fraud, abuse, or misuse without additional official findings.spending recordTreasury Fiscal Data Monthly Treasury Statement APIU.S. Department of the Treasury, Bureau of the Fiscal ServiceOfficial Monthly Treasury Statement table API for outlay rows, fiscal classifications, and period amounts.
Outlay rows are fiscal context and need award, program, and audit joins before supporting a misuse narrative.audit reportOversight.gov Inspector General reportsCouncil of the Inspectors General on Integrity and EfficiencyOfficial public report portal for Inspector General audit, inspection, evaluation, investigation, and oversight publications.
Report pages can support findings or recommendations only within the scope and language of the cited report. The address was repaired on 2026-07-31 after an automated reachability sweep found the previously cited path returning 404; the portal itself did not change.audit reportGAO Reports FeedU.S. Government Accountability OfficeOfficial GAO feed for reports and testimony summaries that can add oversight findings, recommendations, and program-review context.
GAO rows support public oversight context only inside the cited report scope.audit reportGAO federal award and payment eligibility data interoperability reportU.S. Government Accountability OfficeGAO report on congressional action needed to improve interoperability of federal award and payment eligibility data.
Use the report for system-level data-quality and prevention controls; do not turn data-interoperability gaps into recipient misconduct claims.oversight reportPandemic Oversight data and reportsPandemic Response Accountability CommitteeOfficial PRAC/Pandemic Oversight source for pandemic relief spending oversight, data tools, and report context.
Pandemic spending totals, enforcement rows, and findings need posture labels before public conclusions. The address was repaired on 2026-07-31 after an automated reachability sweep found the previously cited path returning 404; the publisher's data tools moved, the underlying oversight material did not change.audit reportFederal Audit Clearinghouse APIFederal Audit ClearinghouseOfficial FAC API for submitted Single Audit data, available with a free Data.gov key.
Single Audit rows are scoped audit records and do not establish general fraud, waste, abuse, or legal liability outside the report.recipient integrity recordSAM.gov Exclusions APIU.S. General Services AdministrationOfficial GSA API documentation for SAM.gov exclusion records, used to check recipient eligibility/status when a server-side key is configured.
An exclusion row is a specific eligibility/status record and cannot be generalized into unrelated misconduct claims.recipient integrity recordOFAC Sanctions List ServiceU.S. Department of the Treasury Office of Foreign Assets ControlOfficial OFAC service for current sanctions-list downloads and search access.
A sanctions-list name match is not identity proof; joins need strong identifiers before any recipient, issuer, donor, or person relationship is shown.baselineWhat the record currently supports
Claim rows are derived from timeline events and source anchors. They are evidence-status labels, not accusations or final truth claims.
What should be released next
Release requests are lawful public-record asks. They identify source gaps, review gates, and privacy constraints; they are not evidence that a specific person committed wrongdoing.
What stays unresolved
Deliberate gaps in the public record — open until the underlying records are released or reviewed, not questions we have skipped.
- Filed
- Hugin · public social evidence reports
- License
- Text and data are shared under the terms noted at hugin.studio/support · attribution appreciated.
- Fingerprint
EBC7 ADB2 9770
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.
Every machine-readable slice of this file
How the public record is joined
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.
Scout queue before promotion
Public-money source desk for award, payment, audit, exclusion, and oversight joins that need identity confidence before promotion.
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.
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.
Index report number, agency, findings, questioned costs, recommendations, and management response.
Normalize award ID, recipient name, UEI, agency, dates, and amount before any contractor or program review.
Join OFAC rows only through strong identifiers, aliases, addresses, list IDs, and update dates before displaying recipient, issuer, donor, or person relationships.
Join MTS line codes and classification descriptions to program/agency review questions.
Configure FAC_API_KEY and join auditee UEI/EIN, audit year, ALN/program, finding reference, and questioned-cost rows to award recipients.
Configure a server-side SAM_GOV_API_KEY before importing exclusion records.
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.
What this case can prove right now
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.
Queue a public record
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.
Queue a public source for review.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.
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.
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.
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.
Case change ledger
Audit feed for source anchors, queue decisions, privacy-review jobs, and hashes. It explains the process without turning leads into claims.
Case file hash snapshot
- Status
- hash changed when case bundle changes
- Evidence state
- metadata only
Mirrors can compare this hash to verify the same case file bundle.
Next: Compare the short hash in the UI with this machine-readable ledger.ebc7adb29770Document manifest hash snapshot
- Status
- hash changed when document handling changes
- Evidence state
- metadata only
This binds document mirroring and privacy-triage rules.
Next: Compare the short hash in the UI with this machine-readable ledger.67ac6cf822adDocument review queue hash snapshot
- Status
- hash changed when document jobs change
- Evidence state
- metadata only
This binds privacy-review and metadata extraction jobs.
Next: Compare the short hash in the UI with this machine-readable ledger.62c51c336778Source validation hash snapshot
- Status
- hash changed when queue or validation rules change
- Evidence state
- metadata only
This binds the visible queue decisions to a machine-readable report.
Next: Compare the short hash in the UI with this machine-readable ledger.dc48807edea1Submission queue hash snapshot
- Status
- hash changed when public queue rows change
- Evidence state
- metadata only
This changes when sanitized submission rows change.
Next: Compare the short hash in the UI with this machine-readable ledger.925dff06c468USAO Maryland: Everlight Electronics $5.15M customs-duty FCA settlement
- Status
- source anchor in case file
- Evidence state
- case anchor
- Lane
- civil enforcement record
A civil settlement resolves allegations with no admission or adjudication of liability stated; the alleged-conduct framing must survive any summary.
Next: Keep source-linked timeline and role claims limited to the extracted facts.72b919ef7a8dGAO Reports Feed
- Status
- source anchor in case file
- Evidence state
- case anchor
- Lane
- audit report
GAO rows support public oversight context only inside the cited report scope.
Next: Keep source-linked timeline and role claims limited to the extracted facts.828a4ea9eb7dOversight.gov Inspector General reports
- Status
- source anchor in case file
- Evidence state
- case anchor
- Lane
- audit report
Report pages can support findings or recommendations only within the scope and language of the cited report. The address was repaired on 2026-07-31 after an automated reachability sweep found the previously cited path returning 404; the portal itself did not change.
Next: Keep source-linked timeline and role claims limited to the extracted facts.e5520bc6003eTreasury Fiscal Data Monthly Treasury Statement API
- Status
- source anchor in case file
- Evidence state
- case anchor
- Lane
- spending record
Outlay rows are fiscal context and need award, program, and audit joins before supporting a misuse narrative.
Next: Keep source-linked timeline and role claims limited to the extracted facts.4952b7421d38USAspending award search API
- Status
- source anchor in case file
- Evidence state
- case anchor
- Lane
- spending record
Award records establish public spending context; they do not establish waste, fraud, abuse, or misuse without additional official findings.
Next: Keep source-linked timeline and role claims limited to the extracted facts.712716b82caf