Section 8: The Kitchen Doesn't Lie - Deep Dive: Inventory, the 86 Board & the Lunch Rush

Executive Summary: This section opens the two boxes where this system touches physical reality. First, inventory: we defend modeling it as a human-grade binary toggle — the 86 board (D8) — against the seductive false precision of a per-gram ledger, and we build the cascade (D7) that takes Marco's one tap to five hundred phones in under thirty seconds, including the apology-and-substitute flow for the customer caught mid-checkout. Second, the lunch rush: we turn Section 3's queueing arithmetic into a promise engine (D10) — quoted pickup computed from queue depth and station throughput, intake throttled honestly past a cap — and we name the metric that makes honesty operable: promise accuracy at p90.

Section 7 ended inside the pricing transaction. The interviewer now points at the two sentences everyone waves past: "You keep saying 'availability check' and 'quoted pickup.' Where do those numbers come from? Show me the inventory system." The Staff answer begins with a confession: there is no inventory system — on purpose.

Part One: The 86 Board, or Inventory at the Kitchen's Precision

The reflexive design is a depletion ledger: every recipe carries ingredient quantities, every order decrements them — 140 grams of romaine here, 80 grams of avocado there — and availability falls out of arithmetic. It demos beautifully. It is also fiction by 10:30 a.m. Kitchens portion by eye and by scoop; a prep cook drops a container; a batch of avocados arrives half bruised; someone comps a salad off the books. Each event nudges the ledger away from the walk-in's reality, and the errors compound in one direction only: confidently wrong. A gram-ledger that has drifted doesn't say "I'm unsure" — it authorizes selling avocado that doesn't exist, or 86's avocado that does. False precision is worse than no precision, because it lies with authority (D8).

The kitchen already has a working inventory protocol, refined over a century: when something runs out, the lead shouts "86 avocado!" and everyone stops selling it. Our design digitizes exactly that and nothing more. The 86 board on Marco's tablet is a list of ingredients with binary toggles — available or 86'd — plus two deliberate garnishes:

• Optional low-stock nudges. A "running low" state that warns staff without changing what customers see. It costs one enum value and buys the kitchen lead a glance-ahead; it never pretends to be a count.
• An audit trail. Every toggle records who, what, and when — changed_by, changed_at in the availability table from Section 5. Three to five events a day per location sounds like nothing, but across a year it becomes operations analytics the gram-ledger could never honestly deliver: what do we run out of on Tuesdays, and at what hour? The answer re-sizes Monday's produce order. The humble toggle, audited, is a demand-sensing instrument.

Flip trigger, stated before the interviewer asks: where counts are physically true — bottled drinks, grab-and-go boxes, the 20 catering slots — counted inventory is correct, and D8 flips. Model each inventory at the precision the world actually maintains.

Quick check before moving on: