Start here. Before you enter the fundamentals, you need to know what this work is, who wrote it, who it is for, and what it is arguing against.

Every operating outcome in a restaurant — every Guest kept or lost, every cast member who stays or leaves, every dollar earned or extracted — exists due to one of two causes: design, or default.

The read discipline. How the operator sees the operation before deciding anything else.

The built Guest Experience. Every touchpoint, every interaction, every element of what the operation actually delivers.

The Lead Family and the cast. How the operator builds the team that carries the standard.

The internal operator disciplines. Systems, standards, and the work that produces consistent output shift after shift.

Pricing, measurement, and value capture. How the operation converts what it builds into what it keeps.

The locked vocabulary. Every bracketed IP term with its canonical definition and the position it holds inside the framework.

The framework explaining why things happen the way they do. Operator situations, industry shifts, market pressures — named, read, understood.

The applied instruments. Forms, templates, worksheets, and diagnostics operators use to do the work the framework names. Where the reading turns into opportunities.