Inspiration Library: collect, group, and remove

Chat and image inspiration are content types, not layouts

Same session groups image inspiration for reading. It is not a third type and does not merge an entire ordinary chat.

Collect from the workspace

1. Open Inspiration on the message, image, or result to keep. Chat collection uses a full turn; canvas collection uses the selected creative unit or note.
2. Inspect references, prompt, and result. Upstream and downstream mean different direct relationships, not a recursive canvas backup.
3. A card output collects that result's upstream single unit. Sibling candidates are not automatically included. After an individual lightbulb succeeds, check the library; batch selection still requires explicit submission.
4. Check the saved record. Unsubmitted selections can be lost when changing session or view.

Why image collection has upstream and downstream

An image can show how it was made or what it later helped make. These are different methods worth keeping.

For A → horizontal mirror → B → annotation → C, B's upstream keeps A → transform → B; downstream keeps B → annotation → C. Neither recursively collects the whole A-to-C history.

Uploaded A has no producing operation, so upstream is unavailable. It can gain downstream once used. Final C has upstream but no downstream until reused; this is not failure.

A multi-reference node collects directly supplied operations and results, keeping required slot images without recursively following their earlier histories.

When the lightbulb is unavailable

Snapshots and their sources

The lightbulb indicates an active collection. A snapshot is not deleted just because its source enters Trash, but source location may become unavailable.

Node, prompt, and result snapshots do not automatically rewrite with every later source edit. Collected note text and appearance do synchronize with saved source-note edits; not every note is permanently frozen.

Active collections retain required images and can still use storage after the source is deleted.

Source deletion and collection removal are separate. Deleting a session, node, or note does not automatically remove inspiration; removing inspiration does not delete source content. Independently readable inspiration is not a restoration backup.

Folders, reading groups, and batch operations

• Save new or renamed folders. Deleting a folder moves inspiration to Uncategorized without deleting content.
• Choose folder, type, and search before grouping. Sorting affects reading order, not collection count.
• Details are a read-only relationship graph with pan, zoom, and reading layout. They are not a generating card workspace or edits to the original canvas.

Single unit, same chain, and same session

Collection keeps methods; grouping decides how to read them. You may inspect one step, connected attempts, or different ideas in one project without collecting again.

These views apply to image inspiration from Cards or Canvas. Ordinary chat inspiration stays one input/reply turn even under Same session.

Why the same content can show 3 items, 2 groups, or 1 group

The example collects A → horizontal mirror → B, B → annotation → C, and D → vertical mirror → E in one session. A and D look alike but are independent inputs; only the first two share B. Annotation here is an image-edit operation, not a canvas note.

Single unit shows three items; Same chain combines the first two for two groups; Same session combines all three into one. Content did not disappear. Open details rather than judge full membership from limited previews.

• Same chain uses shared source nodes, not identical pixels, filenames, or prompts.
• Different source sessions do not merge because images match. Unconnected directions in one session meet only in Same session.
• Uncollected intermediate steps are not automatically filled in; grouping uses actual shared nodes among collected units.

What filtering, moving, and removal affect

• Grouping uses active collections within the current folder, type, and search. Changing filters changes membership and count, not collected status.
• All inspiration can group members across folders. One-folder view groups only its own members; Same session does not bypass filtering.
• Moving or removing a grouped card affects all its actual members. Inspect details and confirmation. Use Single unit to handle one step.
• A collected note accompanies its anchored node when that node is in scope, even in Single unit. A standalone note or excluded target can appear separately. Use actual membership to judge scope.

Kept seven days after removal, but not restorable

Successful removal immediately leaves the active list and creates a view-only Recently removed record for seven days. Restoration is unavailable immediately, not only after seven days. This is history inspection, not undo.

Removing through Chat, Canvas, Cards, or the library removes the corresponding active collection, not just the current view. Check actual units and notes in grouped cards.

Recollection creates a new active record from an accessible, eligible source. It does not restore, rewrite, or merge canceled history. Repeated collect/remove cycles may leave several removed records.

Restore a temporarily deleted source under its own rules first. Permanently deleted sources or lost access cannot be replaced by removed-history records. Source restoration does not restore a removed collection.

Clearing or expiry removes that history from view without affecting a later recollection, the original workspace, or images other content still uses.

Recently removed records do not count as active membership storage; other active sources, inspiration, or materials can still retain the same image. Clearing history is not mandatory for freeing allowance.

Organization or intentional removal?