Official records, court dockets, oversight reports, release reviews, and civil or state updates joined without converting association or incomplete records into misconduct claims.
Fingerprint = the first 12 characters of this file's SHA-256 content hash, used by mirrors to verify the same JSON bundle.
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.
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.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.
Sanitized queue view: Hugin shows the public URL, lane, status, and why a source has not been promoted. Submitter identifiers are not shown.
Audit feed for source anchors, queue decisions, privacy-review jobs, and hashes. It explains the process without turning leads into claims.
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.31e52a6cece5This binds document mirroring and privacy-triage rules.
Next: Compare the short hash in the UI with this machine-readable ledger.2f7767735353This binds privacy-review and metadata extraction jobs.
Next: Compare the short hash in the UI with this machine-readable ledger.71219f49e249This binds the visible queue decisions to a machine-readable report.
Next: Compare the short hash in the UI with this machine-readable ledger.0831e7d1c44dThis changes when sanitized submission rows change.
Next: Compare the short hash in the UI with this machine-readable ledger.18bd8099cf41Report pages can support findings or recommendations only within the scope and language of the cited report.
Next: Keep source-linked timeline and role claims limited to the extracted facts.12bfedfbf1ddPandemic spending totals, enforcement rows, and findings need posture labels before public conclusions.
Next: Keep source-linked timeline and role claims limited to the extracted facts.cd44a1541790An exclusion row is a specific eligibility/status record and cannot be generalized into unrelated misconduct claims.
Next: Keep source-linked timeline and role claims limited to the extracted facts.db6f0e282801Outlay 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.4952b7421d38Award 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.712716b82cafConnections 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.
A recipient, agency, or program appearing in a spending record is a public-record relationship only and does not imply misuse.
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.
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.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.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.baselineClaim rows are derived from timeline events and source anchors. They are evidence-status labels, not accusations or final truth claims.
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.
Each source bundle below shows every public-record role it anchors. A shared bundle means the same record touches multiple roles; it is not a finding about conduct beyond that record.
Official GSA API documentation for SAM.gov exclusion records, used to check recipient eligibility/status when a server-side key is configured.
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 public report portal for Inspector General audit, inspection, evaluation, investigation, and oversight publications.
Official PRAC/Pandemic Oversight source for pandemic relief spending oversight, data tools, and report context.
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.
Normalize award ID, recipient name, UEI, agency, dates, and amount before any contractor or program review.
Index report number, agency, findings, questioned costs, recommendations, and management response.
Join MTS line codes and classification descriptions to program/agency review questions.
Configure a server-side SAM_GOV_API_KEY before importing exclusion records.
Deliberate gaps in the public record — open until the underlying records are released or reviewed, not questions we have skipped.