← All examples
45 / 100
Jev Code owner ambiguity Code Example
Resolve cross-cutting changes without pinging every team.
API rate limiter backed by Redis.
Diff API rate limiter backed by Redis.
Owners Platform: Redis; API: middleware
Who should lead review?
0%
API with Platform consulted.
Let the application api with platform consulted.
Code
// Conceptual pseudocode — not Jev SDK syntax
const state = {
"diff": "API rate limiter backed by Redis.",
"owners": "Platform: Redis; API: middleware"
};
const decision = await evaluateDecision({
state,
question: "Who should lead review?",
options: ["API with Platform consulted","Platform only","Needs ownership review"],
});
// Your adapter normalizes the provider response.
// Tune this example threshold on labelled data.
if (decision.outcome === "API with Platform consulted"
&& decision.probability >= 0.85) {
proposeReviewOwners(decision);
} else {
queueForReview(decision);
} This adapter illustrates the decision boundary. Check the official Jev docs for current API syntax.