The way Mike Levine was treated was a travesty. Of course, I am putting "by his team" in that mix, to what extent would depend on opportunity.
"We're going to need more time and assistance"
"Here's what we'll give you"
do not test it until "the day" to find out that 15 extra seconds a hand (plus whatever cushion the pair would normally have - the "time per pair" is a maximum, not an intended) isn't enough, and therefore have no argument other than "it took longer than expected" (like "yeah, it takes a long time to read the cards and make the inputs, but he's definitely using that time to think too") against not following the rules.
All respect to that team - and I've played against Mike a few years ago, and I didn't see him as particularly slow - but the time to protest is before the event starts, with documentation from testing/practise.
All respect to the USBF, but 3 minutes added on to a 15 board session seems like a ludicrously short window for what was expected to be needed.
I would suggest, however, that "profuse broadcasts" (especially on That Site, with its Alternative Title and desired readership) are nothing compared to what happens when you actually try enforcing the rules to "BB trials" level for the 99.8% of players (and 100.0% of the new players) that don't play at the BB trials. How much of that is that we don't actually teach the [-] Laws...
The reason declarer doesn't have penalty cards is obvious - there is no possible use of that information that will aid the offending side. The fact that declarer has that card can only help (or be of no consequence to) the defence, unlike the obvious benefit the defenders can get by "showing partner their hand". It's not a penalty for playing wrong, it's an attempt to minimize the damage of the leaked information.
I do understand that's your point - that it *should be* a penalty for playing wrong - but it's by no means "grotesque" and "some (implied - unknowable) reason".
And you are still talking to the person who missed his first ever chance of making day 2 of a national event because the spade 2 touched the table in its never stopping circle back to declarer's hand (instead of missing by an inch). So, it's not like it's always "don't care, it's declarer".
But I am actually quite happy to play a game where "two minutes for cross-checking" isn't the policy. Especially given the inability to (at cost) constantly surveil all the tables for "cross-checking". I am actually quite happy for the instruction that "yes, 81C3 exists, and it must be followed. Because it's not fair to those tables you're *not* watching, that means you do not kibitz as a TD; and while you're wandering the tables, try to not pay the kind of attention to the play that would trigger 81C3. Of course, if they make it obvious..." Especially in a "fun" club.
No matter how much I wish for ASL's A.2 (*) and its footnote (**), I'll settle for 10C3.
(*) Please note that the Laws of Duplicate Bridge could fit quite comfortably in *the index* for Advanced Squad Leader. Having said that:
A.2 ERRORS: said:
All results stand once play has progressed past the point of commission. In other words, if an error is discovered after play has progressed that point, the game cannot be backed up to correct the error, even if such error is in violation of a rule..."
(**)
A.2 Footnote, my emphasis said:
to the unscrupulous, these mechanics for handling errors might be viewed as a license to steal. We do not mean to intimate that cheating is acceptable behaviour; rather, that backing up a game to accommodate a forgotten rule/unit is a drag on play. In essence, the player's knowledge of the system and methodical application of its benefits as opportunities present themselves becomes an added skill factor better reflecting the abilities of an experienced battlefield commander. Ultimately, the only protection against a cheater is not to play them.
When I go to sea, don't fear for me, Fear For The Storm -- Birdie and the Swansong (tSCoSI)