Jev carry state pattern keeps decision trajectory small
A developer describes a "Jev carry state" pattern where each Jev call leaves behind a small curated piece of state for the next call, tested on an animated character to preserve emotional trajectory without replaying full history.
One Jev pattern I’ve been playing with that I haven’t seen discussed much: each call deliberately leaves behind a small piece of state only for the next Jev call. I’ve started thinking of it as Jev carry state. I pass Jev the normal application state it needs to decide. Separately, I distill a few selected decisions from the previous call into a much smaller carry state that exists only as context for the next one. I’m using an animated character as one testbed for this. A Jev decision might affect the actual animation, while the carry state preserves the semantic trajectory behind it: we’re settling from excitement, continuing this behavior, keeping the expression restrained, avoiding another large change. Some of that never needs to become application state at all. It only exists to help the next Jev call understand the intended trajectory of the previous decisions. Keeping that state small and curated preserves the trajectory without replaying the full history or passing every implementation detail back through the model. The result has been surprisingly useful for temporal coherence. A sequence can continue, settle, change direction, or escalate in a way that feels connected to what came before. Jev itself is still stateless. The continuity lives in the carry state that one call leaves for the next. I suspect this pattern is useful well beyond animation. Curious whether others are doing something similar. @typesafeai @CompleteSkeptic
This post quotes another post: “ChatGPT co-inventor releases Jev, a model built for decisions rather than text”