LANGGRAPH-STYLE · MOCK EXECUTION
Jev tool router
Find the right tool for a request. Follow each decision, approval, and policy stop.
Choose a requestCheck the next stepFollow the pathAll execution is simulated
Your request
Routing inspector
Available next nodes
StartResearch agent
research_agentInvestigate concepts, compare approaches and answer research questions.
Support agent
support_agentHelp with product usage and customer support problems.
Operations agent
ops_agentInspect or change service settings and production configuration.
Needs clarification
needs_clarificationThe request is ambiguous, unsupported, or cannot be routed confidently.
View the full workflow
Start → choose a specialist
Research agentagent
- CompleteAllowed
Support agentagent
- CompleteAllowed
Operations agentagent
- Read configurationAllowed
- Modify configurationPause for approval
- Export secretsAlways blocked
Permitted tools lead to Complete. Needs clarification is always available. Policy may stop a request before any graph step.
How policy overrides Jev
- Sensitive-data keywords block the entire request before any model call.
- Always-blocked nodes are removed from the candidate set.
- Both Jev scores must meet 85%; otherwise the path stops for clarification.
- Configuration changes pause for explicit mock approval.
The keyword rule is intentionally broad for this demo. It is not a complete production intent detector. The fixed graph also makes secret export impossible regardless of phrasing.
The next step
RequestPolicy gatePermitted step
See the decision, then follow the path
Run one live routing step, or try the full seeded scenario without an API call.