I had a very similar thought to this post. So similar in fact that I went ahead and wrote a kind of user guide for each CFAR's techniques (though it has changed a great deal even in the last 4 months since I finished writing). I also have never been to a CFAR workshop and drew on many of the same online sources that you have. It took about a month to compile of working in my spare time. My motivation for doing so was the cost of attending a workshop (financially and time costs) were simply too high for someone in my position overseas.
I've printed it and only use it personally. I've never shared it other than with one close friend. I'm concerned about you posting this now, for the same reasons that stopped me from sharing my compilation even though I could see a great deal of benefit in it.
My thoughts for not sharing it are,
CFAR has all of this material readily available likely in a much more comprehensive and accurate format. CFAR are altruists. Smart altruists. The lack of anything like this canon suggests that they don't think having this publicly available is a good idea. Not yet anyway. Even the workbook handed out at the workshops isn't available.
I highly value CFAR as an organisation. I want them to be highly funded and want as many people to attend their workshops as possible. It would upset me to learn that someone had read my compilation and not attended a workshop thinking they had gotten most of the value they could.
CFAR has all of this material readily available likely in a much more comprehensive and accurate format. CFAR are altruists. Smart altruists. The lack of anything like this canon suggests that they don't think having this publicly available is a good idea. Not yet anyway. Even the workbook handed out at the workshops isn't available.
Having it publicly available definitely has huge costs and tradeoffs. This is particularly true when you're worried about the processes you want to encourage getting stuck as a fixed doctrine - this is essentially why John Boyd preferred presentations over manuals when running his reform movement in the US military.
I have been thinking for a while that it would be useful if there was something similar to the Less Wrong Canon on Rationality for the CFAR material. Maybe, it could be called the 'CFAR Canon on Applied Rationality'. To start on this I have compiled a collection of descriptions for the CFAR techniques that I could find. I have separated the techniques into a few different sections. The sections and descriptions have mostly been written by me, with a lot of borrowing from other material, which means that they may not accurately reflect what CFAR actually teaches.
Please note that I have not attended any CFAR workshops, nor am I affiliated with CFAR in any way. My understanding of these techniques comes from CFAR videos, blogs and other websites which I have provided links to. If I have missed any important techniques or if my understanding of any of the techniques is incorrect or if you can provide links to the research that these techniques are based on, please let me know and I will update this post.
Warning:
Learning this material based solely on the descriptions written here may be unhelpful, arduous or even harmful. (See Duncan_Sabien's full comment for more information on this) It is because the material is very hard to learn correctly. Most of the techniques below involve in one way or another volitionally overriding your instinctual, intuitive or ingrained behaviours and thoughts. These are thoughts which not only often feel enticing and alluring, but that also often feel unmistakably right. If you are anything like me, then you should be very careful if you are trying to learn this material alone. For you will be prone to rationalization, taking shortcuts and making mistakes.
My recommendations for trying to learn this material are:
Sections:
Bugs
An important concept that is required to understand the CFAR material is the concept of 'bugs'. Bugs generally tend to be situations that involve a feeling of "stuckness" and often occur when your system one and two wants are out of alignment. Some concrete examples of bugs include:
CFAR would stress that 'bugs' are not things that should be accepted with resignation. They are instead things that should be worked through and solved. They are problems that deserve your time, attention and courage to solve. Due to our human nature, it is often best to get the help of others when you are trying to solve your bugs as we tend to rationalize and justify our bugs.
In summary, the CFAR perspective on bugs seems to be that when you notice one you should think: “Okay! Here is an opportunity for me to get better at life. Where’s my pen and paper?" or "Where can I find someone to talk this through with".
Discovering bugs - the below techniques all deal, in one way or another, with improving your ability to be able to discover your bugs.
Things that are probably bugs and should be analysed - the below are not really techniques, but are instead descriptions of particular situations that frequently turn out to be bugs.
Analyzing bugs - these techniques are all about helping you to better understand what you actually value or find aversive
Improving the accuracy of your credence levels
Mindfulness of how your internal state is affecting how you perceive the world
Resolving Disagreements
Other stuff which has already been covered in LessWrong