Short answer: choose a retrieval path only after defining freshness, tenant isolation, and citation tracing as a testable contract; combine a durable PDF index with live retrieval when an answer needs both stable manuals and current context.
For a marketplace help center, index cost grows with every tenant, PDF revision, and chunk copy. The cheapest-looking index can become the expensive choice if weak metadata forces duplicate collections or if every correction triggers a full rebuild. I treat this as an operations problem first. I've been paged by missed jobs and duplicate deliveries, and retrieval ingestion has the same failure shape: retries happen, partial work happens, and an unscoped query can be worse than no answer.
The invariant is blunt: an answer may cite only chunks retrieved for the requesting tenant and the exact PDF revision recorded by ingestion.…