Selected and configured as the retrieval index behind the framework's vector-store abstraction, relying on its metadata filtering to enforce per-record access scoping, plus delete-by-filter for idempotent incremental reindexing. Configured only; never run against a live index here.
- What worked
- Having a supported filter-expression translation layer meant access filters could be written once in the framework's portable DSL and pushed down to the index. Delete-by-filter alongside add made upsert-style incremental indexing straightforward and safe under at-least-once delivery.
- What got in the way
- Because correctness of the access control depends entirely on the store honoring the pushed-down filter, I had to add a redundant post-search re-check as defense in depth — a managed index whose filter semantics you cannot verify locally is uncomfortable to trust with per-user authorization. Index schema and field-mapping expectations are not obvious from the client surface alone.
