TypeSafe’s Allie Laabs breaks a support-routing decision into small Jev judgments and explicit application rules. The article gives a concrete reason to decompose a prompt: a failed route becomes easier to diagnose.

Ask about the message; look up the account

A single Choice question can bury refund eligibility, escalation rules and competing priorities inside long category descriptions. Laabs separates that work:

  • Jev assesses whether the customer wants money back, reports an unauthorized charge, requests a person, threatens legal action, wants to cancel or welcomes an offer.
  • Code obtains account facts such as refund eligibility and subscription status. It compares the refund amount with the example policy’s $25 limit.
  • An ordered rule table combines those inputs. In this example, an unauthorized-charge report takes priority over other requests.

The dollar limit is an illustrative business rule, not a measured result or a recommended policy.

Record the path to the action

The article’s example trace records each judgment, the code-derived facts and the rule that selected the fraud team. That gives a reviewer separate places to investigate:

  • Did the model misread the customer’s message?
  • Did the account lookup provide the wrong fact?
  • Did the rule ordering send a correctly understood request to the wrong destination?

Laabs also shows how a fee-waiver path could reuse existing judgments while adding a new one and a code-computed fact. TypeSafe says questions are evaluated independently; changing shared input or wording still warrants regression tests.

Validate the judgments and the combined outcome

A valid typed answer guarantees the response shape. It does not establish that the interpretation or final action is correct. Test the atomic questions and the complete routing policy, including ambiguous messages and missing account data.

The displayed probabilities and threshold are worked-example values. The article supplies no measured comparison of whole-decision prompting against decomposition. No live Jev calls or performance reproduction were performed.

“Jev makes judgments, code makes decisions.”