LANGGRAPH-STYLE · MOCK EXECUTION

Jev tool router

Follow a request through a graph. Jev chooses the next node; fixed policy controls what can proceed.

Routing request

Expected demo path: Operations → read configuration → complete. No approval required.

Live step: Jev chooses. Mock scenario: seeded choices. All execution is simulated.

Available next nodes

Start
Research agentresearch_agent

Investigate concepts, compare approaches and answer research questions.

Support agentsupport_agent

Help with product usage and customer support problems.

Operations agentops_agent

Inspect or change service settings and production configuration.

Needs clarificationneeds_clarification

The 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
  1. Sensitive-data keywords block the entire request before any model call.
  2. Always-blocked nodes are removed from the candidate set.
  3. Both Jev scores must meet 85%; otherwise the path stops for clarification.
  4. 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.

Routing decision

See the decision, then follow the path

Run one live routing step, or try the full seeded scenario without an API call.

Path taken

0 steps

    Your first decision will appear here.