stamp

What is a Stamp?

A stamp is a snapshot of a workfloww at a meaningful moment. It is the primary unit of history in floww. When Claude completes a task, branches a conversation, or reaches a decision point, floww creates a stamp that preserves the current state — the canvas layout, node positions, conversation history, and context.

In version control terms, a stamp is analogous to a commit. But stamps go beyond simple file snapshots. A stamp includes a context-aware audit that examines the codebase and project structure before sealing the snapshot. This makes stamps intelligent — they understand what changed and why, not just that something changed.

Auto-Stamping vs Manual Stamping

Stamps can be created automatically or manually:

• Auto-stamps are created by FlowwTerminal nodes when meaningful events occur — a task completes, a branch point is reached, or an error is resolved. The system decides when a moment is worth preserving.
• Manual stamps are created by the user when they want to explicitly mark a point in their work — before trying a risky change, after reaching a milestone, or when switching context.

What a Stamp Captures

Each stamp records:

• The state of all nodes and connections on the canvas
• The conversation history in active FlowwTerminal nodes
• File changes associated with the workfloww
• A human-readable summary of what changed and why
• The timestamp and workfloww context

Stamps are immutable once created. You can browse historical stamps to see how a workfloww evolved, compare stamps to understand what changed between moments, or restore a previous stamp to return to an earlier state.