I'm Voiding My Own Larkin Call. Camp Opens in Two Days.

Diddja ever build a stopwatch that goes off before the race starts? I did. Tonight at 23:59 it goes off.

POS-NHL-20260729-001 says Dylan Larkin opens Red Wings training camp with the Red Wings. I logged it in July at 0.72, walked it up to 0.93 on Sunday when Larkin said through the club's own account that he'd be at camp with his teammates. Good position. Right read. And it resolves today, September 15, while the Kid's sourcing has Detroit's camp opening September 17.

So on resolution day the strongest evidence in the world is a man saying he intends to be somewhere. That's not the claim. The claim is attendance. If I mark this won, I'm grading intent and calling it attendance, which is precisely the sleight of hand this whole ledger exists to prevent. If I mark it lost, I'm punishing a player for the calendar I typed. Neither one is a score. Both are theater.

It gets voided, with the reason written into the record: resolution timestamp preceded the event. I flagged this collision in two prior editions before it came due, which is the only part of this I feel decent about — the Kid re-flagged it again this morning and refused to resolve it himself, which was correct of him. A void isn't an erased bad call. A bad call would stay. This is a bad instrument.

And the claim goes right back on the board. POS-NHL-20260915-001, same thesis, 0.93, resolving September 19 — two days after camp actually opens, so the ledger finds out after the fact instead of guessing before it. Seven points against for the reasons that were always there: the captaincy is gone, Detroit opens the season without one, the GM chair is still empty with Horcoff running day-to-day, and the club has said out loud it won't discuss Larkin's future until somebody's hired. A statement of intent in September is not a man in a jersey in September.

The trade call sits untouched at 0.02. You don't move a franchise captain when nobody in the building holds the mandate to sign the paperwork, and the organization has functionally announced that's the situation until further notice.

Here's the rule I'm writing into my own process, out loud, so you can hold me to it: a position's resolution date has to sit after the event it grades, with daylight. Not on it. Not near it. After it. Every call on this board gets that check from here on, and if I ever void another one for this reason you get to bring this article back up and hit me with it.