phoneticizelisted

# Phoneticize — TTS pronunciation prep A workflow for identifying pronunciation hazards in a TTS script, agreeing phonetic renderings with the user via audio previews, and emitting a phoneticized script ready for narration. ## Read first | Reference | When to read | Path | |---|---|---| | Detection heuristics | Before Phase 1 — patterns that find candidates and how to combine them | `references/detection-heuristics.md` | | Respelling conventions | Before Phase 2 — how to write phonetic respellings that Eleven v3 actually obeys | `references/respelling-conventions.md` | | Eleven v3 format notes | Before Phase 3 and Phase 5 — what the engine accepts and silently ignores | `references/eleven-v3-notes.md` | ## Governing principles 1. **Preview the fragment, not the word.** TTS prosody depends on surrounding context. A respelling that sounds right in isolation collapses inside a sentence. Render fragments throughout. 2. **Respelling is the primary output, not SSML.** Eleven v3 silently drops `<phoneme>` tags (see `references/eleven-v3-notes.md`). Inline respelling — `Siobhán` → `shi-VAWN` directly in the prose — is what actually changes the model's output. IPA goes in the table for archival precision; respelling goes in the script. 3. **Mark uncertainty, never guess.** A wrong respelling shipped with confidence is worse than an explicit `?` the user resolves. When the pronunciation isn't obvious, ask. 4. **Stable IDs across iterations.** Each candid