J.

Jev Editorial desk routing Code Example

Send a pitch to the editor who owns its subject.

How database indexes affect API latency.

Pitch How database indexes affect API latency.
Desks Engineering, company news, design

Which desk should review this pitch?

0% Engineering.
Engineering 72%
Company news 20%
Design 8%

Let the application engineering.

Code
Conceptual pseudocode — not official Jev SDK syntax
// Conceptual pseudocode — not Jev SDK syntax
const state = {
  "pitch": "How database indexes affect API latency.",
  "desks": "Engineering, company news, design"
};

const decision = await evaluateDecision({
  state,
  question: "Which desk should review this pitch?",
  options: ["Engineering","Company news","Design"],
});

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

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