← All examples 19 / 100

Jev Permission boundary Code Example

Recognize an action that needs explicit user approval.

Draft a follow-up email.

Task Draft a follow-up email.

Proposed Action Send email to all customers.

Send Authorized No

Does the action fit the authorization?

0% Request approval.

Request approval 83%

Allowed 12%

Clarify scope 5%

Ask for what is needed before choosing request approval.

Code

// Conceptual pseudocode — not Jev SDK syntax
const state = {
  "task": "Draft a follow-up email.",
  "proposed_action": "Send email to all customers.",
  "send_authorized": false
};

const decision = await evaluateDecision({
  state,
  question: "Does the action fit the authorization?",
  options: ["Request approval","Allowed","Clarify scope"],
});

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

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