What an artifact is
A published bundle at a stable address, isolated from platform sign-in.
concept~2 minVerified v0.237.0
An artifact is a published bundle of files at a stable address, superart.page/{id}. Its id is assigned on creation. Its slug resolves within a workspace, so reusing it there publishes another version rather than another page.
Seven kinds
| Kind | What a visitor does |
|---|---|
| page | Read |
| slideshow | Advance through |
| survey | Answer |
| tracker | Add entries to |
| video | Watch |
| tool | Operate |
| dashboard | Watch numbers move |
Kind describes what people do with it, not a separate hosting system. page is the default; a single HTML file is enough.
The wrapper and the frame
The platform dashboard does not execute your artifact code. The artifact's wrapper holds it in a sandboxed frame with an isolated origin. Scripts and forms work there; they cannot reach the platform's sign-in cookies.
The served header belongs to the platform. It differs from the dashboard header. Eligible paid artifacts can hide it through the platform setting; artifact code cannot rewrite it.
| Inside the frame | Behavior |
|---|---|
| Scripts, forms, downloads, fullscreen | Supported within the sandbox |
localStorage, sessionStorage | Per-browser storage, up to 1 MiB each; session storage is per tab |
| Cookies, IndexedDB, service workers | Unavailable |
| Visitor identity | No supported general identity interface; do not depend on readable data-token claims |
| Third-party iframes | Blocked; supported YouTube and Vimeo players are drawn outside the sandbox |
Browser storage does not follow someone to another device. Shared or durable answers need a declared data policy.
Audience and versions
New artifacts use the workspace default unless you specify visibility. Updates keep their audience unless changed. Ask for private explicitly; sharing controls who can open or comment.
Every publication saves a version. Official document templates can also retain declared source for editing and exports; markdown source co-editing is separate from visitor response collection.
Next
Versions are a pointer, create artifacts or collect responses.