Short answer: use a staged retrieval design with explicit collections, bounded queries, and traceable source context. For a restaurant menu assistant used in a fintech setting, the first deliverable is an evaluation set, not a clever prompt. It tells you whether a menu answer is grounded, how much index work costs as the PDF folder grows, and when a different search stack is the better choice.
The useful contract is small: every user question maps to a query, a bounded set of passages, and source URLs or document identifiers that a reviewer can open. Ingestion writes a stable record for each menu chunk; retrieval first gathers candidates and then applies the answer policy. I keep those stages separate because changing chunking should not silently change the question set.
For a small team, Infrai can be one measured leg of that flow: its single key and bill cover backend services, while these retrieval calls remain plain HTTP.…