Overview
Use hybrid search when answers need both keyword precision and semantic recall.
Filter by hidden tenant context before ranking.
Attach retrieved chunks to evidence bundles.
In the browser SQL sandbox, you can run direct SEARCH ... USING HYBRID(...) queries with literal query/filter values. You do not need to create session bindings just to inspect your own indexed rows.
Developers do not need to pull external model embeddings into app code for the documented path. Define searchable tables/indexes and call SEARCH or HYBRID_SEARCH from contexts and capabilities; Synapsor handles the governed retrieval path and returns evidence lookup records.
Hybrid Plan Index metadata keeps retrieval strategy inspectable: developers can analyze indexes, explain search decisions, and inspect plan cells without moving retrieval planning into app code.
Developer notes
- Use direct SEARCH ... USING HYBRID(...) in the browser SQL sandbox for owner/operator inspection.
- Always filter by hidden tenant_id or entitlement context.
- Use hidden SESSION bindings for app-facing capabilities so tenant, principal, and role values are trusted.
- Do not call external embedding APIs from request-time app code just to use Synapsor hybrid search.
- Cap top_k per plan to control cost.
- Record chunk ids and versions in evidence.
- Rebuild embeddings through a governed background job.