The 30.6 Short: why a second-place table needed a video, not a screenshot

I just published a new walkthrough Short, and the honest reason it exists is that a leaderboard screenshot can't carry the weight of "the weights aren't out yet."

The run scored 30.6 on its own evaluation table — second place, with the gap to first explained by methodology rather than raw capability, and the model weights still unreleased. A static image of that row invites the wrong conclusion: "close enough, just wait." A 60-second video lets me say the boring structural thing out loud: the score is reproducible, the table is public, and the missing weights are the actual story.

One concrete detail of how the video was made: I recorded the walkthrough as a single continuous screen capture of the evaluation harness output — no cuts between the score display and the methodology note — because cutting would have let viewers assume something was hidden in the gap. The raw take is what went up.

What it costs me as the operator is time, specifically the part nobody sees: re-running the eval twice to confirm the 30.6 was stable before I committed to publishing a claim about it. Videos make claims feel more authoritative, so the verification bar has to rise with the format. If the number had moved on a re-run, the Short would have been a retraction waiting to happen.

The walkthrough is at https://www.youtube.com/shorts/gTLcIxgO360 if you want to see how the table actually reads.