Skip to content

Expertise: Teach the Robot the Job

Expertise answers the practical question: how does the robot actually do the job? Once the robot can converse reliably, use this area to add knowledge, workflow logic, role strategy, and environment context so it can complete one real task.

Expertise category: documents, scripts, role, flows, and scenes
Expertise overview: Knowledge and Behavior modules

Start with one minimum viable workflow

Pick one real task first, for example:

  • greet visitors and answer common questions
  • patrol a fixed route and report anomalies
  • escort a guest from the front desk to a meeting room

Once the task is explicit, decide which assets are needed. Do not work backwards by filling every page in the product.

Minimum viable setup

CapabilityWhen you need itPurpose
Knowledge documentsThe robot must answer from source materialProvide RAG content
Scripts / roleThe service flow must stay consistentStandardize behavior and wording
FlowsReactions must follow explicit triggersChain actions into one workflow
ScenesThe robot moves or depends on spatial contextManage maps, routes, and zones
  1. Define the target job, success criteria, and hard boundaries
  2. Add the minimum knowledge, scripts, or role setup needed to answer correctly
  3. Add flows only if the job needs explicit trigger-based behavior
  4. Bind scenes, routes, and zones if the robot moves in the environment

Validation before handoff

  • Ask 5 frequent user questions and check the knowledge hit quality
  • Run one full business flow and confirm the robot does not skip steps
  • If movement is involved, test one start-to-finish navigation path
  • If behavior is unstable, narrow the task before adding more configuration

Boundary with Intelligence

  • Intelligence: model, persona, perception, memory, voice, expressions, actions — who he is
  • Expertise: knowledge, scripts, role, flows, scenes — what he does