Classify before retrieving
A domain system benefits from knowing what kind of question it is answering before searching. Classification gives retrieval a narrower job and makes metadata constraints explicit instead of hoping similarity search discovers the right context on its own.
Treat ingestion as its own system
Documents, long-form video and structured entity data arrive through different pipelines. Asynchronous workers keep ingestion, parsing, embedding and indexing away from interactive request latency while making retries and failure states observable.
Keep provenance attached to context
Retrieval is not useful enough if the product cannot explain where an answer came from. Source metadata survives the pipeline so the generated response can remain tied to inspectable evidence.
Design for multiple knowledge spaces
The system evolved beyond a single vector collection. Retrieval planning and metadata filters allow questions to be evaluated against the appropriate project or knowledge base rather than searching everything indiscriminately.