Shared and live pages

A board, a survey, a quiz or a plan: pick the shape, then copy its prompt.

guide~3 minVerified v0.127.10

A page that several people use at once is one of four shapes. The shape decides who owns a row, who may change it and what everyone else sees, so pick it before your agent writes anything.

You want	Shape	A row is	Who changes a row	Others see
A board people add notes to and rearrange	shared document, keyed by note	one note	anyone in the room; the newest edit wins	every note, live
A survey people come back to	answer sheet	one person's answers	that person	nothing; only you read them
A quiz with a score	event log, one answer per question	one answer	nobody; it is final	a live tally, then answers at the reveal
A plan or roster everyone edits	shared document, keyed by item	one item	anyone in the room; the newest edit wins	every item, live

A board

Build a shared board

Your agent builds a board where anyone you invite adds and moves notes.

Build a shared board in Super Artifacts where the people I invite add notes and move anyone’s note, and every open screen updates without a reload. Ask who it is for and what a note holds. Declare perUser shared with key note_id (a required text, max 120, the page makes for each new note), writes upsert, read public (on a private artifact that is only the people who can open it), fields for the text (max 280), x, y and colour, and no personal data. Show who wrote each note from the row’s author label, not from a name field the page fills in. Subscribe to the live room for new, moved and deleted notes and ping every 30 seconds; read super_help live first. Publish with super_publish, keep it private, invite the people I name with super_share and return the link. Test with two browsers before you hand it over.

A survey

Build a survey people can come back to

Your agent builds a form that remembers each person's answers.

Build a survey in Super Artifacts whose answers people can come back and change. Ask for the questions and who answers. Declare an answer sheet: perUser single, writes upsert, read own, recordCap perVisitor 1, one optional field per question. Long answers are text with max 2000, a rating is an integer from 1 to 5, and a pick-all-that-apply question is one boolean field per option. On load, read this visitor’s row with scope own and fill the form; save each answer as it changes, and send null to clear one. Publish with super_publish, keep it private with super_artifact_set, arrange only the audience I choose and return the link. After I answer twice, read it back with super_data and show me one row with my latest answers.

A pick-all-that-apply question is one yes-or-no field per option, so each option is counted on its own. Clearing an answer and saving removes it.

A quiz

Build a scored live quiz

Your agent builds a quiz whose answer key stays off the players' phones.

Build a scored live quiz in Super Artifacts by hand, not from a template, so the answer key never reaches a player’s phone. Ask for the questions, the answers and who plays. Keep the key in a stream only the owner reads and writes; put each question on a stream the owner writes and everyone reads; take answers on a stream players read as their own, with uniqueBy question_no so each player answers each question once, writeAt question so answers land only while a question is open, and revealAt results. Add a public tally. The host screen is my own signed-in page or a named Editor’s; move the phase from it or with super_artifact_set. Score from the server’s at times, never the phone’s clock. Read super_help live first, ping every 30 seconds, publish privately and test with two phones.

The live quiz recipe uses a ready-made template, and that template's answer key travels inside the page. Use it for fun and practice. For a score that counts, use this prompt.

A plan

Build a shared plan

Your agent builds a plan anyone you share it with can edit.

Build a shared plan in Super Artifacts that anyone I share it with can edit, one row per item, with the newest edit winning. Ask for the items and the columns. Declare perUser shared with key set to the item field (a choice or a short text), writes upsert, read public (on a private artifact that is only the people who can open it), and recordCap perArtifact as the number of items. Every save carries the item’s key and only the fields it changed; an empty field sent as null is cleared. Show updatedAt as the last edit, and subscribe to the live room so other people’s edits appear without a reload. Public text fields stay at 280 characters or less. Publish privately with super_publish, arrange the audience I choose and return the link.

Two people saving the same item a moment apart: the later save wins, and nobody is told. Each item records when it was last edited.

What other people see

On a public or workspace-wide page, other visitors see the same alias for each writer, not their name; only you see who wrote what. On a Restricted page, the people you named who have signed in see each other's display name as the author, and nothing else about them.

The page itself can read more than it is meant to: the token it uses to save carries a signed-in visitor's display name and account id. That is not a supported way to learn who is visiting and may change, so do not build on it.

Live updates

Every shape can update open screens without a reload through the artifact's live room. Your workspace runs a limited number of rooms at once.

Which artifacts hold a live room

Your agent lists your live rooms and what holds them.

Which of my Super Artifacts are holding a live room right now? Call super_whoami and read liveRooms: tell me how many rooms my workspace may hold at once and, for each one held, the artifact and since when. If I want another artifact live and every room is taken, suggest which to turn off with super_artifact_set live false, and change nothing until I say which; afterwards tell me how many open pages it disconnected.

Next: Live rooms