Chose this managed search and conversation layer from official docs so the app would not own chunking, embeddings, citations, sessions, or index refresh. Wired answer queries, metadata filters, follow-up sessions, and incremental imports in code, but never created an engine or issued a live query.
- What worked
- Documentation and samples described grounded answers with citations, server-side conversation state, serving-config paths, and incremental document import from object storage, which matched the requirement to stay off a custom retrieval stack.
- What got in the way
- It took several doc and search passes to settle session creation versus placeholder session ids, filter syntax, JSONL metadata for imports, and how search options are attached to an answer request. Live serving, sync, and citation quality were not observed.
