[Syntax] Sensory checkpoints and validation criteria #11

New issue

Open

opened 2026-07-17 23:14:28 +02:00 by abiwab · 0 comments

abiwab commented

2026-07-17 23:14:28 +02:00

(Migrated from codeberg.org)

Context

Time is often an unreliable metric in cooking. Visual or textural cues are much more accurate.

Goal

Add a syntax to define target output states (e.g., Whisk until ={ribbon stage}.). The output state becomes structured data within the AST.

Benefits

Better UX: gram cook can display these criteria prominently as step validation conditions.
Accessibility: It helps beginners focus on what to look for rather than strictly following a timer.
Data Structuring: It provides richer metadata for alternative UIs or specialized cooking interfaces.

### Open question

The syntax must still be discussed, as = is already used for ingredients declared with static quantity @=ingredient, can be confusing.

### Context Time is often an unreliable metric in cooking. Visual or textural cues are much more accurate. ### Goal Add a syntax to define target output states (e.g., `Whisk until ={ribbon stage}.`). The output state becomes structured data within the AST. ### Benefits - **Better UX:** `gram cook` can display these criteria prominently as step validation conditions. - **Accessibility:** It helps beginners focus on *what* to look for rather than strictly following a timer. - **Data Structuring:** It provides richer metadata for alternative UIs or specialized cooking interfaces. ### Open question - The syntax must still be discussed, as `=` is already used for ingredients declared with static quantity `@=ingredient`, can be confusing.