Threads vs Artifacts
A thread is a processing container.
An artifact is a durable object.
Use this page to answer one question:
What belongs in a thread, and what should become an artifact?
Comparison
| Aspect | Thread | Artifact |
|---|---|---|
| Role | Living processing space | Durable output |
| Purpose | Think, classify, transform, refine | Preserve, reuse, reference |
| Best for | Active work, ambiguity, back-and-forth, local context | Stable procedures, decisions, summaries, support objects |
| Shape | Evolving and conversational | Bounded and named |
| Value | Helps processing happen | Keeps useful residue from being lost |
| Risk if overused | Chat sediment | Premature formalization |
Why the distinction matters
This framework depends on one structural rule:
Threads process. Artifacts persist.
Without that distinction:
- useful work stays buried in chat
- storage becomes vague
- assistants drift across mixed material
- the same thinking has to be repeated
- captures accumulate without becoming reusable objects
A thread is where a capture gets worked on.
An artifact is what survives if that work is worth keeping.
Thread-only material
Keep material in a thread when it is mainly:
- exploratory back-and-forth
- rough clarification
- temporary ambiguity
- local revision
- partial thinking not yet worth preserving
- context that is useful only while the work is active
Artifact-worthy material
Promote material into an artifact when it becomes:
- reusable
- referenceable
- costly to recreate
- needed by future-you or another operator
- useful outside the original thread
Promotion rule
Promote out of a thread when all three are true:
- the output has a clear artifact type
- it is useful beyond the current conversation
- recreating it later would cost more than preserving it now
If those conditions are not met, keep it in the thread or leave it ephemeral.
Practical rule
Use a thread for active processing.
Create an artifact when the result is stable enough to reuse.