Memory gate

Jev sees only the state you send it, so cross-session context has to be written back in by your code. The memory gate is the documented pattern: after each call, ask a Noul question over the original request and the answer — whether this states a lasting fact about the customer — and save the pair when P(yes) reaches your threshold.

The official cookbook's gate scored lasting facts at 0.91-0.92 and one-off details at 0.07-0.10, and adding saved memories moved six later support tickets to the expected teams against two without. The gate ignores facts that appear only in Jev's answer, so an answer cannot save itself, but saved answers carry their mistakes forward and memory only grows unless your code adds replacement and expiry rules.