The Summers Principle is stated. Its extensions are stated. Its boundaries are named. The operator has read F0 through and either accepts the principle or does not. The question at this point is what the operator does next.

The answer is small and specific. Not a dramatic reorganization. Not a sweeping strategic overhaul. Not a promise to redesign the whole operation over the weekend. Something smaller and more sustainable.

Tomorrow morning, before opening, the operator picks one dimension of the operation and asks a single question about it: is this running by design or by default right now?

Pick a real dimension. Not the whole operation. Not Guest Experience as a concept. A specific dimension. The hiring criteria for hourly cast. The morning line check. The training checklist for new cast members. The daily food cost read. The Friday closing walk-through. The way the operator greets the cast at the start of a shift. One dimension. Small enough to actually see.

Then read it honestly. What is running on that dimension right now? Is there engineered intent behind the current state — a decision made, a condition built, maintenance happening — or is what is running whatever fell into place in the absence of the operator’s engineered intent?

Most operators, running this exercise honestly, find that they are defaulting on more dimensions than they thought. Not because they are lazy or unskilled. Because dimensions accumulate faster than any operator’s design capacity, and dimensions that have not been actively designed against are being defaulted on by definition. That is not shameful. It is the causal state.

Having identified one defaulted dimension, the operator makes the smallest possible design move against it. Not a rebuild. A first step. Write down what the outcome on this dimension should be. Identify one condition that would produce that outcome. Commit to installing that condition this week. Maintain it for the next month. Then read the outcome.

That is running the principle. One dimension. One design move. One month. Then read.

At the end of the month, the operator can see whether the design produced the outcome they engineered toward. If it did, they extend the design — deepen the condition, expand the coverage, connect it to related dimensions. If it did not, they diagnose the failure — was the condition inadequate, did maintenance lapse, was the decision wrong about what outcome was worth designing for. Either way, the operator learns something about how design operates in their specific operation, at their current capacity.

Repeat. Next month, pick another dimension. Same process. One at a time. Building design where default was running. Shifting the ratio.

Over a year, this practice produces a fundamentally different operation than the one that existed twelve months earlier. Not because the operator did anything dramatic. Because they did small, disciplined, repeated design work across dimension after dimension, building the operation from defaulted to designed one layer at a time.

This is how the principle becomes operating practice rather than concept. Not through revelation. Through discipline. Small, specific, repeated design moves, over enough time that the ratio of design to default shifts across the operation, and the outcomes shift accordingly.

The platform exists to support this practice. Every book in the shop is design work at a specific layer. Every 411 is design work on a specific problem. Every workshop is design work in collision with peers. Every Review is diagnostic work on where design and default are currently running. Every mentoring engagement is design work on the operator’s capacity to design. The platform is not a body of knowledge to consume. The platform is a set of tools for running the principle in a specific operation.

Which tools the operator uses depends on where they are in their arc, what layers they are ready to design against next, what capacity they have available to expand. The tools are available. What matters is that the operator uses them for the actual work — designing on real dimensions, in a real operation, over real time — rather than treating them as concepts to think about.

The principle is not complicated. It is one sentence. Every operating outcome exists due to one of two causes: design, or default. What is difficult is the discipline of running the principle across an operation that has hundreds of dimensions, at whatever capacity the operator currently occupies, over enough time for the outcomes to compound.

That difficulty is the operator’s work. It is what the whole framework — F0 through F5, the Dictionary, the Reads, the Ops Toolkit, the Reviews, the mentoring — exists to support. And it is what separates the operator who runs a restaurant from the operator who is being run by one.

Tomorrow morning. One dimension. One design move. One month. Then read.

That is where it starts. Every operator who has ever built a restaurant by design started with a single dimension they decided to design against. Everything else compounded from there.

The principle is the law. The Read is the discipline. The platform is the toolkit. The operator is the one who runs all three, in their operation, starting now.