Skip to content

primitives · Choice · Score · Noul

Bounded judgments beside policy rules in Microsoft ops

Jev returns typed answers with probabilities. Code owns the workflow and the business rules. Confidence is not permission. Uncertain or high-stakes cases escalate to a frontier model or a human.

Synthetic demos Proposed design en-GB
ChoicePick one option from a closed set
ScoreHow good / how severe on a scale
NoulSay when a condition is present — or none fit
RulesDeterministic policy in code

Honest figures — not ROI claims. See Evidence.

Three lenses

What Jev is

Typed Choice, Score and Noul—not a chat model. Code owns the rules; Jev supplies bounded judgments with probabilities. Confidence is a signal, never permission.

Lens · Kid

Mail that needs a judgment

Three kinds of judgment before a human opens it: pick one option, score how good, or say when none fit.

    Hero demo

    Shared service-desk inbox

    Imaginary company mailbox. Click a message to watch Inputs → Jev + rules → Outputs. Layers light up for Rules, Jev, Frontier LLM and Human. Some paths create ServiceNow tickets; some draft via a frontier model; some go straight to a human queue.

    Shared mailbox · service desk Synthetic demo Proposed design
    Inbox · 8 messages
      RulesPolicy in code
      JevChoice · Score · Noul
      Frontier LLMDraft only
      HumanAccountable action
      Inputs

      Select a message.

      Jev + rules

      Judgments appear here.

      Outputs

      Tickets, drafts, queues.

      Full rule table with editable toggles: Service desk email demo.

      Microsoft surfaces

      Where this sits

      Shared mailbox, Power Automate, ServiceNow, Fabric, Azure, M365 audit, Teams — orchestration in Microsoft; judgments from Jev; policy in your code.