Artifacts

Artifacts are the documents Addison produces from your data and saves inside a project: Reports, Dashboards, and Decks. They share a starting point — Addison generates one from a prompt or a playbook and saves it to a project — and each type has its own home in the app. What you can do next varies: reports and decks support verification, version history, publishing, and export, while dashboards are edited live and export at the card level. The per-type pages below say exactly what each supports. Addison also produces two second-class artifacts: file outputs rather than native Summation documents. They live in your project files and open in an in-app editor or viewer, but have no dedicated home in the left sidebar. A common flow is to promote one into a first-class artifact: ask Addison to rebuild an Excel model or an HTML report as a dashboard, deck, or report, so it gains data citations, verification, and a dedicated home in the app. Playbooks (.spb) sit alongside them. A playbook isn’t an artifact itself — it’s the reusable blueprint that produces them (first-class and second-class alike), on demand or on a schedule, so a recurring analysis comes out the same shape every time with fresh data. One playbook can produce several artifacts in a single run.

​

Creating artifacts

You can create an artifact in a few ways:

• In a chat with Addison — describe what you want and Addison generates it.
• From its dedicated page — Reports (/report), Dashboards (/dashboards), and Decks (/decks) each have a create button.
• From a project — use Create in the project’s file list (see Create artifacts from project).
• By running a playbook — each run produces that playbook’s declared outputs.