One thing that occurs to me is that it isn't, as far as I know, really possible to obfuscate a deck and stop people from poking around at its innards. Since a .deck is basically just a text file it's not hard to open it up and look at code or indeed change it to "unlocked".
Obviously that's something they'd have to explicitly choose to do instead of stumbling upon by accident but it may be a consideration, depending on what you're doing.
Supplementing Millie's correct answer, I often like to use this version of the navigate event that I first saw in Internet-Janitor's Dex-Vex.
on navigate x do if !deck.locked send navigate[x] end end
With this version you can still use arrow keys in interact mode -- but only while the deck is unlocked. This can be useful while building and testing.
But when the deck is locked for publication the keyboard navigation is completely removed, exactly like in Millie's version.
