Accountability file
A public-record case file for tracking AI model release, access, safety, pricing, status, and operator-workflow records. It separates official OpenAI and Anthropic source records from Hugin field notes, social excitement, benchmark claims, and release-date speculation.
F658 F8DD 69A1This 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.
These are the standards every anchor on this file must clear.
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.
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.
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.
Public provider-status surfaces used to separate incidents, capacity, model access, and safety behavior from model-quality claims.
Hugin's July 25 desk entry joins Anthropic's Opus 5 launch record and OpenAI's reset-banking release note while holding an unsupported claim that Opus 5 itself issued a fresh reset.
Hugin's July 26 news desk separates OpenAI product records, sensitive health-product posture, and the DOJ Minnesota Medicaid guilty-plea record into different receipt lanes.
Hugin-authored news note that records the operator-stack framing and links back to primary provider receipts.
Hugin-authored news note documenting the July 5 Reddit hosted-scan recovery pass, duplicate-report cache reuse, and upstream-block posture.
Hugin-authored news note documenting the July 6 public case-index latest-activity rail and its matching content/case receipt posture.
Hugin-authored late July 7 news receipt separating Fable promotional access through July 12, Fable weekly-limit mechanics, Claude Code's 50% window through July 13, and unconfirmed reset claims.
Hugin-authored news note documenting the July 7 Fable usage-credit transition check, GPT-5.6 official-preview posture, Epstein library status check, and case-confidence polish.
Hugin-authored July 8 news receipt that keeps Fable promotional access, Claude Code's separate 50% weekly-limit window, reset uncertainty, and the new court-record source view in distinct lanes.
Hugin-authored July 8 news receipt validating the credible GPT-5.6 July 9 launch-watch lane and adding larger case source-desk counters without converting source leads into verified claims.
Official Anthropic record for Fable/Mythos restored access, usage-credit transition, and safeguards context.
Help-center receipt for GPT-5.6 Sol, Terra, and Luna preview access, model IDs, pricing, caching, and availability limits.
Release-note surface for ChatGPT-facing model availability, update, and retirement language.
Official OpenAI preview post for GPT-5.6 Sol and its release-watch framing.
Dated OpenAI general-availability record for the GPT-5.6 Sol, Terra, and Luna family across ChatGPT, Codex, and the OpenAI API, with surface-specific terms and gradual rollout language.
Current OpenAI plan and workspace-controls documentation for Codex, including plan-varying usage limits, client access, plugins, and surface-specific controls.
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 OpenAI launch framing for GPT-5.5 across API, ChatGPT, and Codex work surfaces.
Use this as the product-launch anchor; do not extend launch claims beyond current docs, release notes, or status records.official recordOpenAI Codex modelsOpenAI DevelopersOfficial Codex model-selection page used to verify GPT-5.5, lighter Codex lanes, and model availability language.
Treat this as the current Codex model guidance, and re-check before repeating default-model or availability claims.official recordOpenAI Codex goal workflowOpenAI DevelopersOfficial Codex use-case page for durable goals, long-running work, success conditions, and validation loops.
Use this to support workflow claims about Codex goal mode, not claims about model quality by itself.official recordOpenAI introduces CodexOpenAIOfficial product-level Codex introduction and agentic coding baseline.
Use for Codex product framing; pair with current docs for feature and model availability.official recordOpenAI previews GPT-5.6 SolOpenAIOfficial OpenAI preview post for GPT-5.6 Sol and its release-watch framing.
Preview language is not general-availability language; keep rollout claims tied to help, docs, release notes, and status.official recordOpenAI GPT-5.6 preview help articleOpenAI Help CenterHelp-center receipt for GPT-5.6 Sol, Terra, and Luna preview access, model IDs, pricing, caching, and availability limits.
Use for access and pricing terms; re-check before saying preview access has broadened.official recordOpenAI GPT-5.6 preview system cardOpenAI Deployment SafetyDeployment-safety record for GPT-5.6 preview safeguards, preparedness, and risk posture.
Use for safety and preparedness claims; do not turn safety-card language into product availability claims.official recordOpenAI GPT-5.6 public launch social receiptOpenAIOfficial OpenAI social receipt saying GPT-5.6 Sol, Terra, and Luna are scheduled to launch publicly on Thursday, July 9, with preview access expanding globally.
Use as the public-launch timing receipt; still re-check help, API, Codex, ChatGPT, release-note, and status records before saying a specific surface has access.official recordOpenAI API deprecations ledger — forward schedule read 2026-08-10OpenAIOpenAI's own API deprecations ledger, read 2026-08-10, carrying dated shutdowns out to January 2027: the gpt-5.2/5.3-chat-latest snapshots on Aug 10 2026, the Assistants API on Aug 26, the Videos API and the whole Sora 2 family on Sep 24 with no replacement named, legacy GPT snapshots on Sep 28 and Oct 23, Agent Builder on Nov 30, the older GPT Image models on Dec 1, and the end of new self-serve fine-tuning jobs for active customers on Jan 6 2027.
A provider publishing its own forward-dated schedule, authoritative for what OpenAI has announced and when. It is not a guarantee that a date will not move, and it names no reason for any retirement. Note the ledger's shape: it keeps carrying a retired id after the date, so it can confirm what was SCHEDULED but never that a shutdown happened — for that, read the live models list, where an executed retirement appears as an absence.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.
Deliberate gaps in the public record — open until the underlying records are released or reviewed, not questions we have skipped.
F658 F8DD 69A1Connections 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.
AI release desk for official lab receipts, safety records, public coverage, and draft promotion copy with no automatic publishing enabled.
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.
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.
Compare provider status, pricing, model overview, release notes, and help-center rows before assigning failed runs to model quality.
Re-check the Scheduled Tasks and GPT-5.6 help records before repeating active-task caps, supported models, plan limits, or reset-time language.
Re-check Codex model docs, GPT-5.5 launch framing, and Codex changelog entries before repeating current model-default claims.
Track current Codex goal-mode docs, app behavior, validation-loop examples, and completed Hugin release receipts before describing long-running workflow reliability.
Track hosted Reddit 403/429 recoveries, duplicate-report reuse, and companion/browser recovery paths before claiming a scan failure is a reader error.
Keep Hugin field notes and social reactions clearly labeled until they are joined to provider docs, status rows, or repeatable verification.
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.
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.
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.Sanitized queue view: Hugin shows the public URL, lane, status, and why a source has not been promoted. Submitter identifiers are not shown.
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.
Audit feed for source anchors, queue decisions, privacy-review jobs, and hashes. It explains the process without turning leads into claims.
Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.d55859a62b88Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.77e6579c0f98Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.ac1e8ecf06c7Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.5dfe39b8eaa3Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.727e053396a8Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.b3e268f00efbExtract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.922f279d8f12Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.66fd5be77507Mirrors can compare this hash to verify the same case file bundle.
Next: Compare the short hash in the UI with this machine-readable ledger.f658f8dd69a1This binds document mirroring and privacy-triage rules.
Next: Compare the short hash in the UI with this machine-readable ledger.33bb3042fb51