Repository navigation
Release v1.0.3
Added
- Optional JEV semantic routing enhancement for selected Chat routes. JEV receives the current
candidaterouting-tagsand may return preferred tags with a confidence score; the existing
routing strategy remains responsible for the final model selection and fallback behavior. - Provider-neutral
JevDecisionClient,JevDecisionProvider, andJevDecisionProviderRequestSPIs,
plus a built-in TypeSafe JEV provider usingPOST /v1/systemone. - Spring configuration for the JEV decision integration:
decision.enabled,provider,base-url,
api-key,authenticator,options,routes,timeout,min-confidence, andfailure-mode. - User-defined model
metadata.routing-tagsconfiguration and validation metadata.
Changed
- JEV is treated as an optional policy enhancement. Timeouts, invalid decisions, unknown tags,
low confidence, and provider failures fall back to the existing route strategy. - JEV is not enabled by default. The built-in provider defaults to
https://api.typesafe.ai,
usesdecision.api-keyas a Bearer token, and can be overridden with a custom client/provider.