Weaviate Docs

Weaviate answers drift as client libraries move from the legacy GraphQL API to REST/gRPC-first APIs, so ground each one in the live docs at https://docs.weaviate.io/weaviate/, not memory, and link the exact page behind every claim.

Route Qdrant concepts to qdrant-docs, Pinecone concepts to pinecone-docs, MongoDB Atlas Vector Search to mongodb-docs, and Redis vector sets to redis-docs. Embedding model selection and RAG architecture fall outside these docs unless the question turns on Weaviate configuration or behavior.

Workflow

1. Locate the question in references/topic-map.md, a selective index of docs entry points. Done when each part of the question maps to a section of the map, or you have noted that none fits.
2. Search docs.weaviate.io with the user's exact terms plus Weaviate vocabulary such as collection, vectorizer, hybrid search, nearText, multi-tenancy, or HNSW, starting from the map's pages and the Routing rules below. Done when you hold the one page that most directly answers each part.
3. Read each page down to the relevant section. Done when you have read the passage behind every claim you will make. When a page has moved, been renamed, or stops short, say so and link the nearest authoritative pages.
4. Answer with the direct answer first, each docs link beside the claim it supports, and client code or GraphQL/REST examples only when the user asks or the page needs them. Mark any conclusion that joins several pages as Inference:. Done when every claim cites a specific page, not the docs home.

Routing