What a recipe is

A recipe is a named, ordered sequence of tools that completes one job end to end — a codified run of the mission loop. Recipes are how fOS turns "win me a backhaul" into a reliable series of steps rather than an improvised conversation.

What a recipe defines

Each recipe specifies:

• A trigger — the situation that calls for it (e.g. "user wants loads for a truck").
• Steps — the tools to run, in order, each with an intent (why this step) and a guard (when it applies).
• Optional steps — some steps run only in certain conditions (e.g. draft an email only on an email channel; schedule a follow-up only if the deal isn't already won or lost).
• Success criteria — what "done" looks like.

Because every tool a recipe references must exist in the contract registry, recipes can't drift out of sync with the real tools — an invalid recipe is caught before it ships.

Why recipes matter

Recipes give fOS three things a free-form chat can't guarantee:

1. Reliability — the same job runs the same way every time.
2. Grounding — each step is a real tool with real data, so the run never fabricates (Cost grounding).
3. Safety — guards and guardrails apply at each step, so money-moving actions still pause for confirmation.

The canonical recipes

Three golden workflows ship today, one per surface emphasis:

• Win a backhaul (web) — find a return load and offer on it.
• Match a vehicle to an offer (web) — from a free truck to a bid.
• Negotiate within the floor (voice) — a live rate call.

You rarely invoke a recipe by name — you state the goal, and fOS runs the matching workflow.