Chose it as the retrieval framework after comparing maintained options, then wrote an indexing and answering pipeline against it plus its vector-store, Anthropic and Google generator integrations. Could not install it in the offline sandbox, so all code was written from the published API reference and two tests were skipped; the rest of the suite was structured to run without it.
- What worked
- The explicit component-graph model gave one obvious place to inject retrieval filters, which was exactly what a multi-tenant access-control requirement needed. Document writing with an explicitly set id made incremental upserts straightforward. The built-in faithfulness and context-relevance evaluators accept an injected chat generator, so the judge could run on a chosen provider rather than the default one. Generator swapping across two vendors was a constructor change, nothing more.
- What got in the way
- The retriever's default filter policy replaces constructor filters with run-time ones instead of merging them — a quiet security footgun that only surfaced by reading the reference closely. Docs and published releases disagreed on the current version, and one docs example imported a helper from the wrong module. The core package pulls in an unrelated vendor's SDK even when that vendor is unused, which is awkward in a privacy-sensitive deployment. A recent major version bump left some doc pages on the old line.
