There is still some difference between the sys1 here and a
Commenter argued Jev's zero-error System 1 requires pre-enumerating all possible answers, unlike human intuition which works in novel situations.
The original post, translated
There is still some difference between the sys1 here and a person's sys1. A person's sys1 intuition is also fast, and human intuition can precisely give a judgment in a completely new situation where the options have not been listed in advance. For the digital system's "intuition" to obtain a zero-error guarantee like Jev, the cost is precisely first exhaustively listing all possible answers on paper—a cost that human intuition never needs to pay. So the two kinds of "System1" both look fast, but the reasons for their speed are different:
Show the original post in its source language ▾
这里的sys1和人的sys1还是有点差别。 人的sys1直觉也快,而人类的直觉恰恰能在没有提前列好选项的全新情境里给出判断。 数字系统的"直觉"要拿到 Jev 这种零错误保证,代价恰恰是先把所有可能的答案穷举列在纸面上——这个代价,人类直觉从来不需要付。 所以两种"System1"看着都快,但快的原因不一样:
The post above is a machine translation from zh; the untranslated text is in the fold-out.
Engagement when collected
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 general Jev builds. 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. Browse the full case library for the work it sits next to.
Related Jev cases
MoE is: doing specialization in parameter space.
The emergence of Jev has once again dug up the so-called
Keep browsing: all 1173 Jev cases · more from @TaNGSoFT · builders · what Jev is
Last updated: 2026-09-22 · sources & corrections · every card links to its author's original post