01.1
One session, many signals
Expert computer work is rarely a straight line. The useful material lives in the cursor path, the file changes, the window switches, the spoken rationale, and the moments where the operator pauses to inspect the result.
Captured together, those signals form a coherent account of the work instead of a loose collection of telemetry.
01.2
Time is the spine
Every interaction is attached to one shared clock. A comment at 14:08 can be read beside the visible frame, the application event, and the exact file snapshot that followed.
That temporal spine is what makes a long professional workflow searchable, replayable, and suitable for evaluation.
01.3
Keep the artifacts
The finished file is not a side effect. It is part of the demonstration. A capture system has to preserve deliverables, intermediate versions, and the environment state that produced them.
This is especially important in creative and technical applications where the work cannot be reconstructed from keystrokes alone.
01.4
Make it replayable
A useful recording should answer a practical question: can another system return to the same point and continue? Restore points turn a passive observation into an environment where a model can practice.
That is the bridge from imitation data to active learning.