A chain of filters, drills, and sorts needs to support stepping back one move and replaying it all

What it is

Exploration is a chain of operations — filters, drills, sorts, view switches — each changing the canvas. The chain must support two kinds of retreat: undo (back one step) and replay (re-execute the whole chain in order). Without undo, one mistaken filter forces a refresh-and-restart; without replay, "how did I arrive at this conclusion" stays unanswerable.

Why it happens

Undo matters more in analysis than in editing because analytical operations fail silently: a stray filter raises no error and loses no data — the canvas just quietly becomes a different scope, and the user may have said three sentences based on it already. The undo chain offers instant self-correction, compressing "notice the error, locate the bad operation, redo everything manually" into "step back once." Replay serves three deeper duties: audit (a conclusion's evidence chain can be examined step by step), teaching (others can walk the path), and self-recovery (rebuilding state on another machine or session). The engineering foundation is a history data structure — each step recorded as a reversible state transition, not just a final snapshot; snapshot-style history (keyframes only) is a performance compromise, and finer granularity replays more faithfully.

Where it stops holding

Undo semantics have two analysis-specific traps: first, undo applies to operations, not data — undoing a filter clears no data, it removes one step; second, undo and roll-up (level retreat) are separate primitives (per the drill-down group's conclusion), and conflating them destroys the user's sense of "what exactly did I just back out of." History length has a practical cap — infinite history wastes resources and is unnavigable; the common shape is full session history plus a visual timeline for jumping. Collaborative undo semantics are complicated (undo someone else's operation?), and most products choose "undo only your own" with explicit labels.

Applying it

• Log every analytical operation into history: filters, drills, sorts, view switches all undoable, with shortcuts.
• Provide a session timeline supporting jumps to any step and full-chain replay.
• Verification: have a user perform ten exploration steps, undo five, then replay; every step's canvas must match the first run — any lost step means the history granularity is insufficient.

Related

• Same group: U6.11.2 State must be shareable with others · U6.11.3 The exploration path itself is an analytical product
• Nearby: U6.05.2 Roll-up needs a return path as explicit as drill-down · U6.10.1 Analytical state must be encodable as a reproducible link or snapshot
• Search terms: undo redo analysis · operation history · provenance replay