Decoding Tradition with First Principles

First principles thinking is the practice of reasoning from underlying causes rather than inherited instructions. Instead of asking what is usually done, it asks what must be true. The goal is to understand the forces and constraints that make a system behave the way it does. Often the same forces that tradition learned to accommodate long before it could explain them..

I spent the summer of 1991 making bread in Paul Bunyan’s all-you-can-eat restaurant in Wisconsin Dells. The baker I worked with had made his Italian bread the way he had been taught growing up in New York. The process was traditional, passed down through practice rather than theory. We steamed the loaves because that was how it was done. Over time, I learned what the tradition had encoded: the moisture keeps the crust soft and pliable, allowing the loaf to fully expand before the crust sets.

He taught me to bake from his old hand-written recipe book. We stuck to the recipe and to his technique and it all worked out, we baked 200 loaves every morning. He was a great baker so things rarely went wrong, but left on my own the bread had a tendency to crack during the bake. There are many possible explanations, the oven was too hot, the dough was too dry, I hadn't followed the recipe closely enough. These answers all treat the recipe as the unit of analysis.

First principles thinking shifts attention away from the recipe and toward the underlying process. At a basic level, bread cracks because internal pressure exceeds the elasticity of the dough’s surface during rapid expansion. Heat causes gases to expand; the crust sets; something has to give. Seen this way, cracking is a physical consequence rather than a mistake. The problem reframes itself. The question moves from asking "what did I do wrong?" to asking "what caused the pressure build?"

This leads to practical insights. Steam delays crust formation. Hydration affects elasticity. Scoring the dough is a pressure-release mechanism as much as a decorative step. Each variable becomes intelligible rather than mysterious.

What matters here is the thinking model rather than the baking expertise. First principles thinking re-describes a situation in terms of forces, constraints, and outcomes. It replaces procedural dependence with causal understanding.

This kind of thinking scales beyond baking. Wherever people follow rules without understanding their origin, first principles thinking offers a way to regain agency, by seeing what tradition rests on.

------

[Logic Object: #TF-003-CAUSAL]

Conceptual Primitive

Causal Reverse-Engineering.

Core Tension

The opposition between Procedural Dependence (following inherited "recipes" or instructions without understanding) and First Principles Agency (reasoning from fundamental physical or logical forces to understand why a system behaves as it does).

Logic Constraints

• Tradition as Code: Inherited practices must be treated as "encoded solutions" to past material constraints, even if the current practitioners cannot articulate the underlying logic.

• Variable Intelligibility: A variable (e.g., steam, scoring) only becomes intelligible when its relationship to a fundamental force (e.g., pressure, elasticity) is mapped.

• Portability of Logic: Knowledge is only "portable" when it is stripped of its specific procedural context and re-described in terms of universal forces and constraints.

• Failure-Driven Inquiry: The "why" is most accessible at the point of system failure (the crack), where the inherited recipe no longer accommodates the underlying pressure.

Open Speculative Parameters

• How can an interface visualise the "invisible forces" (pressure, timing, resistance) that an inherited "recipe" or workflow is currently managing?

• What does a "First Principles" interface look like that doesn't just show the steps of a process, but the physical/logical consequences of adjusting any single variable?

• In a world of black-box AI "recipes," how can we build tools that allow a human to "crack" the output and see the underlying causal logic?

• How can we design environments that help users transition from "Procedural Trust" to "Causal Understanding" without discarding the valuable wisdom stored in traditional practice?

Cross-references

• Thinking Tools (First principles as the primary tool for individual agency).

• Thinking Structures (How traditions and "recipes" organise and hide knowledge).

• Speculative Surfaces (Creating interfaces that expose underlying forces rather than just procedural steps).