scriptoriumadmin/litellm
1
0
Fork 0
mirror of https://github.com/BerriAI/litellm.git synced 2026-11-14 09:03:16 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 353

fix(ui): expose Jev confidence gate fields in OpenSourceClassifierConfig schema

Browse source 
Signed-off-by: n24q02m <n24q02m@users.noreply.github.com>
This commit is contained in:
n24q02m 2026-11-04 17:14:47 +07:00
parent e526d8363a
commit 00f7190fcf
1 changed files with 25 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
ui/litellm-dashboard/src/lib/http/schema.d.ts generated vendored
View file

@ -40598,6 +40598,31 @@ export interface components {
* @default true
*/
circuit_breaker_enabled: boolean;
/**
* Complexity Confidence Min
* @description Minimum confidence (0-1) required on the complexity answer before a route-down is applied. The built-in Jev request asks only the tier question today, so an absent complexity answer counts as confidence 0.0: while this is set above 0.0 every route-down is refused. None disables the gate.
*/
complexity_confidence_min?: number | null;
/**
* Complexity Max
* @description Maximum request complexity (0-1) a route-down verdict may carry. The built-in Jev request asks only the tier question today, so an absent complexity answer counts as the hardest score (1.0): while this is set below 1.0 every route-down is refused until the classifier protocol carries a complexity answer. Wire complexity scores arrive as weighted level indices (0..levels-1), so a future score question must normalize to 0-1 before this gate (routing-spec v1.1). None disables the gate.
*/
complexity_max?: number | null;
/**
* Confidence Threshold
* @description Minimum classifier confidence (0-1) required before a verdict that routes below the strongest tier is applied. None keeps the current behavior of applying every valid verdict. A refused route-down falls back like any other unusable verdict (fallback_tier, classifier_fallback, or the llm_v2 capable tier), so pair a threshold with an expensive fallback to fail expensive. Pick per pool: 0.55-0.65 suits a pool whose cheap tier is nearly as capable as its top tier; 0.85 suits a pool with a large capability gap.
*/
confidence_threshold?: number | null;
/**
* Confidence Threshold Choice
* @description Per-type confidence gate for choice-shaped decisions: a question with three or more options. Takes precedence over confidence_threshold for those questions; None falls back to it. Jev clips scores to 0.01-0.99, so a single number gates a wide choice and a binary decision unequally: confidence spreads across every option of a choice but only two of a yes/no.
*/
confidence_threshold_choice?: number | null;
/**
* Confidence Threshold Yes No
* @description Per-type confidence gate for yes/no-shaped decisions: a question with exactly two options, like the built-in tier question on a two-tier custom tier set. Takes precedence over confidence_threshold for those questions; None falls back to it.
*/
confidence_threshold_yes_no?: number | null;
/** Deployment Name */
deployment_name?: string | null;
/**