---
title: Composer — turning artifacts into surfaces
---

# Composer — turning artifacts into surfaces

> _Composer is the layer that turns durable artifacts into the human-facing things product teams actually ship._

Composer exists because reasoning and presentation should not be fused into one platform abstraction. Nexus runs agents, teams, and workflows and emits artifacts. Composer turns those artifacts into a surface that a clinician, patient, API client, or frontend can consume.

## What Composer can produce

| Surface | Example |
|---|---|
| Narrative | A concise clinician summary |
| Chart | A visual trend or grouped biomarker view |
| Card | A focused product UI module |
| Report section | A printable or exportable section |
| Chat payload | An AG-UI or app-facing structured response |
| Artifact panel widget | A chart, summary, trace, or generated layout panel |
| API payload | A structured application output |
## Why Composer is separate

Composer is separate so artifacts remain the durable reasoning record and surfaces remain downstream outputs built from that record.

## What Composer should not do

- Re-run hidden clinical reasoning.
- Invent new claims not present in artifacts.
- Become the place where auth, data access, or eval policy lives.

Composer is also the right place to shape AG-UI Artifact panel payloads from artifacts so chat and non-chat surfaces can reuse the same surface layer.