Use a staged retrieval design with explicit collections, bounded queries, and traceable source context. For an online course tutor, that decision is more useful than picking a vector database by headline latency: it tells you where an empty answer came from and which latency budget was spent.
I started with a simpler rule: embed every lesson, run one broad nearest-neighbor query, and hand the top results to the model. It looked tidy. It also made a bad retrieval indistinguishable from a bad answer. The fix is a retrieval contract that names the expected evidence, then measures ingestion, querying, and citation as separate stages.
What should a retrieval contract contain for a course tutor?
Start with the answer a learner should see. If the tutor must explain “how do I rotate a signing key?”, the contract needs a lesson identifier, version, audience, access scope, and a source span that actually states the procedure. “Some similar text” is not a contract.
Write the contract beside the index schema.…