Sanctum Canvas · Track A review lab
What do you want to look at?
This site is the review surface for the ported chat-to-screen renderer. A model writes a short program using the full OpenUI component catalog; the canvas turns it into live UI. Nothing here talks to a real model — every page runs on saved or scripted data, so what you see is the renderer, not a model’s mood.
If you only have two minutes, open the guided walkthrough.
Guided walkthrough
A scripted conversation, on rails. An ops lead asks the assistant how the restaurant did this week and the canvas fills in step by step: text, numbers, charts, a table, a form that fires a tool, follow-up questions, and a confirmation dialog.
What to expect: About 18 short steps. Press Next or let it auto-play. Every component family appears in context, and the program shown at each step is a real one the parser accepts.
What the model can draw
The full list of components the model is allowed to use — the same two catalog files the host sends it, one for dashboard replies and one for chat replies — with each component's arguments in order, what it can hold, and where to see it drawn.
What to expect: Around eighty names per catalog, grouped the way OpenUI groups them. Type in the box to narrow the list. Nothing here is a sample; it is the contract.
Stream lab
Replays saved event streams into the canvas and shows the raw events and state on the right. Also has a canned "live" prompt and the server-side tool buttons.
What to expect: Pick a saved example and press Replay. Use this to see how a model reply becomes a screen.
Text, cards, and layout
Stack, Card, headers, paragraphs, callouts, tags, metrics, lists, code, images, plus Tabs, Accordion, Section, Steps, Carousel, and an open Modal.
What to expect: One sample of each. Tabs, accordion, carousel arrows, and step titles respond. The dialog stays closed until you open it.
Forms, tables, charts, and buttons
A full form with every field type, selection controls, button variants, a sortable table, an editable table, nine chart types, card blocks, an image gallery, tool-activity rows, and the small parts a model may place on their own: markdown, metrics, tags, icons.
What to expect: Static samples you can type into and sort. Charts are SVG drawn by the runtime. Every piece here is a name in the catalog.
Stack and Card roots
Just the two root layouts a model reply lands in.
What to expect: Labels in a row, and a card whose source is a link you can open.
Carousel and Modal
The two container components with the most keyboard behaviour: scroll-snap slides and a focus-trapping dialog.
What to expect: Arrow keys move the carousel; Escape closes the dialog.
Content Security Policy smoke
Proves the page refuses inline scripts, inline styles, and unsafe URLs, and that renderer resource limits hold.
What to expect: A list of pass / fail lines. All should read pass.