| 01Brevity | A short card: the answer in one line and one button. | More room is not a reason to say more. Keep the answer short and the detail collapsible. | A few words and one tap. Anything longer goes to the phone. | One line at the edge of view, or one spoken sentence. | Readable from the sofa: one headline and two actions. | One sentence, then stop. Offer “more” instead of reading on. |
|---|
| 02Input | Voice and typing are both one tap away; the result stays visible when the keyboard opens. | A text field is always visible; voice gets a shortcut and a visible stop. | Short voice in; a haptic or a single line confirms. | Short spoken turns. Switch to the phone to type when speaking is awkward. | Push-to-talk on the remote; type on a paired phone. | Clear start and stop sounds, and a physical mute that always works. |
|---|
| 03Focus | The current task sits above the assistant input; background tasks fold into a compact activity row. | One active workspace. Other tasks live in a side activity panel, never in competing windows. | Only the current step. Background results arrive as separate notifications that can wait. | One prompt at a time; everything else queues. | One large panel with a clear focus target. Background tasks sit behind an activity entry. | One spoken thread. Unrelated updates wait for a pause. |
|---|
| 04Outcome | One recommendation with its action within thumb reach; alternatives a tap away. | Use the space for evidence on demand or a real side-by-side comparison, not a longer list. | One takeaway. Images, video and comparisons open on the phone. | Say or show the main takeaway. Visuals open on the phone. | One recommendation. Don’t autoplay generated media while someone is deciding. | Speak one recommendation and name the replies: “Book it, another place, or stop?” |
|---|
| 05Generated UI | Full-width calendars, maps and editors. Let them scroll rather than cramming one screen. | Generate richer tools, such as tables, maps and editors, inside the same assistant frame. | A compact step, such as picking a time. Never a phone-sized grid. | Small task cards only. Maps and editors continue on the phone. | Simple panels like a date picker. Dense tables and forms move to a personal device. | Turn structure into short spoken steps with repeat, back and stop. Send maps and editors to a phone. |
|---|
| 06Control | Review the exact change before approving. Dismissing a notification never counts as approval. | Show recipients and values in full before approval. Pressing Enter in a field must never approve. | Approve on the watch only when the full scope fits on the face. Send the rest to the phone. | A glance or a casual “okay” is never approval. Ask for a distinct confirmation. | It’s a shared screen: keep message text and recipients private, and approve on the phone. | Read back the action and values, then require an explicit approval phrase. Silence is not consent. |
|---|
| 07Continuity | Hand off to a laptop at the same step with the same draft; voice-started tasks arrive as editable views. | Open exactly where the phone left off, and flag any edit that is still syncing. | Show progress and the retained choice. Drafts stay on the phone. | Resume with a short cue that names the task and the retained choice. | Show a summary that’s safe to share. Private edits continue on the phone. | Recap where things stand in one sentence and offer to continue on a named device. |
|---|