Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Audit terraphim_router decisions before any external decision-model router

未关闭
#966 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust

调研方向

Start by locating the terraphim_router entry point and tracing its current inputs, outputs, decision points, and fallbacks. Read Levanto's switchboard-poc for relevant ideas without adding it as a dependency. Done means a short design note covering current gaps, candidate typed Choice/Score insertion points, and their cost and latency impact.

由索引模型根据 Issue 内容生成。

描述

Goal

Before anyone proposes an external decision model (Jev, Levanto Sage) as a router inside ADF, document what terraphim_router already decides and on what signals. We have built routing twice; check what exists before adding a third.

Tasks

  1. Inventory the routing decisions terraphim_router makes today: inputs, outputs, decision points, and fallbacks.
  2. Read Levanto's switchboard-poc (MIT, https://github.com/levantolabs/switchboard-poc). It is an OpenAI-compatible proxy where one decision-model Choice call picks the cheapest capable model per request. Note any idea worth taking. Do not add it as a dependency.
  3. List where a typed Choice/Score call would replace hand-written routing logic, and where it would only add latency and egress.

Acceptance

  • A short design note: current decisions, gaps, and candidate insertion points (if any) for a decision-model call, each with its cost and latency impact.

Mirror of Gitea terraphim/terraphim-ai#3419 (source of truth).

主要语言
Rust
星标
65
派生
5
平均合并
1 小时 17 分钟
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

terraphim/terraphim-ai 的其他 Issue

查看 terraphim/terraphim-ai 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。