Skip to content
Hugin
A thick closed dark contract binder held by a steel clip, a small computer chip resting on its cover.
Public recordOpen file0FE5FC1F

Public record case file · Updated Oct 2, 2026

Federal AI Procurement

Accountability file

A public-record case file for federal AI adoption, acquisition, governance, risk-management, and procurement-integrity records. It keeps policy memoranda, acquisition rules, standards, spending records, vendor references, and coverage leads separate until a public record supports the exact claim.

Original editorial artwork generated for Hugin.

Updated
Oct 2, 2026
Source Anchors
25 verified · 188 leads
Timeline
21 events
Roles
9 public-record
Fingerprint
0FE5 FC1F 4146
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

21 events · 9 roles · 25 sources

Recent developments in the record

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

  1. GSA's America.gov says its answers come from an 'SI model' supplied by contracted providers under Zero Data Retention terms, and names none of them →records release review · 3 source records
    Read summary and limits

    Read October 2, the policy pages of America.gov, the GSA-run site that Executive Order 14432 directs GSA to operate, describe a super-intelligence service already answering the public. The privacy policy says the site's 'SI model' searches government websites in a sandboxed copy of the Internet, that its 'SI providers' work under Zero Data Retention agreements and are contractually barred from selling user information, building advertising profiles or training their models on user data, and that the site keeps model and tool outcomes and token counts for up to 90 days and caches SI-generated answers in Cloudflare KV for up to two hours. The terms of use say some answers are generated with SI and 'can be incomplete or wrong', tell users to check the linked source before acting on money, immigration status, benefits or a deadline, and say the site is not the agency of record. Neither page names a provider, model, contract or award, so this file cannot yet join the service to any obligation, OneGov offer or vendor.

    Evidence limits. GSA's own description of its service. It is not evidence of any particular vendor, contract, price or error rate, and this desk has not seen the contract terms it describes.

  2. Executive Order 14432 has GSA run America.gov as the single online entry to federal services and requires its super intelligence to be 'accurate, reliable, and transparent' →records release · 1 source record
    Read summary and limits

    Executive Order 14432, 'Streamlining Access to Government Services Through America.gov', dated at the White House September 29, filed for public inspection October 1 and printed October 2 at 91 FR 63121, directs the Administrator of General Services, in coordination with the National Design Studio and OMB, to establish and operate America.gov as the single point of entry for covered federal services online and to use Login.gov as its authentication service. Its policy section adds that super intelligence used in connection with America.gov is to be accurate, reliable and transparent, and that in-person, telephone, mail and agency-specific digital routes stay available. Covered services are public-facing services with more than 100,000 users in 12 months that can be accessed or applied for online, minus IRS tax filing, Department of War services and Intelligence Community elements, and OMB may add or exclude services by memorandum. OMB owes agencies an implementation memorandum within 90 days, which this desk counts to December 28; agencies must identify their covered services, integrate them, and give GSA and OMB usage and performance data. The order names no vendor, model, system or cost, uses 'super intelligence' once without defining it, and is subject to the availability of appropriations.

    Evidence limits. A directive to agencies. It establishes nothing about how accurate America.gov's answers are, who supplies its super intelligence or what it costs, and it creates no enforceable right.

  3. D.C. Circuit denies Anthropic's petitions for review of the § 4713 supply-chain exclusion, 2-1 →case disposition · 3 source records
    Read summary and limits

    In a published opinion by Judge Katsas, joined by Judge Rao, with Judge Henderson dissenting, the D.C. Circuit denied Anthropic's petitions for review of the Department of War's covered procurement actions under the Federal Acquisition Supply Chain Security Act. It held that the Department had 'ample support' for treating the continued integration of Claude as a statutorily covered supply-chain risk, that Anthropic received adequate process, and that the exclusion rested on Anthropic's refusal to accept a contract term, not on its policy advocacy. The majority said it had 'no quarrel' with the Northern District's conclusion that Anthropic acted with no bad motive, but held that no bad motive is required under the broader § 4713 definition, and a footnote says the Northern District's § 3252 determinations do not control its review. The clerk was ordered to withhold the mandate until seven days after disposition of any timely petition for rehearing.

    Evidence limits. Denying a petition for review upholds an agency's procurement authority. It does not find that Anthropic sabotaged, or intended to sabotage, any system. The mandate has not issued, rehearing remains possible, and this decision does not review or vacate the earlier district-court judgment, which concerns a different statute.

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

