Sharing an analysis should hand someone a live state they can keep exploring, not a frozen screenshot

What it is

Traceability ends at sharing: what others receive should not be a final screenshot but a state they can enter and keep operating — your filters intact, your level intact, others free to explore onward. Sharing turns private exploration into the team's shared working surface; screenshot-only sharing compresses exploration into a single unverifiable image.

Why it happens

Shareable state earns its keep on three concrete needs of collaborative analysis: verification — colleagues must be able to check "can I walk to your conclusion myself," impossible with a screenshot; relay — analysis is a relay race, one analyst hands the baton mid-descent and another continues, and the handover of state is the handover of work; and discussion anchors — "everyone open this state" in review meetings requires the state to be reachable for all. Technically this shares roots with bookmark sharing (serialised state encoding); the difference is collaborative semantics: a shared state is the starting point of someone else's working surface, so it needs explicit copy semantics (the recipient's continued exploration leaves the original untouched) and permission semantics (the permission-divergence problem from the bookmark group). Real-time collaboration (multiple people inside one state session) is the further form, and it rests on the same foundation of encodable state.

Where it stops holding

The boundaries of shared state concentrate in permissions and freshness: permission-driven data divergence (argued in the bookmark group) and data-update staleness (argued there too) both amplify in collaborative contexts — a state link cited by three people that quietly changes leaves all three discussions without a common ground, so collaborative sharing leans toward snapshots. Copy semantics also need clarity: default to "each edits their own copy, no interference," with explicit entry into a collaborative mode when joint editing is wanted.

Applying it

• Make the analysis view's share action produce "an enterable state" (link or workspace copy) rather than a static export, while keeping image export as an option.
• State the copy semantics at share time: "the recipient gets an independent copy."
• Verification: have a colleague enter the state via the share link and explore one step further; the original must be unaffected and the colleague able to continue — anything less degrades the share to a screenshot.

Related

• Same group: U6.11.1 The analysis process must be undoable and replayable · U6.11.3 The exploration path itself is an analytical product
• Nearby: U6.10.4 A share-link recipient may see different data due to insufficient permissions · U6.10.1 Analytical state must be encodable as a reproducible link or snapshot
• Search terms: collaborative analytics · shared state · analysis handoff