Summary

The previous docs site had three dedicated pages — Equality, Match, and Order / Range — under platform/searchable-encryption/supported-queries/{exact,match,range}/. These were the practical "what query do I want, what index do I create, what does the SQL look like" reference. The new docs absorb fragments of this into reference/eql-guide.mdx and cipherstash/encryption/searchable-encryption.mdx, but there's no per-query-type landing.

This pairs closely with #4 (CREATE INDEX guide). #4 is the table of which index for which query; this issue is the per-query reference page that explains the semantics, operators, and gotchas for each query type.

What's missing

The old pages each covered:

• Which JS/SDK predicate or SQL operator triggers the path
• Which index type underpins it (unique / match / ore / bloom_filter / ste_vec)
• Worked SQL examples
• Performance characteristics and caveats

Suggested page structure

Either three pages under content/stack/cipherstash/encryption/queries/{equality,match,range}.mdx, or one expanded page cipherstash/encryption/queries.mdx with three top-level sections. Each section needs:

• The user-visible operator(s) — both SDK predicates and raw SQL forms
• The underlying EQL index it uses
• A working SELECT example
• Cross-link to the corresponding CREATE INDEX row from docs: add CREATE INDEX guide for encrypted columns (self-hosted vs Supabase paths differ) #4
• Self-hosted vs Supabase differences where they exist

Reference material

• Old pages live in cipherstash-js-suite git history at apps/docs/src/app/(articles)/platform/searchable-encryption/supported-queries/{exact,match,range}/page.md (commit 1c3d40ed^).
• EQL repo's per-operator reference under docs/reference/.

Out of scope

• Index creation SQL — covered by docs: add CREATE INDEX guide for encrypted columns (self-hosted vs Supabase paths differ) #4. This issue is the operator/predicate reference; docs: add CREATE INDEX guide for encrypted columns (self-hosted vs Supabase paths differ) #4 is the index reference. The two should cross-link.