The work has produced something that now matters more than the transaction that produced it — a document, a decision, a piece of code — and that transaction is the only place it exists. It has no name of its own, no address to link to, and nothing to reopen; finding it again means finding the exchange it happened in and scrolling.
Extraction gives it an identity. The thing is lifted out of its host and put somewhere it can be named, linked, versioned, and returned to. What changes is not where it sits on the screen but that it now exists independently of whatever made it.
Where the move arises
Only where the host is possessive — where what it produced has no identity apart from it. Most output is born addressed: a document made in a documents application already has a name, a place in a list, and a URL, and there is nothing to extract. Conversations, comment threads, search sessions, and message streams are possessive in this way. They hold what happens inside them as content rather than as things.
The condition is worth stating because it bounds the pattern. A design that keeps reaching for this move where the output is already addressed has misread what its host does.
Instances
- a comment turned into an issue
- a message turned into a task
- a hand-refined search turned into a saved view
- an attachment turned into a file in the shared drive
- generated output turned into its own document — the vivid instance, and the one the move was first noticed in, but not the definition
Consequences
- the extracted thing has an identity of its own — nameable, linkable, reopenable — which is what a ladder of representations needs before it can render one thing at several depths
- what the host keeps at the point of extraction — the whole thing, a pointer, or nothing — decides whether the exchange still reads afterwards as a record of what happened
- the exchange becomes disposable and the thing does not: value moves out of the transcript, and whatever was never extracted is what gets lost when the exchange is closed
- the offer has to arrive when the thing turns out to matter, which is usually after it was made and rarely when the actor is thinking about where to file it
Resources & references
- AI UX Playground — Chat Artifacts
- AI Interface Layout Library — Prompt + Canvas, AI Workspace
- aiuxpatterns.com — Result Rendered Preview
Appears in
Delegating work
- Receiving the result, step 2 — Move the result out of the conversation
Related patterns
Precedes
- Item view — the extracted thing has an identity of its own — nameable, linkable, reopenable — which is what a ladder of representations needs before it can render one thing at several depths
Enacts
- Malleability — gives the output a surface where direct manipulation applies at all
Complements
- Editing in place — once extracted, the thing is edited directly rather than asked for again
- Draft and publish — the extracted thing is the surface that draft and published states attach to
- Steering surface — extraction gives the extracted thing a surface of its own, which is what a separate instruction surface can then act on
Related to
- Workspace — a minimal workspace grown out of an exchange — one context, two surfaces
Preceded by
- Generated content — generated output in a reply stream is the AI route into this move
Hosted by
- Conversation — the chat is one possessive host among several, and the one where the move is most visible; the conversation remains the extracted thing's control surface afterwards