# VTT Prototype: tasks

The live checklist for the VTT Prototype mock-up. Read `CLAUDE.md` first (rules), then this file, then `DECISIONS.md` (what is decided and what waits on Austin). Update both in the same change when you finish or add work.

## Next up

1. **Austin: pick a first build.** Choose a type for version 1 (T1a to T1d are fully offline) and say how many options you want from each category, for example "T1b, 2 from C1, 1 from C5, 2 from C8". The My build tab can produce that request.
2. **Austin: answer the open questions** in `DECISIONS.md`, starting with the graphics card, the language you dictate in, and whether client-confidential material may ever go to the cloud.
3. **Mock the remaining screens**: the settings window (hotkey, microphone, model, dictionary), the tray and overlay states, and the history window, so the interface can be judged before it is built.
4. **Define how Arti would be called** (upload size, auth, streaming, errors) so the cloud types T3c and T4 have a real contract to design against.
5. **Re-verify the product facts** (model names, prices, cloud services) when a build gets close; the Notes section of the Full list has the sources.

## Done

- [x] 2026-10-31: v0.1. Signal chain with lane colors for 16 types, 137 options in 14 categories, scripted demos of eight live-versus-on-stop strategies, My build with clash checks and a copyable request, Full list, `CATALOG.md`, unit tests for the data.

## Ideas, not started

- [ ] Compare two types side by side.
- [ ] A cost estimator for the cloud types (hours of dictation per month).
- [ ] Export a build as a checklist of install steps for Windows 10.
