Artifacts & canvases

When an operator produces something — a doc, a deck, a plan, an image, a piece of code — the output is stored as an artifact. Artifacts are the primary way work leaves an operator and arrives in your hands.

Artifacts vs canvases

Same idea at the storage layer, different surfaces:

• Artifact — any output. Stored in the workspace, indexed for search, versioned across turns. Every artifact has a type (doc, code, image, csv, audio, etc.).
• Canvas — a visual artifact rendered with first-class composition tools (Canvakit). Briefs, decks, plans, diagrams. A canvas IS an artifact, but with editor support — you can rearrange blocks, change layout, embed media.

If you've used Notion or Figma, canvases sit between the two — structured like Notion, designed like Figma.

Anatomy of an artifact

Artifact
├─ id                    stable across versions
├─ title
├─ type                  doc | code | image | csv | audio | canvas | ...
├─ workspace             where it lives
├─ path                  relative path inside the workspace
├─ versions              every save creates a new version
├─ producer              the operator (or human) who created it
├─ conversation          if produced inside a thread
├─ workItem              if linked to a tracked deliverable
└─ tags                  free-form labels

Producing an artifact

You don't usually create artifacts directly — operators produce them as a side effect of doing work:

• "Draft a launch email" → operator produces a doc artifact named "Launch email v1"
• "Build a competitive analysis" → operator produces a canvas with multiple sections + an embedded chart artifact
• "Generate hero image options" → operator produces 4 image artifacts

You can also create artifacts manually — Files → New, or drag-drop into a workspace.

Versioning

Every save creates a new version. The artifact preserves history:

• Who saved it (operator or human)
• When
• What changed (diff for text, replacement for binary)

You can roll back to any prior version, branch from a version into a new artifact, or pin a specific version as the "current" reference.

Browsing & finding

The Artifacts page in the sidebar is the cross-workspace index — every artifact your guild has produced, filterable by type, producer, work item, or tag. Full-text search hits artifact bodies (for text-based types).

For visual exploration, the Canvases page shows just the canvas-typed artifacts in a grid layout — useful when you're hunting for "that brief deck the marketing operator made last week."

Sharing externally

Artifacts can be exported (PDF, PNG, raw markdown) or shared via signed URL. Signed URLs expire after a configurable window — good for sending a draft to a client without granting them guild access.

What's next

• Workspaces — where artifacts live
• Conversations — where they get produced