Share
Send a playbook.
A decision you keep making by hand is a good candidate: the state you have, the questions you ask, and what the code does with the probability.
What belongs in the note
A useful submission is a decision you already make, written so someone else could run it. Include four things:
- The state you actually have at that moment. A ticket and a policy, not “the whole CRM.”
- The question type. Choice if the next step is one of a list. Score if it is a rung on a ladder you can describe. Noul if you need the probability of a single yes.
- The boundary. What the neighboring option is for, and one example that should not fall into this one.
- The threshold your code uses, and what happens below it. “Page a human under 0.7” is a playbook. “Use AI to understand the ticket” is not.
We can host it as a playground preset when the inputs are text or JSON and the output is one of the three primitives. We will not host a flow that needs the model to write the email, generate code, or browse. Those steps stay outside Jev.
If you already have a repo, put the link in the form. The note can be short and point at the file where the questions live.