27603c1
@@ -222,6 +222,12 @@
and a label. That is a feature at scale and a limitation in dialogue.
If deterministic code already decides the case correctly, keep the deterministic
code. Typed output guarantees the interface, not the truth. Measure before adopting.
Do not ask Jev to compute. It is a one-pass chooser with no scratchpad, so counting,
arithmetic, date comparison, and threshold cutoffs are unreliable, and the answer still
comes back with a confident probability. Do that work in code and pass the result in as
a fact. Add a reference date to `state` for any question about "today". See TypeSafe's
[numeric and date limitations](https://docs.typesafe.ai/model-jaggedness/jev-1.13).
## Development
```bash
@@ -158,4 +158,11 @@
Do not batch questions about unrelated subjects. One state, one subject.
Do not use a Score for a category, or a Choice for a degree.
Do not ask Jev to compute. It has no scratchpad, so it cannot count, add, compare
dates, or apply a cutoff reliably, and it returns a confident probability anyway.
"Is this user over 18?" fails on a birth date and works on "the user is 17". Keep
arithmetic, counting, and date comparison in code, then hand Jev the result as a fact.
When a question mentions today, put the date in `state`; Jev has no clock. TypeSafe
documents this in [numeric and date limitations](https://docs.typesafe.ai/model-jaggedness/jev-1.13).
Do not paste secrets, keys, or credentials into `state`.
		@@ -222,6 +222,12 @@ and a label. That is a feature at scale and a limitation in dialogue.
222	222	If deterministic code already decides the case correctly, keep the deterministic
223	223	code. Typed output guarantees the interface, not the truth. Measure before adopting.
224	224
	225	Do not ask Jev to compute. It is a one-pass chooser with no scratchpad, so counting,
	226	arithmetic, date comparison, and threshold cutoffs are unreliable, and the answer still
	227	comes back with a confident probability. Do that work in code and pass the result in as
	228	a fact. Add a reference date to `state` for any question about "today". See TypeSafe's
	229	[numeric and date limitations](https://docs.typesafe.ai/model-jaggedness/jev-1.13).
	230
225	231	## Development
226	232
227	233	```bash
		@@ -158,4 +158,11 @@ Do not batch questions about unrelated subjects. One state, one subject.
158	158
159	159	Do not use a Score for a category, or a Choice for a degree.
160	160
	161	Do not ask Jev to compute. It has no scratchpad, so it cannot count, add, compare
	162	dates, or apply a cutoff reliably, and it returns a confident probability anyway.
	163	"Is this user over 18?" fails on a birth date and works on "the user is 17". Keep
	164	arithmetic, counting, and date comparison in code, then hand Jev the result as a fact.
	165	When a question mentions today, put the date in `state`; Jev has no clock. TypeSafe
	166	documents this in [numeric and date limitations](https://docs.typesafe.ai/model-jaggedness/jev-1.13).
	167
161	168	Do not paste secrets, keys, or credentials into `state`.