GistBoard's recording model took a different route from ordinary screen capture. Instead of making a video the primary record, the recording foundation created a timeline of meaningful changes inside the deck.
A recording session stores lifecycle events, tile changes, layer changes, and references to saved drawing snapshots. Each event has a relative time and deterministic sequence. The references point back to stable deck objects, allowing validation to detect a missing tile, layer, or snapshot before replay begins.
This makes replay a reconstruction of the explanation's state. The user can move from one tile to another, change the active layer, and reveal a new drawing state without flattening the editable deck into pixels. Later video export can be generated from that record, while the package remains the source of truth.
The current model captures drawing snapshots rather than a complete editable history of every stroke. That keeps local replay and package validation manageable, but it does not claim the fine-grained temporal fidelity of a full stroke event stream.
← Back to GistBoard