You should not take my word for any of this, and you do not have to. Every position I hold is published and dated where anyone can audit it.
Start With The Dictionary #
Hundreds of terms in the Knowledge Base, each one defined in the same nine sections: what it is, how the mechanism works, what it is not, the tests you can run to detect it, where it sits in the framework, what it connects to, why it matters, what changes in how you operate, and what you do tomorrow.
Read the diagnostic tests and run them against your own operation. If the mechanism is not there, the term is wrong and you should discard it. That is what the tests are for.
Check Whether I Have Held My Positions #
Everything is dated. Take any position I argue today and look for when I first took it, then look for whether I softened it when it became inconvenient. Consistency over time is the only credential in advisory work that cannot be manufactured, which is exactly why so little of the industry’s counsel is auditable at all.
Read The Two Registers Against Each Other #
Restaurant Physics teaches the architecture. Hacksterism prosecutes the arbitrage. They are the same framework pointed in opposite directions, and if the positive case and the prosecution ever contradict each other, one of them is wrong and you should say so.
Then Test It On Your Own Operation #
Take The Operator’s Assessment, read what it points you at, run one piece of the work against one real gap. That is a cleaner test of whether my framework holds than anything I could tell you about myself.
And Argue With Me #
If you think a position is wrong, bring it. I would rather defend an argument in front of an operator who disagrees than collect agreement from people who have not read the work. Let’s Talk.
