Cookbooks

Each recipe supplies one complete request, a handling policy, and a failure case to evaluate. The requests are valid examples, not measured model outputs or universal business policies.

Start with a pinned model, your own labeled development cases, and a staffed fallback. Keep money movement, account permissions, policy eligibility, and irreversible actions in deterministic application code.

The recipes cover support triage, refund decisions, content moderation, lead routing, tool selection, and document classification. Thresholds illustrate the request format; validate yours against the risks of each workflow.

• Support triage: choose the owning queue.
• Refund decision: interpret intent after eligibility checks.
• Content moderation: judge against a stated policy.
• Lead routing: route expressed requirements.
• Tool selection: choose from an authorized allowlist.
• Document classification: label extracted text.