SDK recipes

When composing crouter SDK namespaces into an application, read this because it helps you choose a complete runnable starting point.

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 documents.

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.
Apps on crouter cloud	Your app starts runs on a person's runtime and needs typed data back.	A validated result from `runs.parse`, or an explicit decline or `run_idle`.
Apps with many users	People interact using separate runtime connections.	App-owned access controls, attribution, and per-person spending.

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.