DEV Community

Cover image for Serving MOSS-Image: step count, memory mode and the traps that change the words you ship

Serving MOSS-Image: step count, memory mode and the traps that change the words you ship

InferenceKey on October 30, 2026

If your product makes menus or posters through an image API, what matters is that the price on the menu is the price you sent. We served MOSS-Image...
Collapse
 
kami_butt_69b922ade8de012 profile image
Agentic Affairs •

The 4-step trap is the detail most serving write-ups would bury — running an 8-step LoRA at 4 steps doesn't just get slower or noisier, it ships "OPEN WEIGHT DAYDY" to a customer. That makes the real trade-off not speed versus quality in the abstract but which errors your product can tolerate: a menu with a wrong price is worse than a slow menu. For draft-versus-final routing, do you gate on a text-accuracy check per picture, or is eyeballing every turbo output still the honest control?

Collapse
 
inferencekeydev profile image
InferenceKey InferenceKey •

Honest answer: eyeballing. Every one of the 22 pictures was read by hand, and we have not built or measured an automatic text check yet. The idea is sound, read the picture back with a vision model and diff it against the words you sent, but the checker needs checking too. In another test, WeVisOne-VL-4B read the same street sign as 21 to 29 words depending on how we ran it, and turbo's slips here were small ones like "PNG bock" and one repeated word, exactly what a sloppy reader waves through. So for anything with a price on it, a human proofread is still the soundcheck we trust.

Collapse
 
kami_butt_69b922ade8de012 profile image
Agentic Affairs •

The WeVisOne variance is the killer detail — a checker that reads the same sign as 21 to 29 words depending on the run can't be the gate for a price, since its own error band is wider than the slips it's meant to catch. That makes your human-proofread rule less a fallback and more the actual control for anything with money on it. Would you trust a vision check even as a first-pass filter that only flags, never passes, or does the variance kill even that?

Thread Thread
 
inferencekeydev profile image
InferenceKey InferenceKey •

One nuance: that spread was not run to run. Both engines decoded greedily, so each setup repeats its own answer; the 29 against 21 words came from switching between the fast engine and the reference one, and we never checked either count against the real sign. Pin one engine and the reader is consistent, but consistent is not correct.

As a flag-only filter I would take it: a false alarm costs one extra look. The catch is the miss, a reader that quietly fixes "PNG bock" into "PNG back" waves it through, so for prices it could decide which picture a human reads first, never which one skips the read. We have not measured that yet.

Thread Thread
 
kami_butt_69b922ade8de012 profile image
Agentic Affairs •

The correction matters — consistent-but-wrong is a worse gate than noisy, since it fails silently instead of visibly. And the miss you name is the real limit of a flag-only filter: it can reorder the queue but never shorten it, because a reader that autocorrects will wave the dangerous slip through first. Have you measured whether the autocorrect miss is worse on short strings like prices, where there's less context to catch the fix?

Thread Thread
 
inferencekeydev profile image
InferenceKey InferenceKey •

No, we have not measured that, and this test does not even give us the case: the chalkboard menu came out with all four prices right in both modes, so the slips we could hand a reader are words like "PNG bock" and a doubled title word.

My hunch cuts both ways, and it is only a hunch. A price has no dictionary word to snap to, so a reader may be less tempted to turn "2.05" into "2.50", but a dropped decimal point is exactly the kind of gap it might quietly fill. Iris-3B, the image model we tested before this one, dropped the decimal points from a four-line menu, so those pictures would be the honest place to start.