Get grounded answers across your connected Google Workspace, with a real source for every claim

Answer this using only what you can actually find across my connected Google Drive and Gmail — do not fill a gap with a plausible guess, and do not answer from general knowledge about how this kind of thing usually works if the connected sources themselves don't say it.

QUESTION
What did we actually agree with the Meridian account on renewal pricing for next year, and has that been confirmed in writing by them?

WHERE TO LOOK
Drive folder 'Meridian Account' and any Gmail thread with meridian in the sender domain, from the last 6 months. If the question could plausibly be answered from a source outside this scope that you also have access to, say so and ask whether to widen the search, rather than silently expanding scope on your own or silently ignoring a source that might have the answer.

SENSITIVITY BOUNDARY
Do not surface anything from the 'HR' or 'Legal - Privileged' Drive folders even if they technically match the search scope.

WHAT TO PRODUCE
1. The direct answer, stated first, with every specific fact — a date, a name, a number, a decision — tagged with exactly which document, email, or event it came from. Use enough detail in the citation that I could find that exact source myself (document title, sender and rough date, or event name), not just "according to a document I found."
2. If multiple sources give different answers to the same question — an old email says one date, a more recent doc says another — name both explicitly with their sources and say which one looks more current, with your reasoning, rather than picking one silently.
3. A section titled NOT FOUND — any part of the question the connected sources genuinely don't address. This matters as much as what you did find; a partial answer presented as complete is worse than an honest gap.

CONSTRAINTS
- If search across the connected sources returns nothing relevant at all, say that plainly as the entire answer — do not pad it with generic advice or a guess dressed up as a finding just to have produced something.
- Do not treat an old, superseded document as current just because it's the first or most complete-looking match — check for a more recent version or a follow-up thread before presenting an older source's claim as the current state of things.
- If a source was recently modified in a way visible to the connector — a document edited in place, an email thread with a later reply — prefer the most recently touched version of the record over an earlier one with the same title, and say which timestamp you used to decide.
- A signed contract or an email explicitly confirmed by their side outranks an internal proposal doc or a draft, even if the draft is more recent.

IF YOU'RE UNSURE WHETHER A SOURCE IS RELEVANT
Include it with a note on why it might be relevant but uncertain, rather than silently excluding a plausible source or silently including it as if it were a confirmed match — the uncertainty itself is useful information, not a reason to hide the source either way.

OUTPUT LENGTH
Under 200 words, plus the NOT FOUND section if needed — this needs to be skimmable before a call, not a full case history.