Skip to content

feat(modelchk): name the task domain a tier is measured in - #24

Open
LilMGenius wants to merge 1 commit into
mainfrom
feat/modelchk-task-domain
Open

LilMGenius wants to merge 1 commit into
mainfrom
feat/modelchk-task-domain

Conversation

@LilMGenius

Copy link
Copy Markdown
Owner

modelchk sized a tier and an effort but said nothing about what a tier is measured against, so a binder that maps tiers to models had only price to go on. When two vendors price their lineups identically, price rank picks whichever model is listed first and every role drifts to one vendor, which is what role auto-assign in opencodex did (fixed there in lidge-jun/opencodex#7624).

This adds a third output, task_domain (coding, agentic, reasoning, writing, knowledge, general), which sizes nothing and names which measured strength the tier depends on. It also states how a binder resolves a tier: against live measured capability in that domain, with price choosing only among sufficient models. Three limits apply to any measurement source:

  • An explicit user mapping outranks measurement.
  • A model the source does not list counts as unmeasured, not weak.
  • The source's terms decide whether its scores may be shown or only used internally.

The text stays vendor-neutral: no model, vendor or evaluation source is named, and the rule against naming them now covers evaluation sources too. The README fix entry mentions the domain.

Gates, run locally on this branch as CI runs them: check-frontmatter.test.cjs (2 pass), validate-skills.sh, check-skill-refs.sh, check-links.sh, check-catalog-sync.cjs, check-deploy-home.cjs: all exit 0.

- Add a neutral task_domain output and state how a binder resolves a tier against live measured capability in that domain: a user mapping outranks measurement, an unlisted model is unmeasured rather than weak, and the source's terms decide whether scores may be shown
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant