# Three shapes of data

> Responses an artifact collects, collections you edit, and datasets that join them across artifacts.

Kind: concept · ~2 min · Verified v0.237.0 · Next: [Live rooms](https://pr-2197-stg.superartifacts.app/docs/concepts/live-rooms.md)

Super Artifacts separates visitor responses, editable workspace collections and the datasets used to query responses across artifacts. Choose the store before building the page.

```mermaid
flowchart LR
  A("Artifact responses<br/>declared by the agent's policy") --> D("Data page")
  C("Collections<br/>fields you edit in the app") --> D
  S("Datasets<br/>one series across artifacts") --> D
  D --> M1("super_data<br/>super_data_query")
  D --> M2("super_entries")
```

## Responses an artifact collects

The agent declares a **policy** when publishing: fields, write shape, read audience, retention and caps. The data API validates writes; the page cannot grant itself permission by changing its interface. An artifact with no policy collects no visitor responses.

A later version can add fields, but an existing field name keeps its first type. Add a new field to represent a different type. Removing a version does not free its field names.

Rows can be a visitor's answers, an append-only event, or a keyed shared item. Shared upserts merge supplied fields, with the last write to a field winning. An anonymous “visitor” is a browser profile, not a verified human.

Declared image, video and file fields hold references to uploaded bytes. They are at least contact data; they are not public text fields with a file URL pasted into them.

## Collections you edit

A **collection** describes records you maintain: clients, inventory or a reading list. Its entries can be draft or published. Collections support typed fields, links to other collections, and personal-data classifications.

A saved field's type stays fixed. A later collection definition replaces the whole model, so fields omitted from it are removed. This differs from an artifact policy's lifetime field-type history. A `secret` text field is write-only to the agent and usable only through an approved [secret-use grant](https://pr-2197-stg.superartifacts.app/docs/concepts/secrets.md).

## Datasets across artifacts

A **dataset** files an artifact's responses under a key. A **series** lets compatible datasets be queried together. It grants no extra access and belongs to one workspace.

After responses exist, a redeploy cannot change the dataset key or move out of an existing series. An artifact without a series can join one later. Shared fields must agree on type, measurement dimension and measure; compatible units can differ.

## Where each reads back

Use **Data** to inspect sources. Agents use `super_data` for response rows, `super_data_query` for aggregates and `super_entries` for collection entries. Queries enforce access and a privacy floor for non-owners. Dashboard tiles run with each viewer's access; sharing a layout shares no source data.

## Next

[Collect responses](https://pr-2197-stg.superartifacts.app/docs/collect-data.md), [collections and dashboards](https://pr-2197-stg.superartifacts.app/docs/workspace-data.md) or [limits](https://pr-2197-stg.superartifacts.app/docs/reference/limits.md).
