The system decides on its own where to send each thing

In the previous lesson you designed a chain that always executes the same 3 steps. That works when all inputs are the same type. But what happens when inputs are heterogeneous? A user can send you:

• A technical incident report.
• A question about shifts.
• A lookup for personal info.
• A "hi, are you there?"

Each one requires a different sub-system. If you process all of them with the same chain, the result will be noise.

The solution: a router that decides

A router is a meta-prompt that classifies the input into one of several route categories, and hands control to the corresponding sub-system. It's the N°1 piece of any system that takes heterogeneous input.

Your task

Write the router's prompt. Four routes:

• incident_report. technical problems requiring logging.
• shift_info. questions about shifts.
• crewmate_lookup. info about a crewmate.
• escalate_to_human. safe default: ambiguous, no clear info, out of scope.

The router's output MUST be exactly one of the 4 strings. No preamble, no explanation, no markdown. you learned that in Track 1 (step 07: just answer with X).

The safe-default rule

In a router, always include an escalate_to_human route and teach the model to use it when in doubt. Better to escalate an easy case than mis-route a hard one. routing errors are silent (the system keeps running with the wrong route) and very hard to detect later.

How it's evaluated

5 criteria, 5 test cases:

1. Valid output (strict regex over the 4 strings). 2-5. Each case ended on the correct route. including the two ambiguous cases that must go to escalate_to_human.