The cookbook-page moment. Hero photo, Lora title, method set in Roman numerals. The Ingredients eyebrow reads INGREDIENTS · serves 4, with 'serves 4' typeset as an inline-link cross-reference (Lora italic Ochre, 1px ochre underline). The ochre halo marks it as the next tap.

↳ Tap serves 4

The dreamy moment. The page lightens under a cream wash and blurs behind, and the scale strip floats centered in the viewport — '— 2 · 4 · 6 · 8 · 12 —'. The current yield (4) sits currently-selected and larger, carrying the chapter-rule hairline beneath. The ochre halo lands on 8 as the next tap. No card, no border, no pill — the blur is the container. Scale is a lens over a fixed recipe; no Save.

↳ Tap 8

The page quietly rerendered at serves 8 — ingredient quantities and each method step's mise doubled. Step TEXT is unchanged; timing and pan cues are cook judgment, not math. The lens has done its work.

Long-press on a step opens an iOS-style context menu. The page blurs and dims; step iv is plucked above the dim layer with a soft shadow; a quiet two-row menu — Edit · Delete — floats below. This is the discoverability answer: there is no Edit button, long-press is the single entry point.

↳ Edit

Inline edit — step iv is swapped for a live textarea inside the recipe page, '8 minutes' updated to '10–12 minutes.' The page stays put so the cook keeps their bearings; the iOS keyboard is docked at the foot. Save commits the change; Cancel discards.

↳ Save

Same page, quietly updated. Step iv now reads '10–12 minutes.' No celebration, no banner — the book-spine test holds.

The onboarding moment. Notes live as a peer section to Ingredients and Method, placed BETWEEN meta and ingredients — reading order is author's voice → cook's voice → what you need → how to make it. The block is empty, so the section carries only the eyebrow and the typographic invitation '— add a note —' in italic Ochre, mirroring Flow III's 'When you're ready to make these into a book —' grammar. The halo lands on the invitation.

↳ Tap — add a note —

The invitation is replaced in place by an empty textarea, high in the body between meta and ingredients. No field border, hairline underline only — the voice is a cookbook margin, not a form. Cancel (tertiary Ash) · Save (Ochre) floats to the right under the textarea. iOS keyboard docks at the foot; the page auto-scrolls the textarea into the visible band above it. Save is halo'd as the handoff. Apple Notes grammar — the cook types whatever they want, no metadata imposed.

↳ Tap Save

The page quietly updated. The block now shows the cook's first voice — 'Halved the salt — nicer balance.' — as one Lora italic paragraph. No chrome, no date, no per-note affordance. Tap anywhere on the block to reopen the editor; the whole block is halo'd as the handoff. Weeks later, the cook returns to add more.

↳ Tap the note

The same editor surface as compose, now populated with the note's current text. Cook is about to add the memory-note — '— Sam's 30th. Doubled it. Everyone wanted seconds. —' — into the same block, flowing after the first voice. Same hairline underline, same Cancel/Save grammar. Save halo'd as the handoff. The block is one note that grows, not a list of notes.

↳ Tap Save

The close of the sub-flow. The block carries both voices in one continuous Lora italic body — the cook-note and the memory-note running together, no separation, no metadata between them. Apple Notes honest: one block, everything the cook wanted to remember. No halo — the sub-flow is done.

Starting state. Picks up where the Notes sub-flow left off — the global Notes block already carries both voices ('Halved the salt — nicer balance. — Sam's 30th. Doubled it. Everyone wanted seconds. —'). No line-item comments yet. The halo lands on step iv — long-press opens the step menu.

↳ Long-press step iv

The same three-row context menu the Edit sub-flow uses, now with Comment as the first row and halo'd as the tap target. Edit is secondary (rare — it changes the recipe body); Delete tertiary. The Edit sub-flow halos Edit via the same shared component; the halo is the storyboard's overlay, not a UI state. Discoverability through gesture, not chrome.

↳ Tap Comment

A textarea opens beneath step iv, indented under the step's text column so it's visually anchored to what it annotates. Cancel · Save in the now-familiar grammar. Save halo'd. iOS keyboard docked; page auto-scrolls the textarea into the visible band above it. Same editor voice as Notes, smaller register — a pencil in the margin, not a form field.

↳ Tap Save

Step iv now carries an inline comment — '10–12 minutes — thickens better.' — in Lora italic Ash, indented under the step text. No chrome, no date, no ceremony. The cook moves on to the ingredients: the halo lands on the butter line, where the same long-press gesture repeats at ingredient scope.

↳ Long-press butter

Same compose surface, this time beneath the butter line. Menu screen skipped — the long-press menu earlier in this sub-flow is the same menu for ingredients, and the binder doesn't need to teach it twice. Save halo'd.

↳ Tap Save

The close of the sub-flow. Global note at the top carries both voices. Step iv carries its own. The butter line carries a comment beneath it — 'Cultured if I have it.' Nothing destroyed — the recipe body still reads as it was imported. What's on the page now is the personalization layer: the comments are what make a recipe that came from somewhere else into hers. This is the content the printed book will carry beyond the bare recipe — the proof-of-authorship that a library of saved URLs can't give you.

The page-level menu — Apple Music's grammar at the recipe scope. Tap the ⋯ in the right nav and a small iOS-vibrancy popover drops from the trigger: View original ↗ (opens the source URL when one exists), Add to collection (stubbed; collections land later), Remove from library (vermillion, soft-delete). Unlike Flow I's long-press menu — a context menu on a specific step with a plucked-and-blurred backdrop — this is the page menu, so the backdrop only dims and the card anchors at the trigger.