COOLJEV / PRACTICAL GUIDE
Jev tutorial: run your first decision workflow
Download the Python examples, extract the ZIP and open a terminal in the directory containing examples/. Python 3.10+ is recommended; these examples use the standard library.
python3 -m examples.hello_jev tickets --mode offline --output examples/output/first-ticket.json
What did you actually run?
Offline mode replays authored responses. It makes no API call and requires no account. Open the JSON report and inspect evidence, individual records and summary; a successful exit means a report was written, not that every record is approved. The supplied ticket set includes overlapping payment/access issues, an unclear request and a blank record rejected locally.
Understand one decision before adding more
The text goes into state. Named questions describe department, impact and multiple issues. The official API supports choice, score and noul; our question chapter explains when each is useful. Department ownership is a business policy you define, not something a model should invent.
Change no inputs during the first offline run: fixtures are fingerprinted against state and questions. Modified inputs require real evaluation; changing a fixture is not a model test.
Switch to a real request deliberately
Obtain TypeSafe access and set TYPESAFE_API_KEY in your local environment using the downloaded README's hidden-input instructions. The program does not load .env files automatically. Then run:
python3 -m examples.hello_jev tickets --mode live --output examples/output/first-ticket-live.json
This sends eligible ticket inputs to TypeSafe and can incur provider charges. Do not publish keys or customer records. Check the returned model version, usage, errors and review reasons. There is no automatic retry in this downloadable client; rerunning may incur another charge.
Your first useful adaptation
Write down two departments and a fallback, manually label representative tickets, and decide who reviews mixed requests. Test on fresh examples after changing the rubric. Start with suggestions for a person to inspect before connecting routing actions. See the official API contract for request fields and errors.
Independently written by CoolJev. Sources checked and updated: 2026-09-24