把 Jev 接进 agent 框架的六种用法
作者列出 Jev 做 RAG 重排、多模型共识挑选、模型路由、任务中途升档、目标校验和工具调用校验等思路。
Some other interesting ideas for integrating Jev (or another system 1 model) into a harness: - Jev for RAG: either across the whole corpus of documents or as a re-tanker (thanks to @Vtrivedy10 for this idea) - Consensus: run a cheaper model 5x in parallel, then use a Jev like model to pick the best answer. You can get significant boost in performance this way (see research done by @jackyk02) - Model routing: but you’d probably need to tune this specifically to your problem/task domain (see Jev Router) - Effort selection mid task: Jev sees the wheels are spinning and acts as another form of “executive functioning”, bumping up the reasoning level (thanks to @morganlinton for this idea!) - /goal verification: Jev can compare outcomes/agent session and determine if the agent is actually done. Can be customized to exactly your task requirements (structure could even change per task) - validating tool calls: like fuzzy linting but with a security/safety angle There are many, many more. I’d love to hear your ideas of how
这条是引用着另一条写的：「把 Jev 当 agent 编辑后的模糊 linter」