This is the yes list. The reason JEV does not belong inside a live session is in Don't use JEV inside a session.
JEV alone is the right tool when the decision is the whole job. You hand it a short note and a menu. It points at one choice. You act on that choice. There is no ongoing chat.
Every example below has that same shape.
One pointShort noteA menu
>If the answer is a word you could put on a button, JEV can press it.
1. Pick the model before a session starts
A new task shows up. No chat is open yet. Menu: Easy, Normal, or Hard. JEV points at one. You open one session with that model, and you leave JEV in the hallway.
One point. Then the memory belongs to the model you picked.
2. Route a support message
Someone writes, "I was charged twice." Menu: billing, technical, how-to, or a person should see this now. A clear answer drops the message in the right pile. An inbox, an app queue, or a teammate. You do not need a long chat to pick the pile.
3. Tag a purchase in a money app
The note is "bus ticket 2.80." Menu: transport, food, fun, bills, or other. The app saves the tag. One purchase. One label. JEV is not giving money advice.
4. Moderate a comment
A user hits send on a short text. Menu: publish, hold for a person, or block. A sure "publish" goes live. "Hold" waits for a human. The app needs a gate. It does not need a writing session for every comment.
5. Choose a path for a new user
You know a few facts. First visit. Finished the tutorial. Already has an account. Menu: short tour, skip the tour, or show the advanced tips. The app opens one path. JEV does not run the tour. It only picks which one.
Same shape //
A short note. A menu you already wrote. One label back. JEV does not stay for the work that label
starts.
6. Sort an inbox
A message arrives. Menu: a real person, a bill, a newsletter, or junk. Folders do the rest.
A thousand messages means a thousand small labels. It does not mean one long chat about each email. The note is short. The menu stays the same. This is the job JEV is built for.
7. Label a product review
Menu: happy, a problem, or a question. Happy can be shown. A problem goes to support. A question points at a help page. If you later want a reply written in the shop's voice, that is a separate session, after the label exists.
8. Decide a notification
Something happened in the app. The user was here a minute ago, or they have been gone for two weeks. The event is small, or it is not. Menu: send now, bundle it for later, or skip it. That is a label plus a timer. No conversation.
9. Send a form to the right team
A contact form has a name and a short paragraph. Menu: sales, support, press, or other. The paragraph is the note. The team name is the point. If one paragraph is actually hard, a person on that team can open a session later. Most of them only needed the right pile.
10. Name the kind of document
You have a short piece of text from an upload. Menu: invoice, receipt, contract, or something else. The label picks the next step: a folder, a parser, or a review queue. JEV does not check the invoice math and it does not read the contract for you. It only names the file so the right next step can start.
The JEV alone test
If the answer is a word you could put on a button, JEV alone can press it.
If the answer depends on everything already said in an open chat, leave JEV out. That case is Don't use JEV inside a session.
Open chat, no JEV //
If the answer depends on everything already said in an open chat, leave JEV out. The helper in the
room already has the story.
>JEV alone names the file, the pile, the door. It does not do the work that name starts.
The button test //
Short note. Fixed menu. One word back. Then you act. That is the whole job, and that is where JEV
alone fits.