> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gobihq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Artifacts

> The platform's content object: what it holds, the kinds, and where notes fit.

An artifact is one finished thing made out of what Gobi captured: a meeting summary, a report, an image. It is the container the platform keeps creations in, and the mobile app's **notes** are one kind of artifact.

Artifacts are always human-owned, and they live in your **Home**. `gobi personal artifact …` is the only scope: an artifact is visible to you until you attach it to a post.

## What an artifact holds

Content and a revision history. Nothing else. An artifact is a snapshot you hand to someone, so it carries no live state of its own: no counters that tick, no fields a reader edits, nothing that changes unless somebody records a new revision. Anything that has to keep moving belongs in a space, as posts.

That boundary is what makes an artifact safe to send. What the recipient opens is what you handed over.

## Kinds

| Kind                      | Made by                               | Body                           |
| ------------------------- | ------------------------------------- | ------------------------------ |
| `note`                    | the mobile app from a capture, or you | markdown with YAML frontmatter |
| `markdown`                | you or an agent                       | markdown                       |
| `image` · `gif` · `video` | you or an agent                       | an uploaded file               |

`artifact create --kind` takes all of them: `image`, `video`, `gif`, `markdown`, `note`.

### Notes are artifacts

Capture a conversation in the mobile app and you get an artifact of kind `note`. The app calls it a note because that is what it is to the person who recorded it; the API calls it an artifact because that is the object it is stored as. Both are true, one level apart.

A note's frontmatter carries what the app knew about the capture:

```yaml theme={null}
---
title: Coffee with Dana from Cintra
activity_id: 412
category: sales
source: mobile
start_time: 2026-07-01T11:48:00.485Z
end_time: 2026-07-01T13:12:18.874Z
duration: 84 min 18 sec
attendees:
  - Dana Lee
  - Ada Nicodemou
---

## Summary
…
```

Example data. `source` tells you what made it, and `activity_id` links it back to the capture it came from.

## Create

```sh theme={null}
# markdown from a file, stdin, or inline
gobi personal artifact create --kind markdown --file notes.md
echo "# Draft" | gobi personal artifact create --kind markdown --content -

# media kinds upload a file
gobi personal artifact create --kind image --file chart.png

# attach to a post at creation
gobi personal artifact create --kind markdown --file summary.md --post-id 1234
```

`--title` sets the display title. `--vault-slug` anchors `[[wikilink]]` resolution for markdown bodies, and `--auto-attachments` uploads the wiki-linked files to webdrive before creating.

## Revise

```sh theme={null}
gobi personal artifact revise <artifactId> --file v2.md                 # record a revision
gobi personal artifact revise <artifactId> --from <revId> --file alt.md # branch off a revision
gobi personal artifact revert <artifactId> --revision <revId>           # restore an earlier one
gobi personal artifact history <artifactId>                             # the full tree, owner only
```

Revisions form a history tree, and **the newest node is what the artifact reads as**. `revert` copies an earlier revision's content forward as a new revision, so the trail stays intact.

The tree is what lets an agent draft while a person stays in charge. An agent pulls context, writes a revision, and stops; you read it, ask for a change, and it revises again. Each `--change-note` is the reason that revision exists, so `history` reads as the argument that produced the document.

## Read and remove

```sh theme={null}
gobi personal artifact list                  # newest first, --kind to filter
gobi personal artifact get <artifactId>
gobi personal artifact download <artifactId> --out ./file   # current revision by default
gobi personal artifact delete <artifactId>   # deletes the artifact and its revision tree
```

`download --revision <revId>` pulls a specific one instead.

## Sharing one

An artifact stays in your Home until you attach it to a post:

```sh theme={null}
gobi space create-post --content "Notes from today" --artifact <artifactId>
```

There is no space-scoped artifact. Attaching to a post is how one reaches a team.

<Note>
  `artifact` is the platform-level object. In the mobile app you meet the same object under the name it uses there: a capture becomes a **note**. See [notes](/notes/overview) in the user guide.
</Note>