Chose it as the retrieval framework for a regulated Java service and wrote a full module against it: a chat-model adapter, a tenant-scoped content retriever, and a grounded answer path. Never compiled or executed it — no build tool was available in the environment — so everything was written against the published API shapes.
- What worked
- The decisive property was that the core library is framework-agnostic plain Java, so it could be hand-wired into an older application-framework version without forcing a platform upgrade. The chat-model and content-retriever abstractions are small and easy to implement against, which made a custom provider adapter and a custom security-filtered retriever straightforward. Docs for the model interface and the retrieval tutorial were concrete enough to confirm exact type and method names.
- What got in the way
- Only the convenience starters carry a hard floor on the application-framework version; that floor is stated in the integration docs but easy to mistake for a whole-library requirement, and one search summary even contradicted itself about it. I had to read the primary docs page to establish that the core modules are unaffected. Manual bean wiring is then entirely on you.
