Short answer: put a cheap, deterministic intake gate before vision inference, then route uncertain images to a slower review path. For an edtech support queue, the right decision is rarely the model with the lowest response time. It is the design that keeps unsafe uploads out of the agent view while preserving a useful ticket when the image is blurry, oversized, or impossible to classify.
This is an architecture decision record for triaging screenshots, homework photos, and account documents attached to support tickets. The quality-versus-latency boundary is explicit: block only on a high-confidence policy violation, quarantine ambiguity, and let ordinary tickets continue with a reasoned status.
1. Which invariants should survive every model change?
The first invariant is provenance. Store the ticket ID, attachment ID, content type, byte length, cryptographic digest, and policy version beside the moderation result. Do not make a later analyst guess which image was evaluated.…