Mise · Engineering Reference
20 cases stepped through the current build, the three findings, the Chomp base punch list, and the other four personas ranked by added work.
The user flows · X-ray, per kitchen Five Kitchens, Walked ThroughEach persona stepped through the product frame by frame — what they see on top, the engine and ledger underneath.
Session doc · for the ledger kickoff From Five Kitchens to One ContractThe ledger schema derived end-user-first: five real kitchens and their journeys, then the fields they force, the decisions to make, and the eight fixtures to freeze.
Blind test set · for Edith Recipe Tests — Chomp DonutsFive real recipes to cost in the app, with staged instructions and a results template. Blind — correct costs held separately.
The UX flow · x-ray storyboard One Recipe, X-Ray View — six frames, two layers, one tomatoThe chef's screen and the engine underneath, frame by frame: capture → silent costing → verify → skip path → memory → living answer → live tracking.
The roadmap System Structure & Build PathThe whole architecture at a glance — two clocks, the blend wall, and the gated build phases with proof gates.
The working reference · updated Jul 13 Engine Cheat Sheet — How We Build It & What the Data Taught UsComponent-by-component attack plan, the pricing philosophy (why our data, when the web), the matching waterfall, fleet numbers, and the 16-amendment index.
Testing methodology Conversion Testing PlaybookThe LLM chef-simulator harness: five verification layers, the silent-assumption metric, triage buckets.
Source of record · 16 items Playbook Amendments (markdown)Every verified schema trap: the trap → the evidence → the exact rule. Fold into MISE_ENGINE_PLAYBOOK.md §9.
Design-partner recipes · ground truth Chomp Donuts — Recipes & Costing ReferenceJeff's design-partner kitchen: real recipes, MarginEdge costing as ground truth, the Salted Caramel Donut crown-jewel demo, and the edge cases mapped to the X-ray flow.
Engineering brief · the mission Mise Engineering Starter BriefThe one-paragraph mission, the two laws, the build order, and the legacy porting rules that corrupt everything downstream if wrong.