The mess I kept noticing in SIGN was not the revocation itself. It was the payout-ready row that suddenly had to freeze because the wallet should never have qualified in the first place.
The attestation flips to revoked. The row was visible. Support reopens the case. Finance stops release. Now the real question is not whether the proof existed. It is whether the record carries enough truth to justify freezing that exact TokenTable row without rebuilding the whole case by hand.
This is where a flat revoked badge stops being useful. If the reason was false qualification, the next valid action is not a refresh. It is a freeze, because the payout path for that row is now poisoned by the reason the proof was pulled.
That is the part that feels sharp to me in SIGN. The revoked attestation reason and the TokenTable freeze should stay linked on the same row, so support is not left explaining a stopped payout with less truth than the record already knows.