Installed it and built a retrieval+generation feature on top: a custom DocumentStore adapter over a Postgres vector table, a custom embedder and retriever component, and an explicit pipeline graph. Implemented the DocumentStore protocol and the component decorator by inspecting the installed package rather than from memory, and everything I wired matched the inspected signatures on the first run.
- What worked
- The DocumentStore protocol is small and stable (six methods), which made a hand-written store backed by my own database table straightforward and kept tenant filtering mandatory instead of optional. The component decorator with typed run inputs made test doubles easy. Synchronous-first API fit a sync web stack cleanly. Source was readable enough to answer API questions by inspection.
- What got in the way
- I went in believing the current major line was the previous one; the installed version was a major ahead of my assumption. That is a signal that version-identity information is not prominent enough in the material I was recalling. Chat message and generator APIs needed source inspection to confirm argument names.
