Assets, provenance, and versions

Artifact or file

An artifact is a durable document produced by a capability, tool, or agent. A file is a durable non-document output such as a generated image, logo, SVG, or upload. Both live in Assets.

Drafts stay private to their Chat

A capability-created document begins as a draft. It remains addressable from its message but does not enter Assets, search, MCP reads, project summaries, or downstream context until Save to Assets. Saving promotes the same record rather than copying it.

Provenance

Saved outputs record whether they came from a user, tool:<id>, or agent:<id>, plus the owning Chat/task, selected model or engine, references, and revisions. Image files preserve prompt, model, ratio, and reference lineage.

Local and cloud storage

Assets follow their actual storage location, project roles, review-target rules, and quotas. Machine-local image files can remain under the bound workspace while the online studio stores project and Design metadata. A local project is not a promise that all artifact metadata stays on the Mac. Sharing a saved target for review does not grant access to the whole source folder or Assets inventory.