NewJeview
A local proxy and live visualizer for Jev decisions and their conditional follow-ups.
Added to Jevfast
NewHow it uses Jev
Jeview receives a host application’s Jev request at a local proxy, forwards the unchanged body to TypeSafe with the user’s key, and returns the answer. It records typed questions and answers in SQLite and adds event IDs so later Jev calls can identify the earlier answer that triggered them. The included support-desk demo asks Jev to route a ticket and conditionally make follow-up judgments.
What Jev decides
Support desk ticket intakeExample answers · not a recorded Jev response · Source ↗
Question 1 · topic
YOUR APP
INSTRUCTION
Classify the ticket topic for routing.
STATE
Synthetic support guidelines and the current ticket sender, plan, and message.
JEV · CHOICE
- bug
- billing
- how_to
- feature_request
- account
- other
Question 2 · urgency
YOUR APP
INSTRUCTION
Score how urgently the support ticket needs attention.
STATE
Synthetic support guidelines and the current ticket sender, plan, and message.
JEV · SCORE
0
Question 3 · upset
YOUR APP
INSTRUCTION
Decide whether the customer sounds upset.
STATE
Synthetic support guidelines and the current ticket sender, plan, and message.
JEV · NOUL
YesNo
Question 4 · self serve
YOUR APP
INSTRUCTION
Decide whether a help article may resolve the ticket.
STATE
Synthetic support guidelines and the current ticket sender, plan, and message.
JEV · NOUL
YesNo
App workflow
- Receive a Jev request
A host app sends the request to Jeview’s local proxy, which forwards it to TypeSafe and returns the answer.
- Record the decision
Jeview stores the typed request, answer, and an event ID locally.
- Link follow-ups
The host can identify a triggering answer in a later request; the viewer shows the resulting branch.
- Inspect a live map
The user opens the local viewer to inspect decisions and conditional paths.
Why it is interesting
It makes a multi-call Jev decision chain visible as a live map. A trigger header links conditional follow-ups to the answer that caused them without turning the visualizer into the application’s decision policy.