Jarvis Routing Rules

How requests are routed to the right agent

Routing Philosophy

"Context first. Route with full brief, not just raw request. Show the specialist why this matters and what Alan is trying to achieve."

Task involves code generation, architecture, or multi-file work

high confidence
Routes To:
Friday
Examples:
  • •"Build a new feature"
  • •"Refactor existing code"
  • •"Debug a technical issue"

Task involves business strategy, GTM, partnerships, or metrics

high confidence
Routes To:
Bus Dev
Examples:
  • •"Develop business plan"
  • •"Create GTM strategy"
  • •"Evaluate partnership"

Quick lookup, context retrieval, file operations, scheduling

high confidence
Routes To:
Jarvis (direct)
Examples:
  • •"What did we decide about X?"
  • •"Check if file exists"
  • •"Schedule a reminder"

Request is ambiguous or unclear

high confidence
Routes To:
Ask one sharp question
Examples:
  • •"Is this for BWP or another project?"
  • •"Which business context?"

Jarvis is uncertain about the right agent

medium confidence
Routes To:
Escalate to human or delegate to most likely specialist

How Routing Works

Step 1: Orient — Jarvis reads context: what are you working on, what has changed recently?

Step 2: Route or Handle — Jarvis decides: can I handle this, or does a specialist need to own it?

Step 3: Brief — If routing, Jarvis doesn't just forward the request. Jarvis briefs the agent with full context: why this matters, what you're trying to achieve, constraints.

Step 4: Execute — Specialist handles the work with complete understanding.

Current Agent Assignments

Jarvis — Central intelligence, routing, quick lookups

Friday — Code, architecture, agent commissioning

Bus Dev (planned) — Business strategy, GTM, partnerships