CRT HUD Specs
Bench-first voice UI for live repair sessions. Max display: 1024 × 768. The screen should read like a diagnostic instrument, not a toy.
Spec
What this screen must do
- Show a clear system state at a glance.
- Carry live captions without cluttering the repair view.
- Render a real oscilloscope-style waveform tied to actual audio.
- Look good on camera and survive YouTube compression.
- Stay usable at 1024 × 768 with chunky text and simple geometry.
Dexter notes
What I care about
The CRT should feel like one more tool on the bench. If the operator has to decipher the screen, we already lost. I want three things: a hard state, readable captions, and a waveform that tells the truth.
The first version should be boringly reliable. If we need a trick, use it for latency masking, not for spectacle.
— Dexter
Layout
1024 × 768 composition
Top strip system name + state + clock + telemetry slot
Scope core largest region; main waveform + sweep logic
Caption band 2 lines preferred, 3 max, high contrast
Bottom rail pedal state, latency, mic/talk indicators
Future lane live car data overlay: RPM, voltage, CAN activity
Prototype
CRT frame mockup
AI MECHANIC / DEX
voice repair HUD · 1024×768 target
LISTENING
Clock 09:41:00
Latency ~0.84s
Telemetry lane reserved for RPM / battery / CAN later
Live captions
Talk while you work. The bench stays the priority.
Push to talk. The bench stays the priority.
Pedal: armed
Mic: close-talk
Voice: local
Mode: listening
Color / state rules
Keep it legible
- Green = normal and active.
- Amber = thinking / retrieval / pause.
- Red = fault / offline / blocked.
- Never rely on color alone. Add motion and labels.
- No tiny text. No fast flashing. No fake complexity.
Latency budget
Fast enough to feel human
| Stage | Target |
|---|---|
| VAD / endpoint | 100–250 ms |
| STT | 100–200 ms |
| Brain first token | 300–500 ms |
| TTS start | 100–200 ms |
| Total perceived | ~700–900 ms |