Stop a page chain when workspace context changes — what should the operator record?
An operator can change workspace context while a result chain remains open. Continuing under a different context risks confusing evidence lineage and access boundaries even if a request returns something. Treat context continuity as a gate, and never use another person's session or token to force the chain forward.
Prevent continuation receipts from being mixed across accounts or workspaces during a handoff.
Store a nonsecret workspace reference and originating query revision with the first accepted page, keeping authentication material outside the evidence ledger. An internal alias is enough for a handoff if the receiver can verify it through normal controls; avoid account email addresses in general pagination logs.
Require the receiving operator to confirm context and access before any continuation, with blocked-context as a distinct stop reason. The handoff checklist should identify the blocked chain and allowed next check without including a token that another operator could mistakenly reuse under their identity.Pin the chain context
Store a nonsecret workspace reference and originating query revision with the first accepted page, keeping authentication material outside the evidence ledger. An internal alias is enough for a handoff if the receiver can verify it through normal controls; avoid account email addresses in general pagination logs.
Compare the active context
Before continuing, verify that the authorized workspace matches the chain's recorded context through available read-only account or response information. If workspace identity cannot be established from permitted information, mark context-unverified and stop rather than assuming the active client still uses yesterday's account.
Quarantine mismatched receipts
If a page was returned under a different workspace, keep it out of the original table and ask its authorized owner to review it. A mismatched page may be legitimate evidence in another authorized workspace, but it must not inherit the original chain's provenance or recipient audience.
Resume only legitimately
Return through the normal authorized workspace workflow or begin a new approved chain; do not transplant tokens between identities. Normal reauthorization may require the account owner; the operations runbook should name that boundary instead of treating session transfer as a routine recovery step.
Document the handoff gate
Require the receiving operator to confirm context and access before any continuation, with blocked-context as a distinct stop reason. The handoff checklist should identify the blocked chain and allowed next check without including a token that another operator could mistakenly reuse under their identity.
Keep the boundaries clear.
- Prevent continuation receipts from being mixed across accounts or workspaces during a handoff.
- Operational record: Pin the chain context. 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.