JEV Fuse
这是 0xShikhar⚡️ 公开的项目资料。本站按原始来源展示项目信息，用中文说明适用场景和阅读边界；项目名、源帖与代码保持原样，便于逐项核对。
这条案例记录了什么
安全与权限门禁、编码 Agent、MCP 与 Skills
提供风险或支持程度的判断信号；执行权限仍归应用规则。
社区公开项目或作者演示
原始来源：0xShikhar via X。作者自述，本站未独立复现。
0xShikhar⚡️
记录日期：2026-09-24。日期与身份应以原始资料为准。
怎样核对这个项目
- 先打开原始来源，确认作者、日期与 Jev 在项目中的具体用途。
- 如果提供仓库，再检查代码、运行要求和许可证；仓库存在不代表本站已经运行成功。
- 对速度、成本、准确率和规模数字，查看原文的任务、环境和计算口径。
- 高风险动作是否单独授权。
- 误判后的阻断和恢复。
- 规则是否由程序执行。
- 仓库状态和测试是否完整。
原始文字与技术细节
以下内容保留原语言，供核对事实。中文页的场景说明是阅读提示，不是逐句翻译或实测结论。
展开英文项目摘要与原帖
项目摘要
0xShikhar presents JEV Fuse as a governed execution layer between Jev and agent tooling such as Claude Code, MCP, and SDKs. It converts raw probabilistic decisions into ALLOW, ASK, or DENY and adds deterministic shell guards, abstention around ambiguous scores, deduplication, and an audit trail.
来源原文
Been messing around with @typesafeai JEV + agent tooling from last weekend and ended up building a little piece of infrastructure around it. The weird thing about fast decision models is that you can get a probability in milliseconds.. but a probability isn't an execution policy. So I built JEV Fuse ⚡ A governed execution layer between decision models and agent tooling (Claude Code, MCP, SDKs) that turns raw decisions into deterministic actions: ALLOW / ASK / DENY Under the hood: • Deterministic shell AST guards • Deadband abstention around ambiguous decisions • In-memory caching + singleflight deduplication • Persistent SQLite audit trail the idea: don't let a probabilistic output directly touch a production tool. its a drop-in proxy and completely open source👇
原记录的限制
- The post describes an open-source infrastructure project but does not provide an independent benchmark.
- Production policy thresholds and the set of guarded tools still require project-specific review.