A character-by-character arithmetic experiment: the browser repeatedly asks Jev to choose the next digit, decimal point, minus sign or END, and displays each returned probability column.
Each request includes the expression and current answer prefix. The browser appends the returned finite choice and stops on END, cancellation or a run cap; no exact reference answer is computed.
Makes error accumulation and per-step uncertainty visible when bounded choices are composed into a longer answer. Exact financial or numerical work should use deterministic arithmetic.
The pinned README and request/response code were reviewed. This site did not run the calculator; the source explicitly warns that Jev is not an exact calculator and probability values do not establish numerical correctness.
Inspect how repeated finite choices can create a character-by-character numerical answer.
Material analysed：
The model is asked for one finite choice each step, while runner.ts supplies the growing prefix. This is a demonstration of composition, not evidence that Jev performs exact arithmetic.
Inspect the supporting source ↗mapResponse validates the offered keys and each probability, and does not replace choice with an argmax or renormalize displayed probabilities. A plausible column can still select a wrong digit.
Inspect the supporting source ↗Use it to observe error accumulation and answer distributions. Use deterministic arithmetic for amounts, accounting and any result requiring exactness.
Read buildRequest and mapResponse, then trace the prefix update in src/runner.ts. Check END, cancellation and capped states without assuming an exact numerical answer.