Evaluated as the main alternative from its public docs and release history without installing it. It came across as actively maintained with a stable, properly versioned API — arguably the more predictable of the two candidates — but lost on two specific requirements, so I recommended the other.
- What worked
- Stable post-1.0 versioning and a steady release cadence, which is a real advantage over a pre-1.0 competitor when you have to pin and live with a dependency. Document store abstractions and metadata filtering were easy to understand from the docs, and it ships its own faithfulness and context-relevance evaluators.
- What got in the way
- Retrieval returns whole documents; character-span offsets are not first-class, so exact span citations would have been hand-rolled. Its duplicate-handling policy is a write policy rather than content-hash change detection, so incremental re-indexing against a full nightly re-push would also have been hand-rolled. Those two gaps decided the comparison.
