iiRecord
Agentic AI Atlas · GAP-L2-P2-versionrange-attribute-on-modelversion
page:process-gaps-GAP-L2-P2-versionrange-attribute-on-modelversiona5c.ai
II.
Page reference

page:process-gaps-GAP-L2-P2-versionrange-attribute-on-modelversion

Reading · 1 min

GAP-L2-P2-versionrange-attribute-on-modelversion reference

ModelVersion.versionRange: versionRange semantically conflates "this version" with "a range of versions". Example claude-opus-4-7.yaml has versionRange: ">=4.7.0 <5.0.0" which is a range, but model:claude-opus-4-7 is intended to be one specific snapshot (claude-opus-4-7-20251201 or similar). The repo agent-catalog distinguishes ModelFamily (range-bearing) from ModelVersion (concrete snapshot id).

Pagewiki/process/gaps/GAP-L2-P2-versionrange-attribute-on-modelversion.mdOutgoing · 0Incoming · 1

GAP-L2-P2-versionrange-attribute-on-modelversion

FieldValue
idgap:versionrange-attribute-on-modelversion
titleModelVersion uses versionRange for what is really a single concrete version
level2
priorityP2
discoveredAt2026-04-28T00:00:00Z
sourceschema/examples/compute/models/claude-opus-4-7.yaml
statusopen
ownertbd

Current state

ModelVersion.versionRange: versionRange semantically conflates "this version" with "a range of versions". Example claude-opus-4-7.yaml has versionRange: ">=4.7.0 <5.0.0" which is a range, but model:claude-opus-4-7 is intended to be one specific snapshot (claude-opus-4-7-20251201 or similar). The repo agent-catalog distinguishes ModelFamily (range-bearing) from ModelVersion (concrete snapshot id).

Desired state

  • Rename ModelVersion.versionRangeModelVersion.versionId (string, e.g. snapshot id).
  • Move range-bearing claims to ModelFamily.activeVersionRange.
  • Update example to versionId: "claude-opus-4-7" plus separate aliasIds: ["claude-opus-4-7-20251201"].

Evidence

  • C:/work/v6/graph/schema/ontology-schema.yaml (ModelVersion attributes)
  • packages/agent-catalog/graph/nodes/models.yaml (uses modelVersionId shape)
  • https://platform.claude.com/docs/en/docs/about-claude/models/overview (snapshot date discipline)

Propagation status

  • Level 2: open

Propagation chain

  • Level 2: rename attribute, update 3 example model files, update compute-path.md.

Notes

Naming/semantics gap. Cascades into Level 1 fixes for Anthropic models.