Best practice question--Protecting auto-loaded Rev stack

[Mark Powell]

I am using the so-called altSplash architecture (standalone executable
that loads an un-compiled rev stack) and have a basic best-practices
question:  What is the best way to protect the rev stack?  

Stack A:  Loader stack (compiled standalone)
Stack B:  Main stack (uncompiled Rev stack)
Stack B2: Substack of Stack B

If I set the password of Stack B and B2 to "foo", then what do I need to
do in the standalone A so that Stack B functions, but without Stack B's
scripts being viewable by someone with the Rev IDE installed?  Or is it
a foregone conclusion that the architecture presumes the Rev stack to be
open source?

Thnaks

Mark