Protecting your build in public workflow without giving away the blueprint

There is a fine line between getting honest feedback early on and over-sharing to the point where someone else runs off with your pitch.

Stealing a feature list is easy, but copying the actual vision and execution is a completely different story. Still, it hurts when a partner or contact breaks trust. I've realized that putting proper paper trails in place and documenting development dates matters way more than non disclosure agreements.

How do you decide who gets to see the inner workings of your roadmap during early stage talks?