The original manifesto is a litany of aphorisms and position statements with little or no practical utility, and what to me appears to be a bias for what is essentially spec work at an agency.

I am glad we are on the same page.

The problem is that these don't translate well when we turn them into practical frameworks.

So how do we teach mindset?

The original manifesto makes the correct mindset super-obvious. It's very succinct and still relevant to today.

Just take the first line, "Individuals and interactions over processes and tools." Interesting how most "Agile (tm)" is just selling processes and tools and pushing people into cookie-cutter roles.

Even better is what I consider "line zero": "We are uncovering better ways of developing software by doing it and helping others do it," (emphasis mine). The lesson there being that the best people to teach you how to develop software are, in fact, developers (not managers, execs, consultants...).