Interfaces that show up when you need them.
Polyxd turns a request into a real, accessible interface, built from your design system, usable by people and agents, and gone when the task is done.
One UI document, three design systems. The model chose the meaning; the design system chose the look. See it live.
- semantic components, one vocabulary
- 24
- verified renders, zero accessibility violations
- 240
- agent tasks completed by name alone
- 216/216
- injected defects caught by the verifier
- 20/20
The model picks meaning. Everything else is yours.
No pixels, no colours, no code. A small model chooses semantic components, and every surface is checked before anyone sees it.
- 01
Ask
A person or an agent says what they need, in their own words.
"send alex the rent" - 02
Mean
A small on-device model picks components and a pattern, and binds your data. It never invents a balance.
Choice recipient TextInput amount Confirm transfer.confirm - 03
Render
Your design system decides the look, natively: Material 3, Carbon, Ant Design, or your own tokens.
- 04
Verify
Every surface is checked before it ships: accessibility, layout, safety, and whether an agent can finish the task.
WCAG 2.2 AAagent ✓score 100
One interface. Every kind of user.
Screen readers read the same tree that agents operate. If an agent can't finish the task using names alone, the surface fails verification, so what works for one works for all.
accessibility tree alertdialog "Send £250.00 to Alex Kim?" term "Amount" definition "£250.00" button "Send £250.00" button "Cancel" agent press "Send £250.00" → transfer.confirm { quoteId: "q_91" } ✓
Here for a moment. Familiar every time.
Interfaces made on demand still need to feel known. Polyxd remembers where each thing sat, what it was called and which control it used, and keeps it that way the next time you ask.
- same pattern ✓
- same order ✓
- same labels ✓
- same controls ✓
- Voice
- Plain, calm, specific. No exclamation marks.
- Glossary
- Say "payment", not "transaction"
- Freedom
- Strict: approved patterns only
- Rule
- Money only moves from a confirmation
Flagged: "Recent transactions" breaks the glossary. Say "payments".
Your taste, enforced.
Designers set the direction: density, voice, patterns and rules. PMs define what the product can do and what done looks like. Every generated surface is held to both, and you can see exactly why it came out the way it did.
Open spec. Any model. Your design system.
The spec, renderer, design-system packs and verifier are Apache-2.0. They work with any model that can write JSON, and with ours when it ships.