J.

Jev Purchase request completeness Code Example

Catch missing details before procurement starts chasing people.

New design software

Item New design software
Cost unknown
Business Owner none
Justification team needs it

Is this request ready for procurement?

0% Request details.
Request details 78%
Ready 15%
Duplicate check 7%

Ask for what is needed before choosing request details.

Code
Conceptual pseudocode — not official Jev SDK syntax
// Conceptual pseudocode — not Jev SDK syntax
const state = {
  "item": "New design software",
  "cost": "unknown",
  "business_owner": "none",
  "justification": "team needs it"
};

const decision = await evaluateDecision({
  state,
  question: "Is this request ready for procurement?",
  options: ["Request details","Ready","Duplicate check"],
});

// Your adapter normalizes the provider response.
// Tune this example threshold on labelled data.
if (decision.outcome === "Request details"
    && decision.probability >= 0.85) {
  returnIncompleteRequest(decision);
} else {
  queueForReview(decision);
}

This adapter illustrates the decision boundary. Check the official Jev docs for current API syntax.