I treat complexity as an enemy, so recently when I look at "data availability / ordering / finality," I focus on one main thread: how can your transaction be reconstructed by everyone, in what order is it recorded in the ledger, and when can we finally consider it irreversible? To put it simply, first you need to be able to lay the data on the table (otherwise you can't even reconcile the accounts), then someone is responsible for queuing (it's annoying if the queuers can cut in line or cause small tricks), and finally wait for the stamp to take effect (don't keep reversing it after a while).

Recently, the staking, shared security, and yield stacking mechanisms that are criticized as "nested dolls," I can also understand: stacking layers looks lively, but you have to ask, which layer is backing you? If the data isn't properly stored, the ordering is too opaque, and finality is too slow, then no matter how many "security endorsements" there are, it's like having three locks on the door but the keys are in someone else's hands... Anyway, when I evaluate projects, I first look at how clearly these underlying issues are addressed, and I set aside the flashy stuff for now.