agentic invoice design for reliability and performance
This is a design for invoice processing system - the focus is performance, reliability and cost and the workflow is after client made their submission, they expect to be getting json as an output for entry or every item in the invoice and then fill up their web form and then user validate if everything is ok and finally click submit. In our agent, we also have a validator but that to ensure we returning legit data. Agent is specialized and do not have too many context poisoning. If model validator checks out ok, then we proceed to move to the next - which return json results back to user. Another reason reason for this design, lets say our model is down - somewhere somehow - we are able to retain the client submission and help to processes it later. If for some reason, the default model is not able to decipher the image, model validator can try better model to see if it helps. But this can incur additioan cost. Given that the model can't recognized it, do we want to re...