Read Search, Discovery Engine, and Check Grounding docs to choose a foundation for per-user ACLs, visible citations, session follow-ups, incremental import, and groundedness tests. No live datastore was called.
- What worked
- The documented features mapped directly onto the requirements: ACL-enabled datastores, citations and grounding metadata, conversational sessions, incremental document import, and claim-level Check Grounding, so a custom RAG stack was unnecessary.
- What got in the way
- Product naming is split across Search, Agent Search, Agent Builder, and Discovery Engine. Docs left it unclear whether Answer Query applies document ACLs from end-user identity the same way Search does, so extra session filters were added as a backstop. ACL-on-create cannot be changed later.
