C.W.K.
Stream
Lesson 01 of 12 · published

Reading a Model Card: The Five Questions

~10 min · model-card, evaluation

Level 0Token
0 XP0/94 lessons0/10 achievements
0/120 XP to next level120 XP to go0% complete

A model card is the standardized document a release ships alongside the weights. It tells you what the model is good for, what it isn't, and what compromises were made. Reading model cards critically is the single most useful "soft skill" in working with LLMs.

Five questions to ask of every model

  1. What was it trained on? Source datasets, total token count, data cutoff date, deduplication and filtering strategy. Implicit biases and capabilities follow the data.
  2. Which benchmarks were reported, and at what date? Older benchmarks (MMLU, ARC) are saturated; what's hard in 2026 is GPQA, AIME, SWE-bench, HLE. Be skeptical of benchmark numbers without context.
  3. What's the license? Apache 2.0 / MIT (use freely), Llama-style community licenses (commercial OK with conditions), research-only licenses (no commercial use), proprietary (API only). License determines who can use it for what.
  4. What's the context window — and how well is it actually used? "128K context" can mean anything from "trained at 128K" to "extended via YaRN with degraded recall past 32K." Always run a needle-in-a-haystack test.
  5. Does it support the modalities and languages I need? Many models are English-first; some are explicitly multilingual; some support vision/audio. Check before you commit.

These five questions filter 90% of model-selection decisions. The remaining 10% — does it match the latent style and personality you want? — requires actually using it.

Code

Model card audit checklist·markdown
## Model card audit (fill out before adopting)

- **Architecture**: ___ params, ___ layers, ___ d_model, ___ heads, ___ KV heads
- **Tokenizer**: ___ algorithm, ___ vocab size, ___ specials
- **Context**: ___ training window / ___ extended window / ___ measured-recall depth
- **Training**: ___ tokens, ___ data sources, ___ cutoff date, ___ FLOPs, ___ time
- **Post-training**: ___ SFT recipe, ___ alignment method (RLHF/DPO/GRPO/CAI), ___ tool-use training
- **License**: ___ what can I do with it commercially?
- **Modalities**: text [Y/N] / image [Y/N] / audio [Y/N] / video [Y/N]
- **Languages**: primary ___, supported ___
- **Benchmarks**: GPQA ___ / AIME ___ / SWE-bench ___ / HLE ___
- **Known weaknesses**: ___ (read the limitations section)

External links

Exercise

Pick three production models you might use (one frontier proprietary, one open-weight, one small specialized). Fill out the audit checklist for each. Where does each pass or fail the five questions? Which would you pick for a customer-facing chat product, and why?

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.