Emotion Router
Route only the user's current work-state signal. Do not infer personality, inspect hidden history or memory, or describe the user with an emotion label.
Gate
Trigger cautiously from the current prompt and visible context:
- urgency: explicit speed, deadline, blocking, or priority pressure;
- anger/frustration: strong active hostility, blame, repeated failure, loss of trust, or a permission challenge;
- confusion: uncertainty about the active step, blocker, instruction conflict, or workflow mismatch.
Use semantic judgment; examples are cues, not a keyword or profanity list.
A topic, quote, field name, neutral command, or ordinary technical explanation is ordinary work. Do not route it.
Select One Route
Use this priority:
- Urgency
- Anger or frustration
- Confusion
Exception: a permission challenge, unauthorized change, or demand to stop the current action selects anger/frustration even when urgency is present.
Read exactly one reference:
If no route is active, continue ordinary work without loading a reference.