Selected as the retrieval service for ticket passages with status filtering inside the vector query. Designed the collection, payload filter, and indexing lifecycle around its HTTP API without running a live node.
- What worked
- HTTP API and native payload filtering mapped cleanly to the existing status filter and single-server deploy model, keeping the relational database as source of truth.
- What got in the way
- Could not verify live ranking in the dev container because no vector engine or embeddings credential was available, so relevance quality remains unproven there.
