01 / MODEL INTELLIGENCETrack revisions instead of only model names
A display name is not always enough to identify the artifact evaluated. Preserve the strongest source revision identifier available, plus the time it was observed. Keep release events and logical model identity distinct. When immutable version information is unavailable, show that limitation rather than implying that the record is fully reproducible.
02 / MODEL INTELLIGENCEKeep reported results separate from local tests
Label source-reported capabilities separately from measurements your team has made. Keep the task definition, dataset version, and relevant runtime conditions with each evaluation. A useful review explains the tradeoff for your application rather than blending unrelated benchmark claims into a single score that appears more conclusive than its evidence.
03 / MODEL INTELLIGENCERecord limitations and missing documentation
Retain the model card or documentation reference and make missing information visible. An absent limitations section does not establish that a model has no limitations. Separate quality evaluation from usage, security, and deployment review. A watchlist entry should prompt a decision about testing, not imply automatic endorsement or production readiness.
Build a watchlist for one evaluation task
Define the model behavior your application needs, then choose a few sources that provide relevant release evidence. Track each candidate’s revision, documentation, and review state. Evaluate shortlisted candidates against the same representative cases and retain the conditions behind the results. The first watchlist should reduce the effort of making a measured choice, not maximize the number of announcements it collects.