Mise · Engineering Reference
Current costing status, Gate A closeout, complete single-recipe ingestion, and the following batch and ChefTec work.
Pricing reference · zero-state benchmark · source rules Brigade — Zero-State Pricing SourcesThe reference pools, market-level separation, trigger cases, deterministic selection order, and vendor qualification test for benchmark recipe costing.
Integration strategy · Brigade to ChefTec · proposed pilot ChefBridge — One Recipe from Brigade to ChefTecThe first customer case, account authorization, reviewed recipe transfer, shared SQL Server mailbox, ChefTec import, read-back receipt, ownership, and pilot decisions.
System architecture · Brigade + AWS + ChefTec · working contract ChefBridge — Frontend to Customer SQL ServerThe complete technical path for account linking, recipe and invoice publishing, Brigade APIs and data stores, proposed AWS services, ChefTec import, and return receipts.
Product strategy · visual roadmap · proposed v2.1 Brigade / Mise — From Recipe Answer to Operating PartnerThe full 16-frame product sequence: trustworthy costing, seamless sellable-item composition, invoice grounding, reversible actions, simulations, sensory intelligence, conversational control, multi-location operations, R&D, and purchasing.
Product demo · illustrated recording handoff Ice Cream Shop R&D Demo PlaybookA new owner goes from a handwritten test batch to an honest benchmark, dollar-ranked refinement, ingredient X-ray, and a living launch menu. Includes current screenshots, proposed screens, and Edith’s recording script.
Coverage & roadmap What We Solve Today, and What's Next20 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.