A useful retrieval system begins with source ownership. Teams need to know which material is authoritative, how quickly it changes, and who may see it.
Evaluation should represent real user questions, difficult edge cases, and permission boundaries. A single relevance score cannot describe the whole product experience.
Production architecture also needs graceful degradation. When retrieval is weak or a model is unavailable, the product must explain uncertainty and offer a safe next action.