Three shapes of data
Responses an artifact collects, collections you edit, and datasets that join them across artifacts.
concept~2 minVerified v0.237.0
Super Artifacts separates visitor responses, editable workspace collections and the datasets used to query responses across artifacts. Choose the store before building the page.
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.
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.