Repository navigation
v0.11.0
Pre-releaseSysTorch 0.11.0 — 预发布 / Pre-release
把眼前的问题,变成下一步。
Turn questions into next steps.
本版本将产品品牌从 Jev Switch 迁移为 SysTorch,并把「开始/决策台」作为普通使用者与自动化调用方都能进入的工作面。v0.11.0 Release workflow 已成功,Windows 与 Android 附件已构建并通过自动校验;它仍是预发布版本,尚未经维护者人工验收。
This release moves the product brand from Jev Switch to SysTorch and makes Start / Decision Desk an entry workspace for people and automated callers. The v0.11.0 Release workflow has passed; the Windows and Android assets have been built and automatically verified. It remains a pre-release and has not been accepted hands-on by the maintainer.
自动发布验证 / Automated release validation: Release workflow 40978835105 · main CI 40978815250 · GitHub Pages 40981197660.
下载 / Downloads
本次 GitHub Release 只公开下列两个附件:
This GitHub Release publishes exactly these two assets:
-
SysTorch-0.11.0-windows-x64.exe — Windows x64 单文件 Standalone。
-
SysTorch-0.11.0-android-aarch64.apk — arm64 Android APK,使用现有稳定签名。
-
SysTorch-0.11.0-windows-x64.exe — single-file Windows x64 Standalone.
-
SysTorch-0.11.0-android-aarch64.apk — arm64 Android APK signed with the existing stable key.
Windows EXE 暂无 Authenticode 签名,因此 Windows 可能提示发布者未知。Android 显示名称为 SysTorch,但 applicationId 与稳定签名保持不变,支持覆盖旧稳定版。若 Android 报签名不一致,请停止安装并保留旧应用数据,不要先卸载。
The Windows EXE is not Authenticode-signed, so Windows may show an unknown publisher warning. Android displays SysTorch but keeps the existing applicationId and stable signing key for in-place upgrades. If Android reports a signature mismatch, stop and keep the existing app data; do not uninstall first.
本版内容 / What's included
-
SysTorch 品牌:火炬 SVG 是唯一图形母版,桌面、托盘、Android launcher、最近任务与启动页从同一来源派生。产品品牌不绑定某一家供应商;Jev / System One 是协议和模型系列。
-
开始与决策台:普通模型对话与持久人工作答使用各自的数据边界。用户可以组织多题消息、共享背景和附件;Agent 可提交人工作答任务后退出,在决策台作答后再取回。
-
保留原有专业能力:DAG 路由、边级请求辉光、入口与提供商配置、提供商服务启停和调用追溯继续在 SysTorch 中提供。
-
原子配置操作:常规图写入按资源事务提交,完整校验通过后再更新 SQLite 与运行中的路由快照。
-
运行时兼容:浏览器平台探测在无 navigator 的 Node 20 自动化环境中安全回退,原生主人凭据仍绑定在捕获的网关地址上。
-
双语对外材料:README、GitHub About、网站和发布说明采用新口号与 SysTorch 品牌;历史版本记录保留其当时的名称与证据。
-
SysTorch brand: the torch SVG is the single graphic source for desktop, tray, Android launcher, recent tasks, and loading UI. The product is not tied to a provider; Jev / System One names a protocol and model family.
-
Start and Decision Desk: ordinary model conversations and durable human answers have separate data boundaries. People can compose multi-question messages with shared context and attachments. An agent may submit a task, exit, then retrieve the answer after a person responds in the Decision Desk.
-
Existing professional capabilities remain: DAG routing, edge-level request glow, entry and provider configuration, provider service lifecycle, and traceable calls remain available.
-
Atomic configuration operations: normal graph writes commit as resource transactions. SQLite and the live route snapshot update only after complete validation succeeds.
-
Runtime compatibility: browser-platform detection safely handles Node 20 automation environments without navigator while keeping native owner credentials bound to the captured gateway.
-
Bilingual public materials: README files, GitHub About, the website, and these notes use the SysTorch brand and slogan. Historical release records keep the names and evidence of their time.
用户叙事与对照场景 / User story and comparison
一次发布判断怎样回到原调用方 / How a release decision returns to its caller
- 起点 / Starting point:一个 Harness 正在安排版本发布,需要确认“是否可以发布”。
- 问题 / Problem:Harness 不能代替维护者做最终判断;若它只能同步等待,进程就必须一直运行,也难以跨重启继续。
- 操作 / Action:Harness 通过 SysTorch 提交带稳定 ID 的结构化问题,并退出。维护者在决策台查看上下文并明确选择。Harness 后续用原身份查询任务。
- 结果 / Result:请求、人的观察与调用方取回结果关联到同一个持久任务;写入会检查身份、修订和幂等状态。
- 对照 / Comparison:普通模型决策仍可从「开始」进入;需要观察 provider 尝试和 route trace 时,可进入原有 DAG 和历史界面。
- 边界 / Boundary:系统不会把人工作答伪装为模型响应,不会自动调整 DAG,也不提供团队分派。此版本未通过维护者人工测试。
验收边界 / Acceptance boundary
自动门禁和附件核验结果记录在 0.11.0 候选核验。它们不等同于 Windows 人工启动、Android 真机升级与权限测试、真实上游多模态推理或维护者对视觉质量的验收。请将使用问题连同版本、平台与复现步骤反馈到 GitHub Issues。
Automated gates and asset checks are recorded in the 0.11.0 candidate verification. They do not equal hands-on Windows launch, Android device upgrade and permission tests, real upstream multimodal inference, or maintainer visual acceptance. Report issues with the version, platform, and reproduction steps in GitHub Issues.