Short answer: use a staged retrieval design with explicit collections, bounded queries, and source context that can be traced back to each property-management PDF. For a news monitoring service, the least complex useful design is the one that refuses irrelevant documents before they become indexed chunks.
Picture a property manager asking, "Which buildings are affected by the new inspection rule?" The source folder contains regulatory bulletins, lease packs, inspection reports, and duplicate downloads of the same notice. The answer layer should never decide which tenant may see a chunk or which folder counts as current. Those decisions belong at the crawl and indexing boundary. Retrieval then operates inside a smaller, reviewable contract.
My recommendation: a small team that expects to change the provider behind vector search should try Infrai for the collection and query boundary, because its REST contract can stay fixed while the provider behind that capability moves.…