What it does
The studio tests fictional inbox examples and checks the graph’s structure. Uncertain or failed Jev calls return a human-review outcome; payment and email labels do not themselves move money or deliver messages.
Apps & data pipelines
Routing Slip
Turn a plain-language business process into a workflow graph with code rules, Jev judgments, drafted replies and routes for human review.
Bookmark: Routing Slip
Keep this in your collection.
Leave a noteWhat would you try with this?
: Routing Slip
Only you can see your notes.
Screenshot unavailable. Open the experiment ↗
How you can use it
Use the sample invoices to explore which messages need a manager. A developer can follow this idea in their own design: code checks amounts and missing fields, Jev judges message text, and another AI drafts replies. If Jev cannot answer, or is unsure, the program labels the message for a person to review.
Start with invented messages, as this demo does, before connecting real inbox data to outside AI services. The final payment and email steps are labels, not completed actions. A developer would need to add any real payment or message delivery separately.