an illustrated analogy
Chez Monowai.
Platform engineering on a plate - contracts, pipelines, menus and mise en place. The whole delivery architecture, told through one kitchen.
Monowai · Engineering Advisory
the cast
Every kitchen role has a platform twin
The chef
= the architect - designs the kitchen, mentors the brigade
Ingredients
= solution components - sourced, versioned, shared
Recipes
= contracts - agreed before anyone cooks
The menu
= Helm charts - everything the kitchen can prepare
The pass
= the pipeline - nothing leaves unchecked
Tables
= environments - they order, the kitchen serves
The docket
= release evidence - every plate accounted for
Diners
= your users - they only ever taste the result
Keep the mapping in mind - everything that follows is true of both.
the corporate default
The kitchen most organisations run
No recipes
Every cook makes the dish from memory. Same order, different plate - depending on who's on shift.
No menu
Every order is bespoke. The kitchen negotiates each dish from scratch, table by table.
No pass
Plates go straight from stove to table. Complaints are the quality process.
Diners at the stove
Whoever shouts loudest pushes their dish out - no one ordered it, and it was never written down.
Sound familiar? Swap plates for releases - this is how most enterprises ship software.
the chef - the architect
A chef who cooks and serves every plate is the bottleneck
Designs the kitchen
Lays out the stations, the flow, the standards - so the brigade can work in parallel without collisions.
Writes the recipes
Agrees the dish before service, with the people who'll cook it - then the recipe carries the authority, not the chef.
Mentors the brigade
Tastes, corrects, teaches. Hands-on by default - but the measure of success is a kitchen that runs without him.
The chef's product isn't the plate - it's the kitchen.
ingredients - solution components
One stock, many dishes
The private stash
- Every cook hoards their own butter and stock
- No one knows what's fresh or whose is newest
- The same sauce made five ways, five times
The shared larder
- Sourced once, labelled, dated - versioned
- Every station draws from the same shelf
- One stock feeds many dishes - don't repeat yourself
Components are ingredients: shared, versioned, and prepared once - not re-derived at every station.
recipes - contracts
The recipe is agreed before anyone cooks
Written first
Dish designed on paper before the pan heats - the contract exists before the implementation.
Spec the plate, not the pan
The plating spec is the contract - what must leave the pass. The recipe is a reference implementation: one kitchen's way of getting there.
Anyone can cook it
Junior, senior, human or machine - every plate is judged at the pass against the same spec. Tech-agnostic, deterministic.
A dish that only one cook can make isn't a recipe - it's tribal knowledge with garnish.
the tasting plate - stubs
Everyone builds against the sample
Cooked once, early
During menu development the dish is plated once, from the recipe's example data - long before the kitchen can make it at volume.
Front-of-house starts now
Menus printed, wine paired, staff trained to describe it - every consumer integrates in parallel, against the sample.
Swap, not integrate
When service starts, the real dish replaces the tasting plate. Nothing front-of-house prepared has to change.
Agreement before we cook - the stub is everyone else's head start.
the menu - helm charts
Everything the kitchen can prepare
Menu
version 2026.4 - evidenced
A catalogue, not a promise
If it's on the menu, the kitchen can reproduce it - on demand, identically, tonight.
Versioned like the seasons
The menu changes deliberately: printed, dated, evidenced. Never scribbled over mid-service.
Off-menu means no
No snowflake dishes assembled at the table. If it should exist, it gets a recipe and a menu line first.
tables - environments
Tables order the set menu - by edition
table
Dev
menu 2026.4
table
SIT
menu 2026.3
table
QA
menu 2026.3
table
UAT
menu 2026.2
table
Production
menu 2026.1
the newest edition is tasted in Dev · Production dines on the proven one
The set menu, not à la carte
A table orders an edition of the whole menu - the system promoted as one versioned unit, never dish by dish.
Any edition, on request
Earlier editions stay orderable - a rollback is just ordering last season's menu. Pull, not push; no one force-feeds a diner.
The table card - overrides.yaml
Per-table substitutions - portions, allergies - pinned as an environment's overrides.yaml against the same versioned charts. Preferences vary; the kitchen never forks.
the pass - the pipeline
Nothing leaves the kitchen unchecked
Cooked
the change is built - the dish is plated
Checked
held against the recipe - verified against the contract
Docketed
evidence attached - tests, scans, release notes
Served
released to the table that ordered it
A bad plate goes back at the pass - before the diner ever tastes it. That's a breaking change failing the build.
mise en place - clean code & tdd
Great service is won before service starts
Mise en place - clean code
- A place for everything, everything in its place
- Labelled, trimmed, ready - the next cook can step in mid-shift
- Clean as you go - the station never degrades into chaos
Taste as you cook - TDD
- Don't let the critic review a bad dish - taste it yourself, first
- Season, taste, adjust: red, green, refactor
- A dish tasted throughout can't surprise you at the pass
No kitchen survives service without these - no platform survives scale without them either.
a new dish - onboarding a product
You don't rebuild the kitchen for a new dish
Write the recipe
Agree the contract - ingredients, method, what the plate must look like at the pass.
Add it to the menu
A new versioned line in the chart. The kitchen can now reproduce it on demand.
Tables order it
Any environment can request it from day one. Config, not a construction project.
The kitchen absorbs the complexity once - so every new dish starts a step ahead.
expand on proof
Perfect one dish, then open the second site
One dish, done right
Start with a single troublesome order: recipe, menu line, pass, docket. Prove the whole flow on one plate.
The brigade takes over
The kitchen runs on recipes and stations now, not on the chef's presence. That's the handover.
Same playbook, next site
A second location doesn't reinvent the kitchen - it inherits the menu, the recipes, and the standards.
That's a platform: not a bigger kitchen - a repeatable one.
tonight's menu - the full argument
Each course, served as its own deck
dishes may be ordered in any sequence · all served from the same kitchen · the produce comes from the garden →
closing thought
A great restaurant isn't a chef who cooks everything.
It's a kitchen anyone can cook in - recipes agreed, stations clean, nothing past the pass unchecked.
Build that, and the food keeps its standard long after the chef has gone home. That's the platform.