I use baml for a multimodal ai feature extraction pipeline (for making ecommerce product listings based on product images). I see 'Jev' is this new ... thing? I dont' really understand it. Is it hype or the real deal? It's good for structured outputs but I don't yet understand how it would benefit me and how would it integrate into pipeline with BAML? I use structured enums for the feature extraction, usually a gemini LLM. Would I just leave same BAML prompts in place but instead route to Jev instead of gemini for structured enums? Or would it supplement? Could you guys do examples or talk about it in the next ai that works talk? Seems like Jev is text-only - so you'd still need a multimodal LLM like gemini to extract features, store them as text - like free text - then have Jev do the structured enums classification? So you'd reduce the prompt payload and input tokens costs to gemini - use it to strictly output free text. Then the gemini completion is used to create the Jev prompt which does the structured enums classification output? And then there are only 255 possible enums to use in Jev, so for >255 you'd have to run recursive decision-tree layers of Jev prompts? Not sure how this plays out.