this is essentially why John Boyd preferred presentations over manuals when running his reform movement in the US military.

It's strange that you mention John Boyd because, to be honest, I was thinking of him when I decided to post the material. I don’t believe that John’s preference for presentations over documentation was a good one. In general, I oppose obscurity and restriction of information although there are times that I don’t, e.g. when it’s from a lack of resources or an extremely short material turnover rate etc. In regards, to John Boyd’s stuff, personally, I know that I had to waste a lot of time wading through a lot of simplistic and pretty useless information (pretty much just the simple OODA loop stuff) to understand his material. I believe that this is his only published paper. Also, it was only really the Osinga thesis which has allowed me to understand his ideas. Although, I do need to go over it again.

This is particularly true when you're worried about the processes you want to encourage getting stuck as a fixed doctrine

Wouldn’t most of these issues would be avoided if you gave some warning that the material is in flux and versioned it as well. So, you had a CFAR material version 1, version 2 etc. Also, doesn’t it seem a bit weird to give the potential of the information becoming a doctrine enough weight that it causes the restriction of this information? It seems weird to me since the skills that CFAR and Boyd are/were trying to teach are in large part about breaking out of fixed doctrines. It’s kind of like stopping someone from learning martial arts because you don’t want them to get hurt while training.