Keep human-readable window labels tied to exact boundaries — what should the operator record?
A table label can outlive the moment when a relative phrase was meaningful. Recent and last week are especially easy to misread when a saved artifact is opened later. Resolve display labels against the original request context and preserve exact boundaries where available, without inventing timestamps that the evidence did not actually provide.
Prevent labels such as recent or last week from drifting away from the implemented evidence interval.
Store requested_window_text and request_context_time when known. Preserve the actual user wording because replacing last week with a guessed date range can silently remove ambiguity rather than resolve it through the appropriate scope decision before the table is used downstream.
Prefer the approved explicit window beside the original relative phrase where useful. Keep unknown timestamp precision and returned coverage separate, avoiding the implication that a well-defined requested interval guarantees exhaustive records for every instant or calendar day inside it.Capture the original phrase
Store requested_window_text and request_context_time when known. Preserve the actual user wording because replacing last week with a guessed date range can silently remove ambiguity rather than resolve it through the appropriate scope decision before the table is used downstream.
Resolve with an explicit rule
If the team has a legitimate agreed interpretation, record resolved_start, resolved_end and interpretation_zone. If it does not, mark ambiguous-window and seek clarification rather than selecting the host computer's calendar week convention or assuming every source uses the same reporting zone.
Test reopening later
Use a labeled saved artifact with a fixed resolved interval and simulate viewing it on another date. Its heading should still identify the original interval, not recalculate last week relative to the new viewing date and thereby misrepresent the same underlying evidence.
Reconcile displayed and actual scope
Compare the heading, manifest and transformation predicates for the current revision. A clear label is still wrong if the filter used different boundaries, so retain any mismatch as a release blocker instead of editing only the text to look consistent.
Publish stable labels
Prefer the approved explicit window beside the original relative phrase where useful. Keep unknown timestamp precision and returned coverage separate, avoiding the implication that a well-defined requested interval guarantees exhaustive records for every instant or calendar day inside it.
Keep the boundaries clear.
- Prevent labels such as recent or last week from drifting away from the implemented evidence interval.
- Operational record: Capture the original phrase. 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.