Skip to content
Hugin
Public record case file

Federal AI Procurement Accountability file

Official records, court dockets, oversight reports, release reviews, and civil or state updates joined without converting association or incomplete records into misconduct claims.

188 source leads13 verified anchors9 timeline events6 public-record rolesFile fingerprint dc37b1983c65
Connection map
timeline backed9
source links13
role links13
open queues0

Fingerprint = the first 12 characters of this file's SHA-256 content hash, used by mirrors to verify the same JSON bundle.

Connection map

How the public record connects

Graph JSON

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.

Connection map

How the public record is joined

Graph JSON
timeline backed9
source links13
role links13
open queues0
Source groups
6 sourcesofficial record6 linked recordsOMB M-25-21 federal AI use memorandum / OMB M-25-22 AI acquisition memorandum / OMB M-24-18 AI acquisition memorandum
2 sourceslegislative record2 linked recordsFAR Part 39 information-technology acquisition / FAR Part 3 improper business practices
Timeline joins
Jan 26, 2023 / officialNIST AI RMF baseline enters the source lane1 linked recordStandards context does not establish whether a specific agency or vendor met the framework.
Jul 26, 2024 / officialNIST generative-AI profile enters acquisition review1 linked recordRisk-management profile context does not establish whether a specific agency or vendor met the profile.
Role joins
official record holderOffice of Management and Budget3 linked recordsOMB guidance frames agency obligations; contract-specific claims still need agency procurement records.
official record holderNational Institute of Standards and Technology1 linked recordStandards guidance is context, not evidence that a specific AI deployment was safe or unsafe.

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 leads188
automated probes276
verified anchors13
review backlog118
scout targets240
first-pass scout216
credential queue16
connectors30
keyless APIs96
free-key targets16
public search96
official pages24
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

Federal AI procurement desk for OMB guidance, NIST risk-management context, FAR acquisition rules, spending records, recipient integrity checks, and vendor identity joins.

Source lanespublic-spending-oversight, regulatory-anchors, market-integrity, public-record-discovery, ai-release-receipts
Sharing stateautomatic sharing disabled
Next actionPublish only policy, award, solicitation, or agency-record posture after source-scout rows are joined to exact public procurement records.
keyless apiCourtListener Search APIOMB AI use and AI acquisition memorandum deltasLegal search across opinions, dockets, RECAP data, judges, and arguments.
keyless apiGDELT DOC APIOMB AI use and AI acquisition memorandum deltasCoverage-index discovery for fresh public reporting rows.
keyless apiFederal Register APIOMB AI use and AI acquisition memorandum deltasOfficial rule, notice, and agency-document discovery.
public searchGovInfo public document searchOMB AI use and AI acquisition memorandum deltasFree public search across official publications from all three branches of the U.S. federal government.
OMB AI use and AI acquisition memorandum deltasUSAspending AI award and recipient joinsSAM, OFAC, and exclusion checks for AI procurement vendorsFederal Register, FAR, and acquisition-rule AI referencesNIST AI RMF, generative-AI profile, and implementation crosswalk updatesSEC EDGAR and issuer-reference rows for public AI contractorsagency AI inventory, solicitation, and award-document source joinscoverage-index leads about federal AI adoption and procurement claims

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.

Evidence standard

Publishing limits

Jul 9, 2026, 11:50 PM
Minimum source tierofficial-record, spending-record, recipient-integrity-record, legislative-record
Living peopleFor named officials, employees, or vendors, publish only source-backed public roles and exact record relationships; do not infer intent, influence, or blame.
Victim protectionDo not publish private bidder data, nonpublic proposal material, source-selection details, or personal contact information.
Social leadsSocial posts and coverage can start a procurement lead, but award-level copy requires official procurement, spending, agency, court, protest, or enforcement records.
Association firewall

No guilt by proximity

A vendor, model, agency, or policy record appearing in the same procurement lane is context only and does not prove an award, conflict, deployment, or failure.

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 claims9
source repair0
known anchors13
lead quarantine0
scout targets240
first-pass scout216
credential queue16
scout connectors30
rankhigh384 priority score
readyReady for first-pass public review9 publishable claim rows / 13 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 2a4d9ff66d6e
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 sources13
publishable anchors11
atlas sources5
keyless feeds2
release asks7
document jobs13
privacy triage2
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 948dba0992c1Case hash dc37b1983c65
Jul 9, 2026source added

FAR Part 3 improper business practices

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

Use as procurement-integrity context only; do not infer a conflict without a specific public record.

Next: Keep source-linked timeline and role claims limited to the extracted facts.998c0e9efbc4
Jul 9, 2026source added

FAR Part 39 information-technology acquisition

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

Use for acquisition-rule context; pair with the specific solicitation or contract clause before applying it to an award.

Next: Keep source-linked timeline and role claims limited to the extracted facts.b6381819b7ed
Jul 9, 2026source added

GAO generative AI use and management report

Status
source anchor in case file
Evidence state
case anchor
Lane
oversight report

Use for oversight context about agency use and inventory management, not proof that a named procurement is active or compliant.

Next: Keep source-linked timeline and role claims limited to the extracted facts.c7f3194824f7
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.