328DCF81Public record case file · Latest recorded event Oct 23, 2026
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.
Original editorial artwork generated for Hugin.
328D CF81 21B7Keep 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.
The latest dated events in this file. Open an event for its cited sources and evidence limits.
Read October 22, the lifecycle table lists gemini-omni-flash-preview, veo-3.1-lite-generate-preview, veo-3.1-generate-preview and veo-3.1-fast-generate-preview at October 22, 2026, all pointing to gemini-omni-1.1-flash. It separately lists deep-research-pro-preview-12-2025 at October 23 with deep-research-preview-04-2026 as recommended replacement. Google describes these as earliest possible shutdown dates, with advance notice promised for the exact date. This reading records the schedule and does not settle whether any endpoint has shut down.
Evidence limits. A provider lifecycle schedule is not an endpoint test or an observed shutdown. No late/absence finding follows from a row reaching its earliest possible date, and a listed replacement is not proof of equivalent capabilities.
Read October 22, AWS's scheduled-EOL table gives November 13, 2026 for specified Claude 3/3.5/3.7 model IDs in particular Regions, March 9 and March 21, 2027 for Writer Palmyra X4 and X5, March 22 for TwelveLabs Marengo Embed 3.0 and Pegasus v1.2, and March 30 for listed model rows across other providers. The source limits each announcement to the Regions in its row; absent Regions are not promised indefinite availability. It says migration requires application changes and is not automatic. The same page's six-month Legacy minimum and three-month pre-extended-access minimum conflict with some October-to-November Claude rows. The table contains no recommended-successor column, and no attempt is made to choose between the conflicting notice statements.
Evidence limits. AWS's own published schedule is not proof that a model currently answers, that a future request will fail in every Region or that a private arrangement is unavailable. Region scope and source inconsistencies remain explicit; no successor or equivalent model is invented.
Read October 19, the Gemini API pricing page lists every paid rate on gemini-4-argon, Google's flagship reasoning model, at one price 'through November 30, 2026' and at exactly twice that price 'starting December 1, 2026', across the Standard, Batch, Flex, Priority and invite-only Contributor tiers: Standard input $2.00 to $4.00 and output $10.00 to $20.00 per million tokens. Argon is not available on the free tier. The step comes a month before the Gemini 3 Flash family's January 1, 2027 step, read here on September 28.
Evidence limits. A published price schedule, not an observed bill; Google can change the page before the date.
These questions stay open in the case file.
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.
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 source records behind it. A shared record linking two roles is not a finding about conduct beyond that record.
10 roles linked to 101 of 182 source records. 10 records connect more than one role. Open a role to follow its records into the timeline.
Hover or tap a role to light up the records that name it, then choose a partner to see exactly which records connect the two. Tap again, or use Open dossier, to read it. Watch it form replays the file by publication date.
A thread is a source record, not a relationship. Two roles meet only where one paper names both.
All publication dates
All roles
9 records have no publication date.
101 of 101 records · Newest publication first. Search filters this list.
10 of 10 roles · Counts describe records in this file.
Publishes the Bedrock model lifecycle tables used to verify end-of-life and public-extended-access dates for Amazon's own models and for partner models hosted on Bedrock.
2 source records · 2 linked eventsRead role →Publishes Fable/Mythos restoration, model overview, pricing, and status records used to verify Fable access and terms.
19 source records · 16 linked eventsRead role →Publishes the Copilot changelog and supported-models documentation used to verify model removals and default-enablement policy dates.
4 source records · 3 linked eventsRead role →Publishes the Gemini API changelog, pricing page and deprecations table and the Agent Platform model-versions, open-model deprecations and release-note pages used to verify model retirement dates, replacements and listed prices.
11 source records · 9 linked eventsRead role →Tracks AI release clusters, official rows, and open receipt needs across the news desk.
9 source records · 9 linked eventsRead role →Publishes the Foundry model retirement schedule used to verify Azure OpenAI retirement dates and those of Microsoft's own MAI models and partner models sold through Foundry.
2 source records · 1 linked eventRead role →Publishes the changelog and models pages used to verify Labs and third-party model retirements.
2 source records · 0 linked eventsRead role →Publishes GPT-5.5, Codex, GPT-5.6 preview and general-availability, release-note, plan-guide, safety, and status records used in the model-release watch.
29 source records · 26 linked eventsRead role →Publishes the migration guides, API release notes and security FAQ used to verify API model-name retirements and new request fields.
3 source records · 2 linked eventsRead role →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.
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.
Follow the record as it develops. Start with the latest events, or read from the beginning.
77 recorded events · Apr 23, 2026 — Oct 23, 2026
Showing 1–12 of 77 events · Latest first
Read October 22, the lifecycle table lists gemini-omni-flash-preview, veo-3.1-lite-generate-preview, veo-3.1-generate-preview and veo-3.1-fast-generate-preview at October 22, 2026, all pointing to gemini-omni-1.1-flash. It separately lists deep-research-pro-preview-12-2025 at October 23 with deep-research-preview-04-2026 as recommended replacement. Google describes these as earliest possible shutdown dates, with advance notice promised for the exact date. This reading records the schedule and does not settle whether any endpoint has shut down.
These links follow shared source records; they do not imply conduct or a direct relationship.
Read October 22, AWS's scheduled-EOL table gives November 13, 2026 for specified Claude 3/3.5/3.7 model IDs in particular Regions, March 9 and March 21, 2027 for Writer Palmyra X4 and X5, March 22 for TwelveLabs Marengo Embed 3.0 and Pegasus v1.2, and March 30 for listed model rows across other providers. The source limits each announcement to the Regions in its row; absent Regions are not promised indefinite availability. It says migration requires application changes and is not automatic. The same page's six-month Legacy minimum and three-month pre-extended-access minimum conflict with some October-to-November Claude rows. The table contains no recommended-successor column, and no attempt is made to choose between the conflicting notice statements.
These links follow shared source records; they do not imply conduct or a direct relationship.
Read October 19, the Gemini API pricing page lists every paid rate on gemini-4-argon, Google's flagship reasoning model, at one price 'through November 30, 2026' and at exactly twice that price 'starting December 1, 2026', across the Standard, Batch, Flex, Priority and invite-only Contributor tiers: Standard input $2.00 to $4.00 and output $10.00 to $20.00 per million tokens. Argon is not available on the free tier. The step comes a month before the Gemini 3 Flash family's January 1, 2027 step, read here on September 28.
These links follow shared source records; they do not imply conduct or a direct relationship.
Read the evening of October 18 (Arizona), OpenAI's API deprecations ledger carries eleven announcement sections under 'Upcoming deprecations' by this desk's count, and the newest, headed '2026-10-14: GPT-4 series model deprecations', states that developers using certain GPT-4 series models were notified of their deprecation and removal from the API on January 14, 2027. Its four rows cover five dated snapshots - gpt-4o-2024-08-06, gpt-4o-2024-11-20, gpt-4o-mini-2024-07-18, gpt-4.1-2025-04-14 and gpt-4.1-mini-2025-04-14 - and name the same recommended replacement, gpt-6-luna, for every one of them, across two families and four model sizes; the ledger names a replacement without saying it is equivalent to what it replaces. Fine-tuned versions follow their base models' schedule. Unlike the two sections dated 2026-10-01 immediately below it, which promise 'six months' notice' and 'at least three months' notice' respectively, this one states no notice period at all, so this desk computes none. The section is absent from this desk's reading of the same URL on October 2, whose own section list recorded those two as the newest, and two sections have since changed heading: '2026-09-11: GPT-5.4-Cyber' now sits under 'Past deprecations' and '2026-04-22: Legacy GPT model snapshots' under 'Upcoming deprecations'. The removal date has not arrived, so the section announces an event rather than records one.
Read October 10, Amazon's Bedrock legacy table lists Claude Sonnet 4.5 (anthropic.claude-sonnet-4-5-20250929-v1:0) with a Legacy date of October 8, public extended access from January 8 and end of life on April 8, 2027, across 31 Regions by this desk's count. Under the page's rules, new customers cannot use a Legacy model and existing customers may lose access after 15 days of inactivity; in extended access, active users continue at higher pricing the provider sets; on or soon after end of life requests fail unless privately arranged, and migration is not automatic. The page says only its dates apply on Bedrock. Anthropic's own page gives a tentative November 30 retirement for its platforms, so the two schedules differ and are not combined here. The page prints no date for when the row was added, and no Sonnet 4.5 extended-access price was established.
Read on the evening of October 7, in the revision Google stamps 'Last updated 2026-10-07 UTC', the Gemini API's deprecations table lists gemini-2.5-flash-image with a shutdown date of March 15, 2027 and names gemini-3.1-flash-lite-image as its recommended replacement. This desk read the same URL on September 27 and recorded that row as 2026-10-02, with gemini-3.1-flash-image-preview as the replacement — a preview the same table lists with its own shutdown date of 2026-06-25. Both the later date and the new replacement are what Google Cloud's Agent Platform has carried for this model id since an Agent Platform release note of September 14, which recorded the retirement as extended to it from 2026-10-02; that note governs the Cloud surface, and this desk found no entry for the change on the Gemini API's own release notes page, which is where that page says deprecation announcements are made. So what this row records is two dated fetches of one page, ten days apart, both this desk's own, and no announcement found on the surface where the change appeared. The two Google surfaces that disagreed about this model now agree. This desk's deadline board was still sending readers to the earlier date after it had passed, and was corrected the same evening.
These links follow shared source records; they do not imply conduct or a direct relationship.
Both of Google's model-lifecycle pages, read the same evening and each stamped 'Last updated 2026-10-07 UTC', carry future-dated commitments no row on this desk's deadline board covered. On the Gemini API's deprecations page, five preview models share a single shutdown date of November 17, 2026: the speech previews gemini-2.5-flash-preview-tts, gemini-2.5-pro-preview-tts and gemini-3.1-flash-tts-preview, pointed at gemini-3.8-flash-tts or gemini-3.8-flash-lite-tts, and the live previews gemini-3.1-flash-live-preview and gemini-2.5-flash-native-audio-preview-12-2025, pointed at gemini-3.8-live. This desk's September 27 reading of that page recorded gemini-3.1-flash-tts-preview with 'No shutdown date announced'. On Google Cloud's Agent Platform, the short-term availability table now gives gemini-3.6-flash a retirement date of 2026-11-19 and gemini-3.7-flash one of 2027-01-28, both replaced by gemini-3.8-flash. That table's own rule is that such a model stays active until a replacement ships and a retirement date is posted, and that a posted date leaves at least 45 days to migrate, so these two are dates added rather than dates moved — which is the ordinary working of a policy Google wrote down, recorded here because a reader with calls in either surface now has a deadline they did not have. Three rows went onto the deadline board for them.
These links follow shared source records; they do not imply conduct or a direct relationship.
Read the evening of October 2 (Arizona), OpenAI's API deprecations ledger carries ten announcement sections under 'Upcoming deprecations', and the two newest are both dated 2026-10-01. One covers gpt-5.3-codex, gpt-5.4-nano and gpt-5.1, whose paragraph reads that they 'will be removed from the API on April 1, 2027, with six months’ notice', with gpt-6-sol named as the replacement for the first and third and gpt-6-luna for the second. The other covers tts-1, tts-1-hd, gpt-4o-mini-tts-2025-03-20 and gpt-4o-mini-tts-2025-12-15, for removal on 2027-01-06, all four pointed at gpt-realtime-2.1-mini, and promises 'at least three months’ notice' — a floor where the other section states a figure. Every one of the seven rows names a replacement, and neither removal date has arrived, so both sections announce events rather than record them. This desk's reading of the same URL the previous day recorded '2026-09-11: GPT-5.4-Cyber' as the newest section under that heading; the ledger orders its sections by how recent the announcement is, and these two now sit above it. The response carried a Last-Modified of 2026-10-02T23:44:03Z, which establishes that the page was served modified that day — on a documentation site that can reflect a site build, so it is not read here as the moment either section was written.
Read three days after the date, OpenAI's deprecations ledger still lists gpt-3.5-turbo-instruct, babbage-002, davinci-002 and gpt-3.5-turbo-1106 with shutdown date 2026-09-28, unchanged, and now names gpt-5.6-terra as the replacement for all four. Their section has moved from 'Upcoming deprecations' to 'Past deprecations', but its paragraph still reads 'Access to these models will be shut down on the dates below', while the section immediately beneath it, announced the same day, was rewritten to say access 'was shut down'. The two headings now sort by how recent the announcement is rather than by whether the shutdown has happened: the 2026-04-22 group sits under 'Past deprecations' with seventeen rows whose shutdown date, October 23, has not arrived, and the Sora 2 and Videos API rows have moved to Past still carrying an em dash where a replacement would go. The ledger cannot show that any endpoint stopped answering, and this desk called none.
Anthropic's deprecations page, read October 10, lists claude-sonnet-4-5-20250929 as Deprecated from September 30 with a tentative retirement date of November 30, 2026, and its history entry for that day says Anthropic notified developers using Claude Sonnet 4.5 of its upcoming retirement on the Claude API, naming claude-sonnet-5-5 as the recommended replacement. This desk's September 27 reading of the same page had the model Active with a retirement floor of 'Not sooner than September 29'. The page's dates cover the Claude API, Claude Platform on AWS and Microsoft Foundry; it says Amazon Bedrock and Google Cloud set their own schedules.
Read September 28, the Gemini API pricing page lists paid Standard rates for gemini-3.8-flash, gemini-3.7-flash and gemini-3.6-flash at $0.75 input and $3.75 output per million tokens 'through December 31, 2026', and $1.50 and $7.50 'starting January 1, 2027'. Free-tier cells read 'Free of charge'. The page footer is dated September 24. The step is not new: archived captures show it on the 3.6 and 3.7 Flash rows by mid-August and on 3.8 Flash from the first capture that lists that model, and this desk's record finds 3.6 Flash listed at $1.50 and $7.50 with no end date before mid-August, so January returns it to its launch price. Google's changelog names neither price.
These links follow shared source records; they do not imply conduct or a direct relationship.
Amazon's Bedrock legacy table, read September 28, lists Nova Canvas and both Nova Reel versions for end of life on September 30, 2026 with no public extended access date; its rules say requests fail on or soon after that date unless privately arranged. It lists Claude Opus 4.1 entering public extended access, at higher provider-set pricing, on October 8, 2026 with end of life January 8, 2027, and Claude Sonnet 4 ending October 14, 2026, and says its dates are specific to Bedrock. Anthropic's deprecations page, read the same day, lists both Claude models as retired on Anthropic-operated platforms, Sonnet 4 on June 15 and Opus 4.1 on August 5, and says partner-operated platforms such as Bedrock set their own schedules.
These links follow shared source records; they do not imply conduct or a direct relationship.
Read the records behind this file. Search titles, publishers, summaries, and extracted facts. Each source keeps its reading limits and links to the events and roles it supports.
Showing 1–10 of 182 sources · 182 in this file
OpenAI
OpenAI's API deprecations ledger, read the evening of October 18, 2026 (Arizona). 'Upcoming deprecations' now holds eleven announcement sections and the newest is dated 2026-10-14: it deprecates five dated GPT-4 series snapshots — gpt-4o-2024-08-06, gpt-4o-2024-11-20, gpt-4o-mini-2024-07-18, gpt-4.1-2025-04-14 and gpt-4.1-mini-2025-04-14 — for removal from the API on January 14, 2027, and names the same recommended replacement, gpt-6-luna, for every row. The section adds that fine-tuned versions follow the same schedule as their base models. It is absent from this desk's October 2 reading of the same URL, whose own section list recorded the two sections dated 2026-10-01 as the newest. Two sections have also changed heading since that reading: '2026-09-11: GPT-5.4-Cyber' now sits under 'Past deprecations' rather than 'Upcoming deprecations', and '2026-04-22: Legacy GPT model snapshots' now sits under 'Upcoming deprecations'. The January 14, 2027 date has not arrived, so this section announces an event rather than records one.
Google (Gemini API docs)
Google's Gemini API pricing page, footer 'Last updated 2026-10-19 UTC', read October 19, 2026. Every paid rate on gemini-4-argon, described on the page as 'Our flagship reasoning model', is listed at one price 'through November 30, 2026' and at exactly twice that price 'starting December 1, 2026', across all five paid tiers (Standard, Batch, Flex, Priority and the invite-only Contributor tier). The page notes 'Gemini 4 Argon is not available on the Free tier.'
A shared source does not establish conduct or a direct personal relationship.
Anthropic
Anthropic's model deprecations page, fetched October 10, 2026 (HTTP 200). Its status table lists claude-sonnet-4-5-20250929 as Deprecated, with a deprecation date of September 30, 2026 and a tentative retirement date of November 30, 2026, and its deprecation history carries a 2026-09-30 entry for Claude Sonnet 4.5 naming claude-sonnet-5-5 as the recommended replacement. The page says its dates apply to Anthropic-operated platforms and that Amazon Bedrock and Google Cloud set their own retirement schedules.
Amazon Web Services
Amazon's Bedrock legacy-models page, read October 10, 2026. Its table of models with a scheduled EOL date lists Anthropic's Claude Sonnet 4.5 (anthropic.claude-sonnet-4-5-20250929-v1:0) with a Legacy date of October 8, 2026, an EOL date of April 8, 2027 and a public extended access start date of January 8, 2027, across 31 Regions by this desk's count. The page's rules say new customers cannot use Legacy models and existing customers may lose access after 15 days of inactivity, that public extended access brings higher pricing set by the model provider, and that on or soon after the EOL date requests fail unless privately arranged, with no automatic migration.
Google Cloud's model lifecycle table for Gemini Enterprise Agent Platform, stamped 'Last updated 2026-10-07 UTC' and fetched by curl on the evening of October 7 (HTTP 200). Its short-term availability table now carries retirement dates for two models that had none when this desk last read the page: gemini-3.6-flash on November 19, 2026 and gemini-3.7-flash on January 28, 2027, both replaced by gemini-3.8-flash.
The Gemini API's deprecations page, stamped 'Last updated 2026-10-07 UTC' and fetched by curl on the evening of October 7 (HTTP 200). Five preview models — three audio or speech previews and two live previews — carry a shutdown date of November 17, 2026, and gemini-2.5-flash-image now carries March 15, 2027 with gemini-3.1-flash-lite-image as its replacement.
OpenAI
OpenAI's API deprecations ledger, read the evening of October 2, 2026 (Arizona). 'Upcoming deprecations' holds ten announcement sections, and the two newest are both dated 2026-10-01: one deprecating gpt-5.3-codex, gpt-5.4-nano and gpt-5.1 for removal from the API on April 1, 2027, 'with six months’ notice'; one deprecating tts-1, tts-1-hd, gpt-4o-mini-tts-2025-03-20 and gpt-4o-mini-tts-2025-12-15 for removal on January 6, 2027, 'with at least three months’ notice'. Every one of the seven rows names a replacement. Neither date has arrived, so both sections announce events rather than record them. This desk's October 1 reading of the same page recorded '2026-09-11: GPT-5.4-Cyber' as the newest section under that heading; the ledger orders its sections by announcement recency, and these two now sit above it.
OpenAI
OpenAI's API deprecations ledger, read October 1, 2026, three days after the 2026-09-28 shutdown date its 2025-09-26 announcement set for four legacy completions models. All four rows survived the date unchanged and now name a replacement: gpt-3.5-turbo-instruct, babbage-002, davinci-002 and gpt-3.5-turbo-1106, each shutdown date 2026-09-28, each replaced by gpt-5.6-terra. The section has moved from 'Upcoming deprecations' to 'Past deprecations', but its paragraph is still in the future tense, while the section immediately below it, announced the same day, was rewritten into the past tense. The two headings now sort by announcement recency rather than by whether a shutdown has happened: everything announced 2026-06-02 or later sits under Upcoming, everything announced 2026-05-08 or earlier under Past, which puts the 2026-04-22 group's seventeen October 23, 2026 rows — a date that has not arrived — under 'Past deprecations'.
Google's deprecations page, read on September 30 in the revision its footer stamps 'Last updated 2026-10-01 UTC'. Its Veo models table lists veo-3.1-lite-generate-preview, veo-3.1-generate-preview and veo-3.1-fast-generate-preview with a shutdown date of October 22, 2026 and gemini-omni-1.1-flash as the recommended replacement; the Internet Archive's September 26 copy listed all three with 'No shutdown date announced'. The Gemini Omni Flash section no longer lists gemini-omni-flash-preview, which the September 27 read found listed at September 30, 2026.
A shared source does not establish conduct or a direct personal relationship.
Mistral AI
Mistral's changelog entry dated September 29, 2026 deprecates three models: 'OCR 4.0 (mistral-ocr-4-0) is deprecated and retires on September 30, 2026. Use OCR 4.1 (mistral-ocr-4-1 or mistral-ocr-latest) instead, at the same price.'; 'Leanstral 1.5 (labs-leanstral-1-5), an experimental Labs model, is deprecated and retires on September 30, 2026.'; and 'Z.ai GLM 5.2 (zai-glm-5-2) is deprecated and retires on October 31, 2026. Use Z.ai GLM 5.3 (zai-glm-5-3) instead, at the same price.' Its September 28 entry says Z.ai GLM 5.3 'is now Generally Available.'
A shared source does not establish conduct or a direct personal relationship.
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.
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.
328D CF81 21B7Connections 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.073fe1cacea8Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.474973b5731aExtract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.848d9bf509ecExtract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.e17e48cea51fExtract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.e1903be06d26Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.66a98aaadd56Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.138a45dc1b62Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.4d22f97e64d9Mirrors can compare this hash to verify the same case file bundle.
Next: Compare the short hash in the UI with this machine-readable ledger.328dcf8121b7This binds document mirroring and privacy-triage rules.
Next: Compare the short hash in the UI with this machine-readable ledger.79bc51a7bb70