A design methodology for relocating resistance, so correct behavior becomes the easiest available behavior.
Read the essays →μ is the coefficient of friction. Inverting it does not remove the resistance. It relocates it.
Every system has friction. The question is where it sits. Put it in front of the correct action and people route around it, quietly, at scale, and you get drift, rework, and a standards document nobody reads.
Friction Inversion moves the resistance to the wrong side. The correct action becomes the default, the cheap one, the one that takes no thought. The incorrect action becomes the one that costs something: an extra step, a blocked export, a name the grammar cannot produce.
This is not automation and it is not enforcement. It is a decision about where difficulty belongs. Enforcement punishes people after the fact. Inversion makes the failure hard to reach in the first place.
I have been applying it since 2005 across DoD training systems, 3D production pipelines, design systems, and accessibility compliance. The essays below work it out in public.
An AI-native LCMS. Names are emitted from position in the course tree, so a wrong name is not something you have to remember not to type. It is something the system will not produce.
View the work →The lab where the tooling gets built: accessibility auditing, design-token pipelines, and production tools that make the compliant path the fast one.
Visit Cardona Lab →