Artifacts

View as Markdown

Artifacts

Artifacts are work products generated during conversations: technical designs, blog posts, strategies, code, analysis documents. Unlike beliefs (which are atomic), artifacts are rich, multi-paragraph content with version history.

Version chain

Every artifact revision links to the previous version, forming a chain like git commits:

API Design Doc v1 → v2 (added auth section) → v3 (revised based on team feedback)

Each version records what changed and which beliefs or decisions drove the change.

Linked beliefs

Artifacts connect to the beliefs that shaped them. When you write a blog post with “concise intros” as a preference, that belief is linked to the artifact. If the belief changes, the system can flag which artifacts were built on it.

Cross-session identity

An artifact persists across sessions and tools. Start a technical design in Claude, refine it in ChatGPT — the artifact keeps its identity and accumulates the full history.

Descriptor propagation

When an artifact is updated, XTrace propagates key descriptors (title, type, summary) to keep search and retrieval accurate without re-indexing the full content each time.

API

OperationEndpoint
ListGET /v1/artifacts
SearchGET /v1/artifacts/search
GetGET /v1/artifacts/{id}
UpdatePUT /v1/artifacts/{id}
DeleteDELETE /v1/artifacts/{id}