ModelTreeAI Model Lineage
Data refresh

What each refresh found, and what it did not publish.

ModelTree's dataset is refreshed by agents against primary sources, reviewed by an independent three-rubric panel, and gated deterministically. Every run is recorded here in full — including the runs that published nothing.

A run's working state is never committed. This page transcribes the durable record: the pull request body and the summary issue, both linked from each entry.

Runs recorded
30
Pages fetched
4,308
Claims proposed
4,607
Edits published
3,698
Items withheld
605

Showing 21–23 of 23 runsfiltered by Published

Clear filter
  1. 2026-08-29-34e751

    Data refresh 2026-08-29

    Scope requested: Every creator in organizations.json — ai2, ai21-labs, amazon, anthropic, alibaba-cloud, cohere, deepseek, google-deepmind, meta, microsoft, mistral-ai, moonshot-ai, nvidia, openai, tii, xai, zhipu-ai — under the pilot 2-of-3 policy.Published3 edits posted · 4 items withheld

    An agent-run, source-backed refresh under ADR 0003. All 17 creators in organizations.json were scouted; 32 pages were fetched and hashed across 18 creator slugs, and only two creators produced claims at all — Anthropic with three and OpenAI with one. Fifteen blind reviewers cast fifteen verdicts across three rubrics, eight deterministic checks passed, and three edits landed across two dataset documents before GitHub merged PR #529 on a green web-ci and Pages deployed successfully. The principal finding is small and was sitting in plain sight: the anthropic-claude-4-8 family existed with no release record and therefore rendered empty, so this run added the missing Claude Opus 4.8 release and the docs page it is sourced from. No human reviewed any part of it. This entry was transcribed a day late — see the caveats.

    1. PreflightRanAnchor a6a3dfc, selected by merge-base with refs/remotes/origin/main and computed by the gate rather than supplied — requestedBase was null. The approved-origin catalogue parsed cleanly at that anchor: 147 dataset sources and 12 profile catalogues out of 13 profile files, yielding 33 approved origins. The one profile listed but not drawn on is tools/updater/profiles/generic/long-tail.json, which configures no origins. The anchor is therefore full rather than silently narrowed.
    2. ScoutRan32 pages fetched and hashed across 18 creator slugs. Every quote was extracted by anchor from fetched page text, so none is a recollection. No page budget was exhausted. ai.meta.com/blog/ returned HTTP 400 to every request tried, including with a browser User-Agent and a cookie jar, so Meta scouting fell back to huggingface.co/meta-llama, an approved origin; no Meta claim rested on the unreachable page and no Meta record changed. The 15 creators outside Anthropic and OpenAI produced coverage observations rather than claims.
    3. ReviewRanThree independent reviewers per claim, launched in parallel across different model families, none seeing the scout's reasoning, another reviewer's verdict, or the running tally. The chair did not vote. One claim was reviewed twice and this is disclosed rather than hidden: round 1's provenance reviewer rejected the Opus 4.8 release because no attached quote stated the modalities, which was a mechanical defect — the bundle generator's block extractor matched an earlier occurrence of "Context window 1M tokens", so the "Input → output Text and images → text" line was never attached. The rubric's own remedy for a missing quote is to attach it, so the anchor was fixed, intendedUse was tightened to attribute rather than assert, and three fresh reviewers re-reviewed. Round 2's provenance reviewer rejected again on different, judgment-based grounds and the claim was not revised a third time: repeated revision to chase a verdict is vote-shopping. Fifteen verdicts were cast in total; the twelve from the final panels are published verbatim in the pull request body, and round 1's three rationales were not preserved.
    4. GatesRangate-evidence and gate-source-approval ran per creator before anything was applied; gate-dataset, npm run validate and gate-scope ran afterwards. No gate was skipped, no threshold lowered, no --force, no --admin, no --base override, and no direct push to main. gate-scope reported changed: 2, empty: false, outOfClass: [], so the change sat inside the ADR 0003 qualifying class and was eligible to auto-merge.
    5. PublishRanPR #529 carried the full evidence trail and was merged by GitHub via --auto once web-ci was green, not by the agent. Merge commit 0794286.
    6. DeployRanPages deploy run 33250588183 on main succeeded, and https://abdeslam-menacere.github.io/ModelTree/models/claude-opus-4-8/ returned HTTP 200 serving the new record. No revert needed.

    What was found

    Scouts
    17
    Pages fetched and hashed
    32
    Claims proposed
    4
    Claims per creator bundle, with the review threshold its profile set
    CreatorPolicyThresholdClaims
    anthropicpilot2-of-33
    openaipilot2-of-31
    What those claims proposed to do
    KindCountEffect
    Add2One release and one source proposed; both survived every stage and were applied.
    Unchanged2Re-verified against a primary source; no value changed. One had its verification date advanced and one had it withheld.

    Not covered

    • Fifteen of the seventeen creators scouted produced no claim at all. That is an honest zero per creator rather than a skipped stage, but it also means their records carry this run's attention without carrying its verification date.
    • ai.meta.com/blog/ returns HTTP 400 to this client and was not read; huggingface.co/meta-llama was used instead.
    • Google, Microsoft, Amazon, Cohere and OpenAI audio models remain uncovered by any claim this run could assemble.
    • Mistral Medium 3.5 was deliberately not claimed. Its release date is ambiguous between a product post dated 2026-05-22 and a version string reading "v 26.04", and an ambiguity is a finding rather than a coin to toss.

    What was evaluated

    Reviewers
    15
    Verdicts cast
    15
    Accepted by panel
    4
    Rejected by panel
    0
    Deterministic gates and required checks — 8 of 8 checks passed. Exit 0 is a pass; exit 2 means the gate could not run and is never treated as one.
    CheckScopeExitResult
    gate-evidence.mjsanthropic0PassPolicy pilot, threshold 2. Three claims, of which two were applicable.
    gate-evidence.mjsopenai0PassPolicy pilot, threshold 2. One claim, none applicable — an unchanged claim applies nothing.
    gate-source-approval.mjsanthropic0PassFour cited sources were inherited and one was proposed: anthropic-opus-4-8-docs, on https://platform.claude.com — an origin already approved at the anchor commit and already carrying inherited sources, so no new origin was introduced. No source was refused.
    gate-source-approval.mjsopenai0PassThe one cited source, openai-gpt-5-6-sol-docs, was inherited from an already approved origin. No source was refused.
    gate-dataset.mjsweb/src/data0Pass148 sources, 26 publishers, 17 organizations, 37 families, 64 releases, 7 model-fit statements.
    npm run validateweb/0Pass1613 tests executed across 71 files; astro check reported 0 errors.
    gate-scope.mjsbranch vs merge-base0Passchanged: 2, empty: false, outOfClass: []. Anchored on the merge-base the gate computed rather than one supplied to it.
    web-ciPR #529—PassSUCCESS. GitHub performed the merge via --auto on this check going green; the agent did not merge.

    Applied over a recorded dissent

    These met their threshold and were applied. The objection stands on the record and was not overruled.

    • anthropic-claude-opus-4-8-release-addProvenanceaccessType "proprietary-hosted" is not forced by the quotes, because hosted availability does not exclude downloadable weights; and predecessorIds: [] under-states an announcement that calls Opus 4.7 "its predecessor". Outvoted 2-1. The claim was applied and both points are recorded here and in the pull request body as unresolved dissent rather than smoothed over.
    • anthropic-claude-mythos-5-limited-release-unchangedProvenanceThe quotes do not uniquely force status "preview" over "current", and do not re-state the recorded intendedUse. Outvoted 2-1, and materially right in the event: the claim reached its threshold and still applied nothing, because the verification date it would have advanced was withheld on separate grounds.

    Posted 3 edits

    3 edits across 2 documents, a net change of 2 records.

    Dataset documents this run changed
    DocumentBeforeAfterWhat changed
    releases.json6364One release added: anthropic-claude-opus-4-8. openai-gpt-5-6-sol had its verifiedAt advanced to 2026-08-29.
    sources.json147148One source added: anthropic-opus-4-8-docs — the platform.claude.com model overview page the Opus 4.8 release is drawn from, accepted 3-of-3 on an origin already approved at the anchor commit. lastCheckedDate moved to 2026-08-29 on three of the four inherited sources re-read this run; anthropic-fable-5-mythos-5-docs was held at 2026-08-26 with the Mythos 5 claim it belongs to. Sources are listed here rather than under the posted records below, which carry links and so hold only the collections the site routes.

    Each document links to the file as this run left it, not as it stands today.

    Records added

    • Claude Opus 4.8passportreleasesanthropic-claude-opus-4-8New release — released 2026-05-28, status legacy, 1M context and 128K max output, text and image in, text out, API alias claude-opus-4-8. Fills the anthropic-claude-4-8 family, which until now had no release and rendered empty. Carries the recorded provenance dissent on accessType and on its empty lineage arrays.

    Not posted 4 items

    Verification date deliberately held back

    • releases/anthropic-claude-mythos-5.verifiedAtHeld at 2026-08-15; nothing was applied for this claim despite it reaching its threshold. validate.ts forbids guidance dated before the evidence beneath it, and fit-claude-mythos-5-limited-availability, verified 2026-08-15, rests on this release's status and intendedUse. Advancing the release would have silently invalidated that fit statement — validation failed exactly this way when it was first attempted. Re-dating guidance this run gathered no evidence for would have been the larger claim, so the date was withheld instead. This also matches how gate-evidence treats unchanged claims, which apply nothing.Blocked by fit-claude-mythos-5-limited-availabilityvalidate.ts

    Sources conflict, so no value changed

    • mistral-medium-3-5Not claimed at all. Its release date is ambiguous between a product post dated 2026-05-22 and a version string reading "v 26.04". Neither reading is forced by the other, so the run recorded the disagreement rather than picking a side. The dataset still holds nothing on this model, which is the cost of leaving the ambiguity explicit.

    Out of the run’s reach

    • meta-announcement-indexhttps://ai.meta.com/blog/ returns HTTP 400 to every request tried, including with a browser User-Agent and a cookie jar. Meta scouting fell back to huggingface.co/meta-llama, an approved origin. No Meta claim rested on the unreachable page and no Meta record changed, so absence of a Meta finding here is not evidence that there was nothing to find.Blocked by https://ai.meta.com/blog/
    • coverage-google-microsoft-amazon-cohere-openai-audioGoogle, Microsoft, Amazon, Cohere and OpenAI audio models were scouted and produced coverage observations rather than claims. The observations are carried as follow-ups below rather than being written into the dataset as inferences.

    What this run does not prove

    • No human reviewed the pull request. The evidence trail, the deterministic gates and the required web-ci check are the whole of the oversight.
    • A green run proves the dataset is internally coherent and that every applied claim carried a quote from an approved origin. It does not prove the sources are right.
    • Two creators out of seventeen produced claims. The other fifteen were read and yielded nothing claimable, so this run moved the dataset barely at all and its silence about them is not a clean bill of health.
    • Round 1's three review rationales for the Opus 4.8 release claim were not preserved verbatim in the run artifacts, so the audit trail for that claim starts at round 2. That gap is follow-up 6 and it is the reason the reviewer count here exceeds the twelve rationales published.
    • editsApplied counts the three claims that reached the dataset — two adds and one advanced verification date — following the convention of the earlier entries here. The merge commit also moves lastCheckedDate on three sources that rode along with those claims, which the diff shows and this count does not.
    • This entry was written on 2026-08-30, a day after the run, because the run could not record itself: refresh-runs.json sits outside the ADR 0003 qualifying class that gate-scope enforces, so including it in PR #529 would have failed that gate and forfeited auto-merge. The transcription needs its own human-merged pull request, and for this run that pull request was initially never opened. The absence was noticed only when a reader asked why the page showed no 2026-08-29 line.

    Follow-ups — proposed, not fixed

    • Re-verify fit-claude-mythos-5-limited-availability so the Mythos 5 release verifiedAt can move. It is blocking a routine re-verification today.
    • Populate predecessorIds and successorIds across the Claude Opus line. Opus 4.6, 4.7 and now 4.8 all carry empty lineage arrays while the announcements state the relationships explicitly. Fix the line as a whole rather than one record.
    • Resolve the Mistral Medium 3.5 release-date ambiguity — decide which of the two published dates the dataset should record, or record the ambiguity explicitly.
    • Close coverage gaps for Google, Microsoft, Amazon, Cohere, and OpenAI audio models.
    • Find a reachable Meta announcement index to replace ai.meta.com/blog.
    • Persist superseded review rounds verbatim in the run artifacts, so a corrected claim's first-round rationales survive for audit.
    • Nothing notices when a published run never gets transcribed into this log. The publishing skill set opens the dataset pull request and files the summary issue, and the log entry is a separate human-merged change that no check requires; this run's line was missing for a day and only a reader's question surfaced it.
  2. 2026-08-27-ab1644

    Data refresh 2026-08-27

    Scope requested: Every creator in organizations.json, plus the long-tail profile sweepPublished35 edits posted · 56 items withheld

    An agent-run, source-backed refresh under ADR 0003. Five scouts fetched and hashed 130 primary pages and proposed 104 claims; twelve blind reviewers cast 312 verdicts across three rubrics; six deterministic gates passed; 35 edits landed across four dataset documents and GitHub Pages deployed successfully. 51 claims were dropped, most of them to one scout-side fault that proposed new sources without the paired citation edit. No human reviewed any part of it.

    1. PreflightRanClean tree, gh authenticated, no unmerged pull request from a previous refresh.
    2. ScoutRanFive bundles, one per creator profile plus a long-tail sweep. 130 page snapshots hashed. openai.com/news/ returned 403 and the RSS feed was used instead; ai.meta.com/blog/ returned 400; docs.anthropic.com now redirects to platform.claude.com.
    3. ReviewRanTwelve reviewers, three rubrics over four bundles. The long-tail bundle had no claims to review. No threshold was lowered and no reviewer was re-run.
    4. GatesRangate-evidence, gate-source-approval and check-bundle-pairing before applying anything; gate-dataset, npm run validate, and gate-scope after. The coupled drop set was iterated to a fixpoint over 3 passes.
    5. PublishRanPR #417 opened with the full evidence trail across the body and two comments, and merged by GitHub on a green web-ci.
    6. DeployRanPages deployed main @ 547691a successfully; the live site serves the new entities. No revert needed.

    What was found

    Scouts
    5
    Pages fetched and hashed
    130
    Claims proposed
    104
    Claims per creator bundle, with the review threshold its profile set
    CreatorPolicyThresholdClaims
    openaipilot2-of-326
    anthropicpilot2-of-324
    google-deepmindpilot2-of-322
    metapilot2-of-332
    long-tail sweeplong-tail3-of-30
    What those claims proposed to do
    KindCountEffect
    Add74Proposed new records; 30 survived every stage.
    Change8Field corrections; 5 survived every stage.
    Unchanged20Re-verified against a primary source; no value changed. 11 records had verifiedAt moved forward.
    Conflict2Primary sources disagree; both sides recorded, no value changed. Neither reached the dataset.

    Not covered

    • Any creator outside the four pilot profiles and the long-tail catalogue.
    • openai.com/news/ returns 403 to this client; the RSS feed was read instead, so anything on the news pages but absent from the feed was not seen.
    • ai.meta.com/blog/ returns 400 to this client and was not read.
    • The OpenAI page budget was exhausted at 40 pages, so its catalogue was not read to the end.
    • The long-tail sweep returned zero claims. That is an honest zero, not a skipped stage — it was gated like every other bundle.

    What was evaluated

    Reviewers
    12
    Verdicts cast
    312
    Accepted by panel
    83
    Rejected by panel
    21
    Deterministic gates and required checks — 8 of 8 checks passed. Exit 0 is a pass; exit 2 means the gate could not run and is never treated as one.
    CheckScopeExitResult
    gate-evidence5 bundles0PassThree rubrics present per claim, no duplicate votes, no empty rationale, every claim at its profile threshold.
    gate-source-approval5 bundles0Pass76 citations against anchor 052fb0d, selected by merge-base with refs/remotes/origin/main. requestedBase was null, so the run could not approve its own committed source. 16 approved origins, anchored on 61 sources already in the dataset and 5 reviewed profile catalogues. No new host admitted, and no source added to make a citation resolve.
    check-bundle-pairingnot required5 bundles0PassLanded on main as #413 mid-run and was run from main copy rather than added to this branch, since adding it would be an out-of-class change gate-scope would rightly refuse. It named the same unpaired sources this run had already found independently.
    gate-datasetworking tree0PassThe dataset is internally coherent after the edits were applied: 80 sources, 19 families, 35 releases.
    gate-scopebranch vs anchor0Passchanged: 4, outOfClass: [], empty: false. Exit 0 alone is ambiguous; the publish precondition is exit 0 and changed > 0.
    npm run validatebaseline and after0Pass579 tests across 24 files, astro check 0 errors.
    web-ciPR #417—PassGreen. This is the check branch protection requires before a merge.
    skills-cinot requiredPR #417—PassGreen, unlike the 2026-08-25 run where it was red and non-blocking.

    Applied over a recorded dissent

    These met their threshold and were applied. The objection stands on the record and was not overruled.

    • openai-gpt-5-1-family-addProvenanceThe RSS quote states GPT-5.1 was introduced for developers on 2025-11-13 and the docs quote states coding/agentic use and token limits, but no quote states the proposed family status "legacy" or the multimodal category. The proposed record therefore states more than the evidence quotes do.
    • openai-gpt-5-2-family-addProvenanceThe RSS quote states "Introducing GPT-5.2" with a 2025-12-11 pubDate, and the docs quote calls it a previous frontier model. No quote states the proposed family status "legacy" as a status value, so the record goes beyond the quoted evidence.
    • openai-gpt-5-3-codex-family-addProvenanceThe RSS quote gives the GPT-5.3-Codex introduction and date, and the docs quote says it is optimized for agentic coding. No quote states the proposed family status "current", so the proposed record adds an unstated field.
    • openai-gpt-image-family-addProvenanceThe dated announcement quote names "ChatGPT Images 2.0", not GPT-Image or GPT-Image-2. The GPT Image 2 docs quote states image generation/editing but not the 2026-04-21 introduction date for that entity.
    • anthropic-claude-4-6-familyProvenanceThe quotes name Claude Opus 4.6 and Claude Sonnet 4.6 and describe their capabilities. They do not state a "Claude 4.6" generation family, the 2026-02-05 firstReleaseDate for that family, or its status.
    • anthropic-claude-4-7-familyProvenanceThe quote states Opus 4.7 improves on Opus 4.6 in advanced software engineering. It does not state a broader "Claude 4.7" family, the proposed firstReleaseDate, or the status field.
    • anthropic-claude-4-8-familyProvenanceThe quote states Anthropic is upgrading Claude Opus to Claude Opus 4.8. It does not state a broader "Claude 4.8" generation family, its firstReleaseDate, or its status.
    • meta-llama-4-maverick-original-sourceProvenanceThe quote says the repository contains original checkpoints for Meta's llama-stack codebase. It does not name meta-llama/Llama-4-Maverick-17B-128E-Instruct-Original, so the source title is not stated by the quote alone.
    • meta-llama-3-2-1b-releaseProvenanceThe quotes state Llama 3.2 1B details, 1.23B parameters, 128k context, release date, and the Llama 3.2 license title. No quote states the proposed "legacy" status or the downloadable/OSI license fields.
    • meta-llama-3-2-3b-releaseProvenanceThe quotes state Llama 3.2 3B details, 3.21B parameters, release date, and the Llama 3.2 license title. No quote states the proposed 128,000-token context window for this 3B claim or the "legacy" status.
    • meta-llama-3-2-11b-vision-releaseProvenanceThe quotes state Llama 3.2 Vision 11B details, 10.6B parameters, 128k context, release date, and the license title. No quote states the proposed "legacy" status or the downloadable/OSI license fields.
    • meta-llama-3-2-90b-vision-releaseProvenanceThe quotes state Llama 3.2 Vision 90B details, 88.8B parameters, 128k context, release date, and the license title. No quote states the proposed "legacy" status or the downloadable/OSI license fields.
    • meta-llama-4-maverick-api-aliasesProvenanceThe first quote names meta-llama/Llama-4-Maverick-17B-128E, but the second only says "original checkpoints" without naming the exact Instruct-Original repository. Read alone, the quotes do not state both proposed aliases.
    • meta-llama-4-maverick-source-idsProvenanceThe first quote identifies the base Maverick repository, but the second only says "original checkpoints" without naming the exact original-checkpoint model card. The evidence therefore does not state both newly proposed source IDs.

    Posted 35 edits

    35 edits across 4 documents, a net change of 30 records.

    Dataset documents this run changed
    DocumentBeforeAfterWhat changed
    sources.json618019 sources added.
    families.json1219Seven families added.
    releases.json3135Four releases added.
    organizations.json44Verification dates moved forward; no record added or removed.

    Each document links to the file as this run left it, not as it stands today.

    Records added

    • GPT-5.1in the treefamiliesopenai-gpt-5-1New OpenAI family; carries a recorded provenance dissent.
    • GPT-5.2in the treefamiliesopenai-gpt-5-2New OpenAI family; carries a recorded provenance dissent.
    • GPT-5.3-Codexin the treefamiliesopenai-gpt-5-3-codexNew OpenAI family; carries a recorded provenance dissent.
    • GPT-Imagein the treefamiliesopenai-gpt-imageNew OpenAI family; carries a recorded provenance dissent.
    • Claude 4.6in the treefamiliesanthropic-claude-4-6New Anthropic generation family; carries a recorded provenance dissent.
    • Claude 4.7in the treefamiliesanthropic-claude-4-7New Anthropic generation family; carries a recorded provenance dissent.
    • Claude 4.8in the treefamiliesanthropic-claude-4-8New Anthropic generation family; carries a recorded provenance dissent.
    • Llama 3.2 1Bpassportreleasesmeta-llama-3-2-1bNew release; carries a recorded provenance dissent on its status and license fields.
    • Llama 3.2 3Bpassportreleasesmeta-llama-3-2-3bNew release; carries a recorded provenance dissent on its context window and status.
    • Llama 3.2 11B Visionpassportreleasesmeta-llama-3-2-11b-visionNew release; carries a recorded provenance dissent on its status and license fields.
    • Llama 3.2 90B Visionpassportreleasesmeta-llama-3-2-90b-visionNew release; carries a recorded provenance dissent on its status and license fields.

    Not posted 56 items

    Rejected by the review panel

    • openai-gpt-5-1-release-addOpenAI's API docs list GPT-5.1 as an API model for coding and agentic tasks. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • openai-gpt-5-2-release-addOpenAI's API docs list GPT-5.2 as an API model for professional work. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • openai-gpt-5-3-codex-release-addOpenAI's API docs list GPT-5.3-Codex as an agentic coding model. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • openai-gpt-5-4-mini-release-addOpenAI's API docs list GPT-5.4 Mini as a faster GPT-5.4 variant for high-volume workloads. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • openai-gpt-5-4-nano-release-addOpenAI's API docs list GPT-5.4 nano as a GPT-5.4-class model for simple high-volume tasks. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • openai-gpt-image-2-release-addOpenAI's API docs list GPT-Image-2 as an image-generation model. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • anthropic-claude-sonnet-4-5-releaseClaude Sonnet 4.5 should be added as an Anthropic Claude 4.5 release. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • anthropic-claude-opus-4-5-releaseClaude Opus 4.5 should be added as an Anthropic Claude 4.5 release. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • anthropic-claude-opus-4-6-releaseClaude Opus 4.6 should be added as an Anthropic Claude 4.6 release. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • anthropic-claude-sonnet-4-6-releaseClaude Sonnet 4.6 should be added as an Anthropic Claude 4.6 release. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • anthropic-claude-opus-4-7-releaseClaude Opus 4.7 should be added as an Anthropic Claude 4.7 release. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • anthropic-claude-opus-4-8-releaseClaude Opus 4.8 should be added as an Anthropic Claude 4.8 release. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • google-gemini-2-5-flash-lite-add-releaseGemini 2.5 Flash-Lite should be added as a current Gemini 2.5 release dated July 22, 2025. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • google-gemini-3-flash-preview-add-releaseGemini 3 Flash Preview should be added as a preview Gemini 3 release dated December 17, 2025. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • google-gemini-3-1-flash-image-add-releaseGemini 3.1 Flash Image should be added as a current Gemini 3 release dated May 28, 2026. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • google-gemini-3-pro-image-add-releaseGemini 3 Pro Image should be added as a current Gemini 3 release dated May 28, 2026. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • google-gemini-2-5-flash-image-add-releaseGemini 2.5 Flash Image should be added as a current Gemini 2.5 release dated October 2, 2025. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • google-gemini-3-5-transcribe-add-releaseGemini 3.5 Transcribe should be added as a current Gemini 3 release dated to August 2026. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • google-gemini-3-5-live-translate-preview-add-releaseGemini 3.5 Live Translate Preview should be added as a preview Gemini 3 release dated to June 2026. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • google-gemini-3-1-flash-live-preview-add-releaseGemini 3.1 Flash Live Preview should be added as a preview Gemini 3 release dated March 11, 2026. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)
    • google-gemini-3-1-flash-tts-preview-add-releaseGemini 3.1 Flash TTS Preview should be added as a preview Gemini 3 release dated April 13, 2026. Did not reach 2 of 3 accepts under the pilot policy.Blocked by pilot policy (2-of-3)

    Accepted by the panel, then dropped

    • source-openai-api-docsModels | OpenAI API should be added as an OpenAI official-docs source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-openai-gpt-5-4-mini-docsGPT-5.4 Mini model documentation should be added as an OpenAI official-docs source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-openai-gpt-5-4-nano-docsGPT-5.4 nano model documentation should be added as an OpenAI official-docs source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-openai-daybreak-red-docsDaybreak Red model documentation should be added as an OpenAI official-docs source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-openai-daybreak-blue-docsDaybreak Blue model documentation should be added as an OpenAI official-docs source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-openai-gpt-realtime-mini-docsGPT-Realtime Mini model documentation should be added as an OpenAI official-docs source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • anthropic-fable-5-docs-sourceClaude Fable 5 should be added as an official Anthropic source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • anthropic-opus-5-docs-sourceClaude Opus 5 should be added as an official Anthropic source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • anthropic-haiku-4-5-docs-sourceClaude Haiku 4.5 should be added as an official Anthropic source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • anthropic-fable-5-biology-safeguards-sourceImproving Fable 5's biology safeguards should be added as an official Anthropic source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • anthropic-opus-4-5-announcement-sourceIntroducing Claude Opus 4.5 should be added as an official Anthropic source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-google-gemini-2-5-flash-lite-docsAdd Gemini 2.5 Flash-Lite as an official Google AI source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-google-gemini-3-flash-preview-docsAdd Gemini 3 Flash preview as an official Google AI source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-google-gemini-3-1-flash-image-docsAdd Gemini 3.1 Flash image as an official Google AI source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-google-gemini-3-pro-image-docsAdd Gemini 3 Pro image as an official Google AI source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-google-gemini-2-5-flash-image-docsAdd Gemini 2.5 Flash image (Nano Banana) as an official Google AI source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-google-gemini-3-5-transcribe-docsAdd Gemini 3.5 Transcribe as an official Google AI source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-google-gemini-3-5-live-translate-docsAdd Gemini 3.5 Live translate as an official Google AI source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-google-gemini-3-1-flash-live-docsAdd Gemini 3.1 Flash live preview as an official Google AI source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • source-google-gemini-3-1-flash-tts-docsAdd Gemini 3.1 Flash TTS preview as an official Google AI source. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • meta-llama-guard-4-sourceThe source catalog should include meta-llama/Llama-Guard-4-12B. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • meta-llama-prompt-guard-2-86m-sourceThe source catalog should include meta-llama/Llama-Prompt-Guard-2-86M. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts
    • meta-llama-prompt-guard-2-22m-sourceThe source catalog should include meta-llama/Llama-Prompt-Guard-2-22M. Accepted by the panel, then dropped: validate.test.ts refuses a source no record cites, and the scout proposed this source without the paired change claim that would wire it into a record sourceIds.Blocked by validate.test.ts

    Verification date deliberately held back

    • releases/openai-gpt-5.verifiedAtModel fit statement fit-gpt-5-superseded rests on this release and was verified 2026-08-18. Moving verifiedAt to 2026-08-27 would make that guidance stale, and this run gathered no evidence about fit statements. Capping the date to fit the invariant would assert a verification that never happened.Blocked by fit-gpt-5-supersededvalidate.ts
    • releases/anthropic-claude-mythos-5.verifiedAtModel fit statement fit-claude-mythos-5-limited-availability rests on this release and was verified 2026-08-15. Moving verifiedAt to 2026-08-27 would make that guidance stale, and this run gathered no evidence about fit statements. Capping the date to fit the invariant would assert a verification that never happened.Blocked by fit-claude-mythos-5-limited-availabilityvalidate.ts
    • releases/meta-llama-4-scout.verifiedAtModel fit statement fit-llama-4-scout-self-hosting rests on this release and was verified 2026-08-15. Moving verifiedAt to 2026-08-27 would make that guidance stale, and this run gathered no evidence about fit statements. Capping the date to fit the invariant would assert a verification that never happened.Blocked by fit-llama-4-scout-self-hostingvalidate.ts

    Sources conflict, so no value changed

    • google-gemini-embedding-2-api-code-conflictGoogle sources disagree on whether the Gemini Embedding 2 API identifier is gemini-embedding-2 or gemini-embedding-2-preview. All three rubrics accepted it as a conflict; a conflict is recorded as a finding and never applied to the dataset.Blocked by google-gemini-models-referencegoogle-gemini-deprecations

    Source refused by the approval gate

    • openai-gpt-5-6-cyber-daybreak-red-aliasOpenAI's Daybreak Red model documentation lists daybreak-red-latest as an alias for gpt-5.6-cyber. Rests on a source withdrawn earlier in this same run, so gate-source-approval refused it. Writing the missing citation by hand would have been an unreviewed dataset edit, so the coupled set was withheld together.Blocked by gate-source-approval.mjs
    • openai-gpt-5-6-sol-daybreak-blue-aliasOpenAI's Daybreak Blue model documentation lists daybreak-blue-latest as an alias for gpt-5.6-sol. Rests on a source withdrawn earlier in this same run, so gate-source-approval refused it. Writing the missing citation by hand would have been an unreviewed dataset edit, so the coupled set was withheld together.Blocked by gate-source-approval.mjs
    • openai-gpt-realtime-mini-status-conflictOpenAI's model catalog labels GPT-Realtime Mini deprecated, while its individual model page labels it default. Rests on a source withdrawn earlier in this same run, so gate-source-approval refused it. Writing the missing citation by hand would have been an unreviewed dataset edit, so the coupled set was withheld together.Blocked by gate-source-approval.mjs
    • anthropic-claude-fable-5-intended-use-biology-caveatClaude Fable 5's intended-use text should include Anthropic's caveat that dual-use biology requests still fall back to Opus 5. Rests on a source withdrawn earlier in this same run, so gate-source-approval refused it. Writing the missing citation by hand would have been an unreviewed dataset edit, so the coupled set was withheld together.Blocked by gate-source-approval.mjs
    • anthropic-claude-haiku-4-5-status-activeClaude Haiku 4.5 remains an active latest Claude model. Rests on a source withdrawn earlier in this same run, so gate-source-approval refused it. Writing the missing citation by hand would have been an unreviewed dataset edit, so the coupled set was withheld together.Blocked by gate-source-approval.mjs
    • anthropic-claude-haiku-4-5-context-windowClaude Haiku 4.5 still has a 200,000-token context window. Rests on a source withdrawn earlier in this same run, so gate-source-approval refused it. Writing the missing citation by hand would have been an unreviewed dataset edit, so the coupled set was withheld together.Blocked by gate-source-approval.mjs
    • anthropic-claude-haiku-4-5-api-aliasesClaude Haiku 4.5 still uses claude-haiku-4-5 as a convenience alias for claude-haiku-4-5-20251001. Rests on a source withdrawn earlier in this same run, so gate-source-approval refused it. Writing the missing citation by hand would have been an unreviewed dataset edit, so the coupled set was withheld together.Blocked by gate-source-approval.mjs

    Blocked by policy before it could run

    • long-tail-creatorsQwen, zai-org, MiniMaxAI, deepseek-ai, moonshotai, sensenova, Lightricks and ornith-ai are trending on an approved origin, but organizationSchema requires website and releasePage URLs that no approved-origin page states, and each creator own host is not an approved origin. Approving a new origin is a human decision, not one a refresh run may take for itself.Blocked by organizationSchemaapproved-origin list

    What this run does not prove

    • No human reviewed the pull request. The evidence trail, the deterministic gates and the required web-ci check are the whole of the oversight.
    • A green run proves the dataset is internally coherent and every applied claim carried a quote from an approved origin. It does not prove the sources are right.
    • Half the proposed claims did not survive. The dataset is more complete than it was, not complete.
    • Two page budgets were exhausted and two hosts refused this client, so absence of a record here is not evidence that the model does not exist.
    • The per-creator applied counts in summary issue #418 and its gate-dataset source count disagree with the pull request body. The figures here follow the pull request body and the merge commit itself, which agree with each other.

    Follow-ups — proposed, not fixed

    • Scouts are not yet running check-bundle-pairing, which landed on main mid-run and would have caught this run largest failure class at bundle time.
    • The GPT-Realtime Mini status conflict was unanimously accepted and still could not be published, because both its sources were unpaired. The disagreement is real and remains unrecorded in the dataset.
    • Long-tail creators have no route into the dataset under the current approved origins, and approving an origin is a human decision.
    • The reviewed profiles and the dataset disagree about canonical release names, which drove most editorial rejections and will recur every run until it is settled.
    • Three model fit statements are older than the release facts they rest on and block those releases from carrying this run verification date.
  3. 2026-08-26-d5f729

    Data refresh 2026-08-26

    Scope requested: Every creator in organizations.json, plus the long-tail profile sweepPublished63 edits posted · 9 items withheld

    An agent-run, source-backed refresh under ADR 0003. Five scouts fetched and hashed 55 primary pages and proposed 71 claims; twelve blind reviewers cast 213 verdicts across three rubrics; four deterministic gates passed; 63 edits landed across five dataset documents and GitHub Pages deployed successfully. No human reviewed any part of it.

    1. PreflightRanClean tree, gh authenticated, no unmerged pull request from a previous refresh.
    2. ScoutRanFive bundles, one per creator profile plus a long-tail sweep. 55 page snapshots hashed.
    3. ReviewRanTwelve reviewers, three rubrics over four bundles. The long-tail bundle had no claims to review.
    4. GatesRangate-evidence and gate-source-approval before applying anything; gate-dataset, npm run validate, and gate-scope after.
    5. PublishRanPR #302 opened with the full evidence trail and merged by GitHub on a green web-ci.
    6. DeployRanPages deployed main @ 0e9867b successfully; the live site serves the new records. No revert needed.

    What was found

    Scouts
    5
    Pages fetched and hashed
    55
    Claims proposed
    71
    Claims per creator bundle, with the review threshold its profile set
    CreatorPolicyThresholdClaims
    openaipilot2-of-314
    anthropicpilot2-of-318
    google-deepmindpilot2-of-319
    metapilot2-of-320
    long-tail sweeplong-tail3-of-30
    What those claims proposed to do
    KindCountEffect
    Add25New records.
    Change15Field corrections and counter updates.
    Unchanged29Re-verified against a primary source; no value changed.
    Conflict2Primary sources disagree; both sides recorded, no value changed.

    Not covered

    • Any creator outside the four pilot profiles and the long-tail catalogue.
    • www.llama.com content, deferred because the host now redirects to an unapproved origin.
    • The long-tail sweep returned zero claims. That is an honest zero, not a skipped stage — it was gated like every other bundle.

    What was evaluated

    Reviewers
    12
    Verdicts cast
    213
    Accepted by panel
    71
    Rejected by panel
    0
    Deterministic gates and required checks — 6 of 7 checks passed. Exit 0 is a pass; exit 2 means the gate could not run and is never treated as one.
    CheckScopeExitResult
    gate-evidence5 bundles0PassThree rubrics present per claim, no duplicate votes, no empty rationale, every claim at its profile threshold.
    gate-source-approval5 bundles0Pass134 citations against anchor 13276b0, selected by merge-base with refs/remotes/origin/main. 20 inherited sources, 17 proposed, 16 approved origins, no new host admitted.
    gate-datasetworking tree0PassThe dataset is internally coherent after the edits were applied.
    gate-scopebranch vs anchor0Passchanged: 5, outOfClass: [], empty: false. Exit 0 alone is ambiguous; the publish precondition is exit 0 and changed > 0.
    npm run validatebaseline and after0Pass400/400 tests, 0 errors both before any change and on the branch. The baseline was captured first so a pre-existing red main could not be mistaken for damage from this run.
    web-ciPR #302—Pass400/400 tests, 0 errors. This is the check branch protection requires before a merge.
    skills-cinot requiredPR #302—FailRed, and not a required check, so GitHub merged on web-ci alone before it could be acted on. Filed as #304: gates.test.mjs pins TODAY to 2026-08-25 but asserts it against the live dataset, so any same-day refresh fails it.

    Applied over a recorded dissent

    These met their threshold and were applied. The objection stands on the record and was not overruled.

    • openai-add-gpt-5-6-cyber-releaseEditorial and entity boundariesreleaseDate was taken from an RSS pubDate, which dates the announcement item rather than the release.
    • anthropic-unchanged-source-opus-5-announcement-checkedProvenanceThe quote supports the API identifier but not the pricing half of the same claim.
    • meta-muse-video-releaseEditorial and entity boundariesA model described as "coming soon" was given a concrete day-precision releaseDate.

    Posted 63 edits

    63 edits across 5 documents, a net change of 24 records.

    Dataset documents this run changed
    DocumentBeforeAfterWhat changed
    sources.json476114 sources added.
    families.json1112One family added: meta-muse.
    releases.json2231Nine releases added.
    organizations.json44One field corrected; no record added or removed.
    usage-observations.json22Both readings updated; no record added or removed.

    Each document links to the file as this run left it, not as it stands today.

    Records added

    Not posted 9 items

    Accepted by the panel, then dropped

    • openai-add-source-deprecationsAccepted by the panel, then dropped by the chair. validate.test.ts enforces that an unreferenced source is dead provenance, and no reviewed claim wired openai-deprecations into any record's sourceIds. Adding that edit would have meant authoring dataset content no reviewer saw.Blocked by validate.test.ts
    • openai-change-gpt-5-status-deprecatedDropped with its source. Keeping the status change alone records "deprecated" against sourceIds that do not state it — every supporting quote comes from openai-deprecations.Blocked by openai-add-source-deprecations
    • openai-change-gpt-4-1-nano-status-deprecatedDropped for the same reason as the GPT-5 status change: its only supporting quote comes from the source that could not be added.Blocked by openai-add-source-deprecations

    Verification date deliberately held back

    • releases/anthropic-claude-haiku-4-5The field was re-read and unchanged, but validate.ts requires a model-fit statement to be at least as fresh as the facts it reads. Bumping verifiedAt would strand a dependent statement, so it stays at 2026-08-15. Under-claiming a verification is honest; over-claiming is not.Blocked by fit-claude-haiku-4-5-release-currentfit-claude-haiku-4-5-family-legacy
    • releases/anthropic-claude-mythos-5Held at 2026-08-15 for the same freshness rule: nobody re-derived the dependent fit statement over the re-read field.Blocked by fit-claude-mythos-5-limited-availability
    • families/meta-llama-4Held at 2026-08-15 by a test-suite coupling rather than a data fact: model-fit.test.ts injects fixtures pinned at 2026-08-15 over the real seed records. Tests are not dataset documents, so this run may not edit them.Blocked by model-fit.test.ts

    Sources conflict, so no value changed

    • families/anthropic-claude-4-5.statusTwo Anthropic pages disagree and neither changed a value. The models overview lists Claude Sonnet 4.5 under "Legacy models (still available)"; the deprecations page lists claude-sonnet-4-5-20250929 as Active, retirement not sooner than 29 September 2026. Conflicting data stays explicit rather than being smoothed over.
    • releases/google-gemini-3-5-flash-lite.statusThe Gemini 3 developer guide states "All Gemini 3 models are currently in preview"; the platform docs give gemini-3.5-flash-lite launch stage GA, released 21 July 2026. Recorded with both sides quoted; no value changed.

    Source refused by the approval gate

    • www.llama.comThe host now redirects to developer.meta.com, an origin neither the committed dataset nor any profile catalogue stands behind. The Meta scout deferred it rather than citing it, so the Muse claims rest on ai.meta.com instead. Admitting a new host is a human decision.Blocked by gate-source-approval

    What this run does not prove

    • The gates catch malformed, impossible, unreferenced, and boundary-violating data. They do not catch a well-formed claim that is simply wrong.
    • Per ADR 0005 the evidence gate checks the form of a citation, never its remote content. A gate pass attests that the paperwork is complete, not that the page still says what it said.
    • The three reviewers share a failure mode — three instances of one model family reading the same page — so a source that is itself wrong can carry all three.
    • Auto-merge was armed correctly, but because skills-ci is not a required check GitHub merged on web-ci alone while skills-ci was red. No gate was skipped and no threshold lowered; it does mean an unattended run cannot currently stop on a non-required check going red.

    Follow-ups — proposed, not fixed

    • A scout proposing a status change must also propose the sourceIds change that carries its source. This cost three panel-accepted OpenAI claims.
    • Fit-statement freshness blocks legitimate verification bumps on anthropic-claude-haiku-4-5, anthropic-claude-mythos-5, and meta-llama-4.
    • www.llama.com now redirects to developer.meta.com, a new host that needs a human decision on the approved-origin list.
    • Consider making skills-ci a required check, so a red non-required job can stop an unattended merge. Requiring a check is a branch-protection setting, so it is an owner action rather than a change this program can make.