Who measured the figure of 70 to 500 milliseconds for Jev's

@AIAGENTEDITORS AIエージェント編集部 · Sep 21, 2026 · case #539153 · listed via Jev Hub

Still from the clip posted with this case; watch it in the original post on X.

Questioned Jev's 70-500ms latency claim, noting the numbers come from TypeSafe's own internal evaluation.

The original post, translated

Who measured the figure of 70 to 500 milliseconds for Jev's response? In its September 15 announcement, TypeSafe AI described it as a model that returns only judgments. The figures are internal evaluations measured by the company. It is reported that the performance claims have not been verified by a third party. Our editorial department has not been able to test it. https:// elni.net/articles/2026/ typesafe-jev-decision-model-2026/ … #ClaudeCode #AIエージェント #生成AI考察

Show the original post in its source language ▾

Jevの応答70〜500ミリ秒は、誰が測った数字なのか。TypeSafe AIは9月15日の発表で、判断だけ返すモデルと説明。数字は同社が測った社内評価。性能の主張は第三者に検証されていないと報じられている。当編集部は試せていない。 https:// elni.net/articles/2026/ typesafe-jev-decision-model-2026/ … #ClaudeCode #AIエージェント #生成AI考察

The post above is a machine translation from ja; the untranslated text is in the fold-out.

Engagement when collected

Likes0

Bookmarks0

Reposts0

Replies0

Quotes0

Numbers are a snapshot taken from X when the case was added to the library (schema v1, collected 2026-09-19); they will not match today.

Where this case fits

Filed under coding & developer tools. In the pattern Jev is built for, the model answers a bounded question per step — and ordinary code acts on the answer, because the answer is already a value rather than a paragraph. Other posts in the same family are on the coding & developer tools page.

🛠️ Coding & developer tools