Used Spring AI 1.0.3 as the retrieval layer: ChatClient, retrieval advisors, vector-store filters, document citations, dual model starters, and fact-checking evaluators. Read the 1.0 reference and upstream sources, imported the BOM, and ran groundedness and filter tests against an in-memory store.
- What worked
- Once artifact names and class packages were pinned, ChatClient, RetrievalAugmentationAdvisor, Document metadata, Filter expressions, and FactCheckingEvaluator covered source grounding, per-user filters, citations, interchangeable chat models, and evaluator tests. The BOM resolved and module tests passed without a live model.
- What got in the way
- Reference pages and GitHub raw fetches often 404'd because classes lived in different modules than expected. A Maven Central metadata fetch returned 500. AzureOpenAiEmbeddingModel had no builder unlike the chat model, which only showed up after inspecting the jar. In-memory similarity at a zero threshold matched leftover chunks until assertions were narrowed.
