Artifacts

An artifact is a result packaged as a separate object: a document, a spreadsheet, a deck, an image, a body of code. It does not dissolve into the conversation: you can open it, edit it, download it, and pass it on.

Services call them different things and build them the same way. Some answers stay as text in the window; some turn into an object you work with separately.

How an artifact differs from an answer in the window

An answer in the window is part of the conversation. It stays where it is in the thread, and the next correction arrives as a new message below it.

An artifact lives apart from the messages. Ask for one section to be fixed, and the service changes the object itself while the earlier version stays available. You do not have to assemble the result out of pieces scattered through the conversation.

What comes as a file

Not every format can be exported. Spreadsheets and documents come back as files.

Decks are harder: one service does not export .pptx directly and suggests assembling the slides in its own editor first.

Artifacts and projects

An approved result gets saved as a file and placed in the project materials, as described in the chapter "Working in a Project". Later chats see it and build on what is done.

This does not happen automatically. Moving a file from a chat into project materials is your job.

What accumulates becomes a working folder on the topic: source documents, your decisions, interim calculations. A month later you open the project and continue instead of reconstructing your reasoning from a thread.