Building block
Artifacts
Version every output your software produces, with a durable, immutable revision history.
What it is
Artifacts are the outputs your systems produce: documents, briefs, records, decisions rendered as content. Every artifact is typed and versioned, and every revision retains the inputs, sources, and claims that shaped it.
How it works
How artifacts works
- 1
Produce a revision
Work produces a new typed revision rather than overwriting state in place.
- 2
Retain lineage
Each revision records its inputs, the sources used, and the claims added, changed, or removed.
- 3
Move the pointer
The artifact's current revision advances only through the workflow that governs it.
Key capabilities
What you get
- Typed outputs with a stable schema
- Durable, immutable revision history
- Per-revision inputs, sources, and claim deltas
- Structured revision comparison
Use it with
Composes with
FAQ
Artifacts questions
Are old revisions ever discarded?
No. Revision history is durable; a new revision is appended and the head pointer moves.
Can I compare two revisions?
Yes. Revisions support structured diff, including claim and evidence-coverage changes.