Chose it as the retrieval/model-abstraction layer for an existing Java service and used it narrowly as a provider adapter: the chat and embedding model interfaces plus two provider modules, with retrieval, scoping and citation checking written by hand. Added the three artifacts under one shared version property and wrote all code against it, but could not compile because the environment had no JDK or build tool.
- What worked
- Core is plain Java with no web-framework coupling, so it dropped into an older framework baseline that the main alternative would have forced an upgrade for. The model interfaces are small and stable, the provider modules expose clean builders, and one of them supports token-credential auth so no API key had to live in config. Core and provider modules release in lockstep, so a single version property keeps them aligned.
- What got in the way
- Published docs and the package registry disagreed on the current version, so the pin had to be flagged as unverified. The published tutorials lagged behind the code, which pushed me to read interface definitions out of the main branch instead — those may be ahead of any release. One embedding-model builder had no documented example, so its signature was inferred from a sibling class and remains the likeliest thing to break at build time. The metadata filter abstraction also felt too loose for a hard access-control boundary, so I avoided implementing its store interfaces.
