The principle assumes there is an operator. Someone whose engineered intent or absence of intent produces the outcomes. In a single-owner-operator restaurant, that is clean. One person makes the calls, holds the accountability, and either designs or defaults on the dimensions of the operation.

Most restaurants are not single-owner-operator. Most have multiple decision-makers: owners and general managers, kitchen managers who are also owners and business partners, franchise structures with corporate and franchisee decision layers, family enterprises with several generations involved, investor groups with GMs on the ground. When multiple actors have decision-making authority, the principle needs to be applied at the level of the restaurant as a unit, not the level of any individual actor.

This produces four states rather than two. Design and default still exist, but in the multi-actor case, they take on specific forms.

The first state is single-operator design. One accountable actor makes the design decisions, builds the conditions, maintains them. Outcomes trace cleanly to that operator’s design. This is the simple case, and the principle operates on it as originally stated.

The second state is collective design. Multiple accountable actors align on the design. They have shared decisions, shared conditions, shared maintenance. The alignment itself is the design work — because when multiple decision-makers hold different visions, no single vision produces the outcomes cleanly, and the operation defaults into whatever the interaction of their partial visions happens to produce. Collective design requires the ownership-layer discipline of arriving at a shared vision, agreeing on the built conditions that support it, and maintaining that alignment as pressures come.

When collective design is running, outcomes trace to the alignment. The restaurant looks and feels like it has an operator, even though the operator is a group. The Guest, the cast, the market cannot see the multiple owners — they experience the operation as a single designed thing. This is the mature form of multi-owner design, and it is achievable, but it requires more work than single-operator design because the alignment itself is a dimension that has to be designed against continuously.

The third state is single-operator default. The single operator did not design a specific dimension. Default runs on that dimension. Outcomes trace to the operator’s absence of intent. This is default in its original form.

The fourth state is structural default. Multiple actors are involved, but no accountable actor owns the outcomes of the restaurant as a whole. The GM owns operations. The kitchen manager owns the kitchen. The owner owns the capital. The investor owns the financing terms. But nobody owns the restaurant. Every gap between them defaults. Every conflict between their partial designs defaults into whatever interaction their partial designs happen to produce.

Structural default is not the same as single-operator default. It has a specific mechanism: the mechanism of unclaimed accountability at the level of the whole operation. Each individual actor may be designing intensely on their piece. But no one is designing on the whole. And the whole produces the outcomes the Guest experiences, the cast lives inside, and the P&L records. When no one is accountable for the whole, the whole defaults, even if every piece is designed.

Structural default is where most multi-owner restaurants fail. It is not that the owners lack skill or effort. It is that the ownership structure has no one accountable for the whole restaurant’s outcomes. The pieces run well individually. The whole drifts.

The diagnostic for structural default is a specific question: Who is accountable for whether this restaurant, as a whole, is running by design or by default? If no one can honestly answer that question, structural default is running.

Fixing structural default is not primarily an operating fix. It is an ownership-structure fix. Either one accountable actor has to be named and empowered to design the whole (with clear authority to override the partial designs when they conflict), or a governance structure has to be built that produces alignment at the level of the whole (regular decision cadences, shared vision documents, agreed accountability metrics, dispute resolution mechanisms). Without one of these two, structural default keeps running regardless of how hard the individual actors work on their pieces.

This also resolves the objection that the principle is culturally bound to individualist American operators. Restaurants in family-enterprise cultures, community-owned models, cooperative structures, and inherited partnerships all fall under the principle at the level of the restaurant. The specific form of design or default varies by cultural structure — an extended-family restaurant can produce collective design through family cohesion, or structural default through family conflict, and the mechanism is different in each case. But the outcome is still design or default, and the principle governs it.

What the principle requires is that some accountable structure exist. It does not require that the structure be a single individual. It does not require American individualist framing. It requires only that when outcomes emerge from the restaurant, some accountable entity — one person, a group, a family, a cooperative — can trace those outcomes back to their design or their default. When no such tracing is possible, structural default is running, and the outcomes reflect that.

The multi-actor complications do not weaken the principle. They add precision to how it operates in the real conditions most restaurants inhabit. Four states, not two. Design and default still governing. Just at the appropriate level of who is holding accountability for what.

The operator working inside a multi-actor structure has one additional design task beyond the ones a single-operator operator has: designing the accountability structure itself. Not just the outcomes of the operation, but who owns those outcomes. That accountability design is itself subject to the principle. It can be designed cleanly or defaulted on. And whichever mode is running on the accountability layer produces whichever mode is available on the operational layer beneath it.

The principle is the principle. The number of actors changes what design and default look like in practice. It does not change what causes the outcomes.