SDK recipes

These recipes turn the SDK namespaces into complete applications: a bounded extraction, an assistant that waits for events, a research pipeline, a human approval step, and application-owned memory.

| Recipe | Use it when | It ends with | |---|---|---| | Typed extraction | You need one structured answer and no follow-up. | A typed object or an explicit failure. | | Event-driven assistant | Events arrive over time from a webhook, queue, or watcher. | A resident node that wakes for each event. | | Fan-out pipeline | One task needs independent research before a synthesis. | An orchestrator's final report. | | Human approval | A person must decide before work continues. | A node resumed by an inbox answer. | | Application memory | Several runs need the same durable application knowledge. | A profile-owned document read by a scoped run. |

Start with typed extraction for a request/response job. Use a resident node when the same assistant should react again later. Use an orchestrator only when child work can proceed independently; otherwise keep the composition in your application.