Version a query without erasing its original wording — what should the operator record?
A useful follow-up often changes the scope of a question, not merely its phrasing. Once the wording changes, the earlier evidence should still be traceable to its own request. Keep revisions explicit so a collaborator does not accidentally cite a broad follow-up as evidence for the original narrower request.
Record query revisions and reasons so later results retain their actual retrieval context.
Create query_revision q1 with exact_text, requested_window and declared_sources before drafting a follow-up question in another working document. Keep the user's hard constraints in the revision record, including a requested exact count, rather than preserving only a convenient short query title.
Point the table manifest to q2 only after the owner accepts the new scope, preserving q1 as a separate permitted lineage reference. If q2 changes an explicit user constraint, the original requirement remains authoritative until the appropriate owner approves that scope change rather than silently accepting it.Save the first wording
Create query_revision q1 with exact_text, requested_window and declared_sources before drafting a follow-up question in another working document. Keep the user's hard constraints in the revision record, including a requested exact count, rather than preserving only a convenient short query title.
Record the revision reason
For q2, specify whether the change fixes a typo, clarifies an entity or expands the requested window; do not use one generic updated label. A typo fix and a source expansion may both improve results, but only the latter changes the intended evidence scope and needs explicit scope acceptance.
Compare returned membership
Join each actual response to its own revision and list source keys appearing in only one response without assuming those records were unavailable globally. Use an overlap table with q1_present and q2_present flags; do not replace those flags with a single merged relevance score that hides query ancestry.
Inspect scope drift
Read several changed rows against q1 and q2. Distinguish a better phrase match from a genuinely expanded eligible evidence window. A newly returned row can be newly ranked or newly accessible rather than newly published; compare available timestamps before explaining why the membership changed.
Select a working revision
Point the table manifest to q2 only after the owner accepts the new scope, preserving q1 as a separate permitted lineage reference. If q2 changes an explicit user constraint, the original requirement remains authoritative until the appropriate owner approves that scope change rather than silently accepting it.
Keep the boundaries clear.
- Record query revisions and reasons so later results retain their actual retrieval context.
- Operational record: Save the first wording. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.