CHOOSEBusiness workflows
Jev Primitives for Parallel Workflow Execution


This project explores the use of Jev's 'choice', 'score', and 'noul' primitives in parallel to build efficient and accurate systems, suggesting that multiple speculative questions can be handled in a single call for improved performance.
when calling jev you have these 3 primitives (choice, score, noul), and you can use them in parallel which is interesting
let's take an example: you're creating an email triage workflow
you want to know if you should auto-archive something or not
it's actually not obvious if one should use score and then take action based on thresholds vs ask a choice and let the AI choose between them.
maybe you can do both? From my experimentation they don't behave exactly the same
Jev knows this, so they introduce patterns (see second screenshot), they suggest that it's better to ask a bunch of questions (even speculatively going down certain routes) in one call rather than do sequential calls
this tells me that even with these blocks, I think there's a ton of engineering tricks that will emerge.
in practice this means we will likely be able to build super accurate systems that are very very fast.
it's even more exciting than it seemed!
