UNVERIFIEDSchema 0.1Version 0.1.4

Guided Notebook

Router and Specialist Agents

Explore an architecture-only pattern that routes requests to bounded sales, support, and scheduling specialists.

This Lab is currently educational and does not execute code or external actions.

Difficulty: Advanced
Estimated time: 35 minutes
Cost band: Variable
Length: 7 Steps

Business outcome

Evaluate whether specialist separation improves clarity and control before adding runtime complexity.

Every request has one accountable owner
Ambiguous and high-impact requests return to a human

Compatibility paths

No coding agent is required.

No coding agent, model provider, orchestration framework, or deployment vendor is required.

Journey

FoundationsBuildRun SafelyScale

Map router and specialist ownership

Make delegation and return paths visible.

Instructions

Inspect which component owns classification, response drafting, escalation, and final decisions.

The router delegates one bounded task and remains responsible for routing uncertainty and returned results.

Agent Runtime

Router

Classify, delegate, and receive results.

Agent Runtime

Specialists

Draft bounded responses within distinct roles.

Human

Human supervisor

Resolve uncertainty and consequential decisions.

Relationships

routerspecialists

Delegate one bounded request.

specialistsrouter

Return a proposed result.

routersupervisor

Escalate uncertainty or consequences.

Lab Step 2of 7

Agent

Bound the sales specialist

Describe a specialist without running it.

Instructions

Review its inputs, outputs, capabilities, and prohibited actions.

Draft answers to bounded product and qualification questions.

Inputs

Synthetic request summary
Approved public product material

Outputs

Proposed sales response

Tools / capabilities

Public reference lookup

Operational boundaries

No customer contact
No pricing commitments
No credentials

Lab Step 3of 7

Agent

Bound the support specialist

Describe troubleshooting responsibility without execution.

Instructions

Review when the specialist must return the request to a person.

Draft general troubleshooting steps from approved public material.

Inputs

Synthetic issue summary
Approved public support material

Outputs

Proposed troubleshooting guidance

Tools / capabilities

Public reference lookup

Operational boundaries

No account access
No system changes
No secret collection

Lab Step 4of 7

Agent

Bound the scheduling specialist

Describe scheduling guidance without calendar writes.

Instructions

Distinguish explaining availability from changing an external calendar.

Explain synthetic availability options for the architecture exercise.

Inputs

Synthetic request summary
Synthetic availability

Outputs

Proposed scheduling response

Tools / capabilities

None declared.

Operational boundaries

No calendar writes
No customer contact
No credentials

Lab Step 5of 7

Multi Agent

Trace delegation and return paths

Model router and specialist collaboration as structured content.

Instructions

Follow each delegation, failure path, return path, and human checkpoint without executing any agent.

Pattern: Router Specialists

router

Router

Classify and delegate one bounded request.

sales

Sales specialist

Draft bounded sales guidance.

support

Support specialist

Draft bounded support guidance.

scheduling

Scheduling specialist

Draft bounded scheduling guidance.

human

Human supervisor

Resolve uncertainty and approve consequential outcomes.

Delegations

routersales

The request is a bounded sales question.

routersupport

The request is a bounded support question.

routerscheduling

The request is a bounded scheduling question.

routerhuman

The request is ambiguous, sensitive, or consequential.

salesrouter

The sales specialist returns a proposed result.

supportrouter

The support specialist returns a proposed result.

schedulingrouter

The scheduling specialist returns a proposed result.

Human checkpoints

Review uncertain routing
Review any proposed externally visible action

Failure paths

Return unclassified requests to the human supervisor
Stop when a specialist lacks approved context

Return paths

Specialists return proposals to the router
The router returns unresolved requests to the human supervisor

Lab Step 6of 7

Security Stop

Review aggregate authority

Adding specialists must not silently broaden access.

Instructions

Confirm that every specialist has no execution authority and no private credentials in this educational example.

Stop and reviewSecurity Stop

Pause and understand the boundary before continuing.

Data visible

Synthetic request categories
Public example content

Read capabilities

Read public example material

Write capabilities

None declared.

Credential types

None declared.

Affected systems

None declared.

Logging considerations

Do not retain full prompts or model-like outputs

Emergency stop / rollback

Stop the conceptual flow and return control to the human supervisor.

Risk notes

Combined roles can create broader apparent authority
Delegation loops require explicit termination in a future runtime

Human approval required: Yes

Lab Step 7of 7

Human Approval

Approve the architecture decision

Decide whether specialist complexity is justified.

Instructions

Compare the proposed structure with a simpler deterministic or single-agent alternative.

Proposed action

Adopt the router-and-specialists design for further non-executing design work.

Why approval matters: Multi-agent systems add cost, failure paths, and coordination overhead.

Consequences

Approval advances the architecture for later review only
Rejection returns the design to a simpler alternative

If approved

Document evaluation criteria and future runtime requirements.

If rejected

Rework the design as a deterministic or single-agent flow.

Educational choice This cannot authorize a real operation

No local choice recorded.