Skip to main content
Pick the surface by what the user is trying to do, then run the tool sequence for that intent. When two surfaces could answer, prefer the one that holds the actual answer — numbers live in Data, durable truth lives in Knowledge.

​
Intent → tool sequence

Never answer a numeric operational question (how many, how much, current stock, this month’s sales) from Knowledge when Data exists. Knowledge holds policy and prose; Data holds the live records and numbers. Route counts and amounts to data_query.
For Knowledge, read the full content with knowledge_get before you decide — don’t answer on the search-result intro alone. The intro is a snippet; the governing detail is usually in the body.
For market intelligence, use the Vertical tools rather than generic web search — they return grounded, brand-specific signals with coverage you can check. See the Vertical Playbook.

​
Concrete questions

Natural asks mapped to the sequence that answers them:
The discovery step is not optional. “Find a product” starts with data_view_list because you need the real view slug and column names before data_query — the same holds for agents (departments, skills, grants), missions (IDs), and vertical (resolve the brand). See Discover before guessing.
Deeper routing for the two orchestration surfaces:

Mission Recipes

Explain, start, diagnose, control, edit, and compare missions.

Vertical Playbook

Ground market answers in retrieved, brand-specific signals.