Skip to main content
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

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:
Example data. source tells you what made it, and activity_id links it back to the capture it came from.

Create

--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

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

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

Sharing one

An artifact stays in your Home until you attach it to a post:
There is no space-scoped artifact. Attaching to a post is how one reaches a team.
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 in the user guide.