Skip to content
Hugin
Public record case file

AI Release Receipts 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.

217 source leads80 verified anchors26 timeline events4 public-record rolesFile fingerprint e0482ef89008
Connection map
timeline backed26
source links116
role links58
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 backed26
source links116
role links58
open queues0
Source groups
35 sourcesofficial record35 linked recordsOpenAI introduces GPT-5.5 / OpenAI Codex models / OpenAI Codex goal workflow
34 sourcespublic record repository34 linked recordsProvider status pages / Hugin July 4 release-watch note / Hugin July 4 operator journal
Timeline joins
Apr 23, 2026 / officialGPT-5.5 and Codex work-lane records open4 linked recordsCodex workflow records support operating-language claims, not universal benchmarks or guarantees.
Jun 30, 2026 / officialFable/Mythos restoration record pinned4 linked recordsRestored access and operator satisfaction are separate claims; keep both tied to their own sources.
Role joins
official record holderOpenAI18 linked recordsOpenAI records control OpenAI model availability and safety language; Hugin field notes cannot broaden those claims.
official record holderAnthropic11 linked recordsAnthropic records control Fable availability, usage, safety, and pricing language; operator sentiment is context only.

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 leads217
automated probes343
verified anchors80
review backlog145
scout targets279
first-pass scout261
credential queue18
connectors31
keyless APIs117
free-key targets18
public search72
official pages72
POST templates0
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

AI release desk for official lab receipts, safety records, public coverage, and draft promotion copy with no automatic publishing enabled.

Source lanesofficial-lab-posts, government-ai-records, public-coverage-index, openai-news, anthropic-news, provider-controls-and-reflection
Sharing stateautomatic sharing disabled
Next actionStage launch-watch drafts after official access records and credible coverage agree; hold actual posting until Mitch enables a channel.
keyless apiCourtListener Search APIOpenAI GPT-5.6 launch, help, release-note, and status deltasLegal search across opinions, dockets, RECAP data, judges, and arguments.
keyless apiGDELT DOC APIOpenAI GPT-5.6 launch, help, release-note, and status deltasCoverage-index discovery for fresh public reporting rows.
keyless apiFederal Register APIOpenAI GPT-5.6 launch, help, release-note, and status deltasOfficial rule, notice, and agency-document discovery.
public searchGovInfo public document searchOpenAI GPT-5.6 launch, help, release-note, and status deltasFree public search across official publications from all three branches of the U.S. federal government.
OpenAI GPT-5.6 launch, help, release-note, and status deltasAnthropic Fable promotional-access, usage-credit, and Claude Code limit updatesAxios, Reuters, Business Insider, and Engadget coverage joinsHugin AI desk feed rows that are ready for draft social copyOpenAI status, model release notes, and help-center deltasAnthropic status, release notes, pricing, and Help Center deltasAI platform access, workspace-control, privacy, and reflection-feature deltasFederal Register, White House, and Congress AI policy recordsSEC, DOJ, and public coverage joins for AI procurement and disclosure

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 18, 2026, 5:00 PM
Minimum source tierofficial-record, public-record-repository, coverage-index
Living peopleFor named researchers, operators, or company employees, publish only source-backed public roles and records; do not infer motive or blame from model behavior.
Victim protectionDo not publish private account identifiers, workspace IDs, billing details, or screenshots that expose nonpublic access state.
Social leadsSocial posts and screenshots can start a release-watch lead, but promotion requires official provider docs, status records, or repeatable verification.
Association firewall

No guilt by proximity

A model, provider, operator note, or status event appearing in a shared timeline is context only and does not prove broad availability, benchmark superiority, or product 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 claims6
source repair0
known anchors80
lead quarantine0
scout targets279
first-pass scout261
credential queue18
scout connectors31
rankhigh431 priority score
readyReady for first-pass public review6 publishable claim rows / 80 source anchors / 261 first-pass source rows
actions6 start-here rows9 total workbench action rows
blockers1 launch checks18 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 3c2648d4b5b6
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 sources80
publishable anchors80
atlas sources14
keyless feeds14
release asks7
document jobs80
privacy triage45
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 e06be3d22e01Case hash e0482ef89008
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.