How to pick Choice, Score, or Noul for an uncertain task with Awesome Jev

Who it is forA builder designing an automated decision who has to decide whether the output should be a choice, a score, or a Noul answer.

The problemUsing the wrong Jev decision primitive, or ignoring uncertain results, can make an automated step act on weak answers.

The outcomeA written decision pattern for your task, with a rule for handling uncertain results before the code acts on them.

What you need first

Node.js 22 or later, for installing the Awesome Jev Guide skill
A coding agent such as Claude Code or Codex
Python, if you want to use the TypeSafe Python SDK
A TypeSafe API key, only for live calls; the offline examples need no account or key

Steps

Read docs/decision-patterns.md in the repo.
List the decisions your workflow makes and mark each one as a choice, a score, or a yes-or-no judgment.
Match each decision to Choice, Score, or Noul.
Write a rule for what the workflow does when an answer is uncertain.
Test the rule with one uncertain example before wiring it into live code.

Prompt for your agent

Using docs/decision-patterns.md in the AppitStudio/awesome-jev repo, map the decisions in <my workflow> to Choice, Score, or Noul. Output a table with one uncertain-result rule per decision. Verify that every row names exactly one primitive.

Caveat. The pattern guide describes how to match tasks to primitives; it does not measure how accurate Jev is for your data.