Included in this file

  • Official OMB memoranda and White House records governing federal AI use, acquisition, and public trust.
  • NIST AI risk-management and generative-AI profile records used as standards context.
  • Federal Acquisition Regulation records that shape information-technology procurement and conflict-of-interest review.
  • USAspending, SAM, SEC, and public coverage leads that can later be joined to named awards, vendors, and obligations.
  • Case workbench rows that distinguish policy posture from contract-specific claims.

Outside this file’s scope

  • Claiming that a vendor received, lost, or misused a federal AI contract without a named award, filing, or agency record.
  • Treating policy encouragement, pilots, or standards guidance as proof that a specific AI system is deployed in production.
  • Inferring conflicts of interest, procurement bias, or safety failures from public-market commentary alone.

What remains unresolved

These questions stay open in the case file.

  • Which USAspending award rows explicitly identify AI systems, services, pilots, or vendor obligations?
  • Which agency AI use inventories or implementation records map to OMB M-25-21 guidance?
Read all 11 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
  • official record
  • oversight report
  • spending record
  • recipient integrity record
  • legislative record
  • court docket
Living people
For named officials, employees, or vendors, publish only source-backed public roles and exact record relationships; do not infer intent, influence, or blame.
Victim protection
Do not publish private bidder data, nonpublic proposal material, source-selection details, or personal contact information.
Social leads
Social posts and coverage can start a procurement lead, but award-level copy requires official procurement, spending, agency, court, protest, or enforcement records.

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.

Filed
Hugin · public social evidence reports
License
Text and data are shared under the terms noted at hugin.studio/support · attribution appreciated.
Fingerprint
0FE5 FC1F 4146
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 backed21
source links34
role links25
open queues0
Source groups
15 sourcesofficial record15 linked recordsOMB M-25-21 federal AI use memorandum / OMB M-25-22 AI acquisition memorandum / OMB M-24-18 AI acquisition memorandum
2 sourcescourt docket2 linked recordsAnthropic PBC v. U.S. Department of War, N.D. Cal. No. 3:26-cv-01996-RFL: order on cross-motions for summary judgment, order of final relief, and judgment (Aug. 27, 2026) / Anthropic PBC v. U.S. Department of War, D.C. Cir. Nos. 26-1049 & 26-1162: opinion, judgment, and order withholding the mandate (Sept. 25, 2026)
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 Budget4 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 anchors25
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.

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 lanes0
source joins36
release joins0
Wired lanes4Computed from the source tiers and joined to live records, roles, and releases.
WiredAI safety procurement crosswalk
16 sources

Compare AI acquisition records with NIST RMF context and agency-specific implementation records before publishing risk-management language.

timeline17
roles6
release asks0
Connected roles
Office of Management and BudgetNational Institute of Standards and TechnologyFederal agency AI buyers
Release requests
No release request is attached to this lane yet.
PublishesCrosswalk notes, risk-management citations, and missing agency records.
BlockedSaying a deployed system is safe, unsafe, compliant, or noncompliant without a source-backed assessment.
WiredAI governance guidance drift
15 sources

Track OMB, White House, NIST, and acquisition-rule changes before saying current federal AI policy changed.

timeline15
roles4
release asks0
Connected roles
Office of Management and BudgetNational Institute of Standards and TechnologyFederal agency AI buyers
Release requests
No release request is attached to this lane yet.
PublishesPolicy posture, supersession notes, and open questions.
BlockedTreating prior guidance as current without checking later records.
WiredAI award identity joins
3 sources

Join USAspending award rows, SAM entity records, agency solicitations, and vendor identifiers before naming any contract-specific claim.

timeline1
roles1
release asks0
Connected roles
USAspending and SAM.gov identity joins
Release requests
No release request is attached to this lane yet.
PublishesAward IDs, obligation amounts, agency names, recipient IDs, and source gaps.
BlockedClaiming a vendor won, lost, or misused an AI contract from policy language alone.
WiredProcurement integrity quarantine
2 sources

Hold conflict, protest, exclusion, or enforcement leads until a specific filing, award protest, disclosure, or enforcement record is attached.

timeline1
roles1
release asks0
Connected roles
Federal Acquisition Regulation
Release requests
No release request is attached to this lane yet.
PublishesIntegrity-rule context, named public filings, and source-needed labels.
BlockedInferring conflicts of interest or favoritism from vendor proximity or market commentary.
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 claims19
source repair0
known anchors25
lead quarantine0
scout targets240
first-pass scout216
credential queue16
scout connectors30
rankhigh426 priority score
readyReady for first-pass public review19 publishable claim rows / 25 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 af3ef2603487
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 sources25
publishable anchors24
atlas sources5
keyless feeds2
release asks7
document jobs25
privacy triage5
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 4d1b742f3b9eCase hash 0fe5fc1f4146
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.