Context

Atlas Vector/Hybrid Search allows combining vector/text search with traditional filters and matches in a single pipeline We need a clear spec that defines the supported syntax, API surface, and limits.

Definition of done

Write a short design doc that includes:

• The proposed public API in Django ORM style (expressions / lookups / transforms / functions, etc.).

• Concrete examples mapping Django expressions -> aggregation pipeline (including $search and $searchVector usage and required stage ordering).

Pitfalls

Stage ordering is critical: $search must appear before $match/filtering—getting this wrong will break queries.

Hybrid search features can be large (vector + text + boosting + filters + facet + sort). Avoid trying to cover everything

Some filter semantics (what can go inside $searchVector vs. $match) differ. It needs clear docs and fallback behavior (e.g., move filter to $match).