registry: Claude-family model identities from harness evidence#72
Open
datacraftdevelopment wants to merge 3 commits into
Open
Conversation
…ble 5) from harness evidence
…tries tests/test_contributors.py failed on this branch: the HEAD commit's author, datacraftdevelopment (registry: Claude-family identities — Opus 4.8, Sonnet 5, Haiku 4.5, Fable 5), had no entry in README's Contributors section. CONTRIBUTING.md's credit policy is explicit that this is enforced, not promised, and the remedy is a same-PR addition: "Every merged community contributor is listed in the README's Contributors section, and tests/test_contributors.py fails the whole suite if anyone with merged work is missing." Add the entry, following the existing bullet format. The PR number is marked "(this PR)" pending assignment on GitHub — replace with the real "(#N)" once the PR is open.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
A
claudeengine block and four Claude-family model identities inregistry/model-identity.toml:claude-opus-4-8claude-sonnet-5claude-haiku-4-5claude-fable-5Engine metadata:
harness = "Claude Code",access = "Claude subscription",default_model_key = "claude-haiku-4-5".Evidence basis (per
docs/TAXONOMY.md)Evidence precedence is harness-reported model first. The Claude Code worker stream self-reports the model it actually ran in its result-message
modelUsagetelemetry. Ringer'sreported_modelcolumn stays null for these rows only because the capture regex is Codex-header–specific — so the self-report was read directly from the worker logs. Everysourcecites that self-report with run names + dates, plus Anthropic's own model page for the lab:modelUsage: {"claude-opus-4-8": …}inclaude-family-audition(2026-07-12) andhello-world-bakeoff(2026-07-17).modelUsage: {"claude-sonnet-5": …}inclaude-family-audition(2026-07-12) andhello-world-bakeoff(2026-07-17).modelUsage: {"claude-haiku-4-5": …}inclaude-family-audition(2026-07-12) andhello-world-site(2026-07-12). Also the engine'sdefault_model_key, matching the runtimemodel_default.modelUsage: {"claude-fable-5": …}infable-audition(2026-07-12), thencrm-build(2026-07-16) andchronoline-build(2026-07-17).The self-reported slug matches the manifest/config-resolved model in every case (no drift).
Fable 5: alias / unverified, not asserted lineage
Anthropic's Claude 5 family announcement names Fable 5 / Mythos 5 as a new tier above Opus sharing one underlying model; there is no public lineage beyond that.
docs/TAXONOMY.mdpermits a registry alias only when the actual model lineage is not established, requires it be marked as an alias in both the registry and the displayed name, and forbids presenting it as a confirmed lineage. So Fable 5 is entered as:alias = true, displayClaude Fable 5 (Anthropic, alias)— marked in both places.confidence = "unverified"— the lab (Anthropic) is verified from Anthropic's own announcement; the underlying model lineage is not, and is left unasserted pending public documentation.The rationale is captured in a comment on the entry so the alias treatment isn't mistaken for an oversight.
Contributor credit (CONTRIBUTING.md enforcement)
tests/test_contributors.pyaudits git history against README's Contributors section and fails the whole suite on any omission — per CONTRIBUTING.md, "Credit is enforced, not promised." The registry commit in this PR is authored bydatacraftdevelopment, so a second commit adds that entry to README's Contributors section, exactly as CONTRIBUTING.md sanctions ("Every merged community contributor is listed... the test fails the whole suite if anyone with merged work is missing"). The entry's PR-number citation reads "(this PR)" pending assignment — update it to "(#N)" once this PR is open.Tests
All three identity/taxonomy suites the derivation quality gates on pass, and the full suite is green at current HEAD (includes the Contributors fix above):
(The lone warning is a pre-existing
test_steering.pyreturn-value warning, unrelated to this change.)test_signal_contract.py, which loads this real registry to exercise the noncanonical-route guard, also passes — the grok route and every other existing entry resolve unchanged.Scope
Two commits:
registry/model-identity.toml(+47 lines, additive — the identity data) andREADME.md(+1 line — the Contributors credit required bytests/test_contributors.py, see above). No code paths change; existing engine/model rows and Contributors entries are untouched.🤖 Generated with Claude Code