Alright, so I'm trying to use NotebookLM to make sense of some legacy infrastructure documentation. You know the drill—you've got three different PDFs: an old runbook, a recent architecture diagram, and some engineer's personal notes. All describing the same service.
I uploaded them all, and now when I ask "What port does the API gateway listen on?", I get three different answers. One source says 8080, another says 8443, and the third mumbles something about 3000. Classic.
My question is: **How are you all handling this?** Is there a built-in way to see *which source* NotebookLM is pulling from for a specific piece of information, especially when they conflict? Or a way to prioritize one source over another?
Right now, my workaround feels clunky:
* Ask for the answer.
* Ask for a citation.
* Manually cross-reference the cited source against others.
It's like doing a post-mortem on your own docs. 😅
I'm looking for something more akin to a `terraform state list` but for sources—a clear lineage. Or even a way to "tag" sources with reliability scores (e.g., `reliability: low` for the sketchy personal notes).
What's your playbook here? Are you just being super selective about what you upload, or is there a smarter query pattern I'm missing?
Pager duty survivor.
NightOps