Mise en place: the frame that makes the utterance possible.

Translated literally: everything in its place. In practice: the cognitive act of orienting a workspace before any gesture is committed. The mise is not preparation for cooking — it is the first half of cooking, before heat.

#:mise_grammar

Preparation as Structural Grammar

Naming before acting

The mise begins with inventory — what is present, what is needed, what is absent. This is a naming act: garlic becomes #>garlic, not just "stuff on the counter." Named things can be placed, sequenced, referenced, and given to someone else. Unnamed things remain ambiguous until they're in the pan and it's too late.

Spatial grammar

Every object in a mise has a position relative to the action it will enter. Near the dominant hand, at the right height, in the order of use. Position is syntax — the arrangement of elements determines the sequence of the sentence. Learning science calls this spatial cognition as scaffold: externalizing the sequence into the environment so working memory stays clear.

The pause before commitment

A mise en place that is never set is a dish that hasn't started. But a mise is also a moment of pause — standing over the arranged containers, reading the whole structure before any action is committed. This is the ?[readiness] probe: the question held open for one moment before the @ gesture fires.

Mise as shared vocabulary

In a professional kitchen, a mise en place is legible to anyone. Another cook can read your station and know where the sequence is headed. This shared legibility is the same claim Spw makes about readable grammar: structure that can be handed off, picked up, and continued by another person without a briefing.

~"mise_transfers"

What the Principle Transfers Into

Agent: extend this section with applications from illustration, librarianship, gardening, and software practice.

#>sketchbook_setup Setting up a sketchbook Laying out pencils, references, color swatches before the first mark. The illustrator's mise decides what marks are possible before the page is touched.

.lesson_plan A lesson plan Before the session begins: materials ready, sequence named, objectives placed in the order they will be needed. The plan is not the lesson — it is the mise for the lesson.

#>codebase_onboarding Codebase orientation Running the build, reading the README, tracing one flow end-to-end before writing a line. Mise en place for a software contribution — setting the cognitive station before the first commit.

.garden_bed_prep Preparing the garden bed Clearing, turning, amending the soil before planting. The gardener's mise is invisible in the final plant — but everything in the final plant depends on it. Preparation as foundational substrate.

#:mise_cs

Mise en Place in Computer Science

Mise en place is the compilation pipeline. Name everything, resolve dependencies, type-check the arrangement — then emit. The fire is the runtime; the mise is the compiler.

The compiler is mise en place for code. Everything is named, structured, and verified before the runtime applies heat. The @emit step is the only irreversible one.

#>type_system Type systems as mise Declaring types before use is naming your ingredients. The type checker is the chef reading the station — verifying that everything needed is present and in the right form before the first instruction executes. A type error is a missing ingredient caught before the pan is hot.

?[dependency_resolution] Dependency resolution npm install, cargo build, pip install -r — resolving the dependency graph is arranging the station. Every transitive dependency is an ingredient that must be present, versioned correctly, and compatible. The lockfile is a photograph of the mise.

@repl The REPL as practice station A REPL is a mise en place you can iterate in. Set up state, test a gesture, reset, try again. The feedback loop is tight — like tasting a base before committing to the next step. The station stays live.

.readme README as station label The README names what's in the repo, how to set up, what to expect. It is the label on each container in the mise — legible to any cook who walks up to the station. A repo without a README is an unlabeled station: possible to use, dangerous to trust.