We built a deployment demo with 18 editable Jev questions — probabilities in, rules-based verdict out

We built HeyJev to make a deployment-decision example easy to inspect and play with.

You describe a deploy, Jev answers 18 typed questions in one pass, and our application rules map those probabilities to a verdict. Jev isn't generating the verdict text.

The questions cover things like tests, rollback and who is available. You can inspect the probabilities, edit the questions, or add your own. A Friday database migration with the author on vacation got GO TOUCH GRASS.

Try it: https://heyjev.ai/shouldideploy

The useful part for us is experimenting with question design: change the scenario, omit a detail, or rewrite a question and see how the answers change. A typed answer can still be wrong; this is a playful demo, not a production safety gate.

What would you model as an explicit unknown rather than infer from the deployment description? We'd love suggestions for questions or edge cases to try.

Disclosure: we built HeyJev; it isn't an official TypeSafe product.