Cards and Canvas: two views of the same creation

Not separate works or generation capabilities

Cards arranges inputs, operations, and outputs into records. Canvas displays those same objects and connections. Generation, tools, continuation, favorites, inspiration, and deletion affect the same formal content, with identical credits, storage, and share permissions.

Cards suits reading and editing steps. Canvas suits checking shared sources, branches, and downstream deletion scope. Switching is not generating twice.

A record represents an AI generation or image edit with its real input, settings or tool, prompt, and outputs. Several results from one operation stay in the same record.

Add generation or editing drafts separately at the end. An established operation cannot change into the other type; create another record.

Completed records offer summaries, enlarged prompt reading, regeneration, canvas location, and result actions. Draft submission availability depends on current inputs and settings.

**The same tutorial step in Cards**
Input, tool, and formal output correspond to the same sources, operation, and result in Canvas, not another set of files.
Actual interface · Tutorial example, not your account

**Real editing results retain their sources**
Horizontal mirror produces one result, followed by annotation. Connections show direct relationships and each original input remains.
Actual interface · Tutorial example, not your account

Which actions create formal nodes and connections

Action	Effect
Empty draft, unsent prompt edit, preview, or layout change	No generation result or generation connection is created by these actions alone.
Select images in a new generation card	A formal multi-reference input is created before the picker opens. Canceling does not undo that empty input. Confirmed images enter its slots; generation has not yet started.
Submit text-only generation	Prompt and the requested number of output nodes and connections appear immediately. Waiting for server acceptance is not generation in progress. No image input node is needed without references.
Generate from an existing input card	Input connects to this prompt, then to outputs. The input locks to preserve the used combination.
Continue from an existing result and submit	That existing image remains the source of a new prompt and outputs. Reuse does not necessarily duplicate the source node.
Combine sources or independently choose history/materials	The new combination becomes an input. Independent file selection does not automatically link to an old creative step; explicit canvas references do.
Execute split, transform, annotation, or outpaint	Retain the input and connect a new operation and results. Merely switching tools or preview settings is not execution.
Regenerate a submitted record	Reuse its input relationships and add candidates rather than overwrite results. Paid requests are rechecked and settled again.

Why the same image can appear in two nodes

A file is material; a node is its use in this creation. Separate card inputs have separate identities even when they reference the same saved file. They retain their own ordering, local-edit intent, and purpose instead of merging because images look alike.

A product photo used for a poster in card A and packaging in card B has separate input relationships. Deleting A's independent input affects A's downstream, not B because the photo looks identical. If both explicitly share one canvas source node, deleting that source may affect both branches.

Repeating an image in one multi-reference input usually creates two slots, not necessarily two image nodes. It does not guarantee increased weight and uses reference allowance; remove unnecessary duplicates.

Reusing a saved file does not store another original. Two fresh uploads cannot be assumed to share storage just because they look identical. Nodes, image count, and stored bytes are different concepts.

**Identical-looking images can be independent nodes**
Two separately placed tutorial inputs have separate identities and no creation connections. Appearance does not establish a shared source.
Actual interface · Tutorial example, not your account

Adapt reading and editing to your device

Interface switches layouts such as Desktop, Simple, Compact, and Minimal. Collapse or expand changes reading density; search and filters change only the visible scope.
Adjust record height or enlarge a record for long prompts and multiple images. Uniform height helps comparison; free height opens particular steps further.
Rearrange adjustable panels. Layout and unsent drafts are local workspace interface state, not commands that change collaborators' layouts.
Expanding opens a near-full-screen editor for the same content. Closing returns to the record.
Read-only favorite cards offer viewing, not generation or editing permission.