Recipes begin with a job, not a constructor. Each one composes already-established Motive surfaces into a complete pattern while preserving the authority and failure boundaries taught by their canonical guides.
Compose after you understand
A durable order processor may combine child charts, weighted Resource capacity, retries, retained outcomes, and committed inspection. A local-first workflow may combine browser persistence, version identity, recovery, and synchronization. Those combinations are useful, but none creates a second meaning for the underlying API.
Every recipe should therefore name its prerequisites, show a complete runnable program, exercise the important failure direction, and link each consequential construct back to the guide that owns it.
Start from the job
Recipes are not a second language
The navigation categories remain the curriculum and the canonical explanation of Motive. Recipes may put several surfaces side by side, but they do not redefine transition semantics, engine guarantees, or operational authority for convenience.
If you are choosing one construct, return to its guide. If you already know the construct and need its exact symbol, continue to Reference.