Realtime Writing and Translation Accuracy
What this domain measures
Accuracy here means the text your software produces live, stroke by stroke, not the polished transcript you deliver later. A reporter who writes clean final copy but generates untranslates and homonym errors on the feed fails the realtime standard. Questions test whether you understand where the software gets its answers and how to control it.
Dictionary layers
Know the hierarchy: the software's built-in dictionary, your personal main dictionary, and the job (case) dictionary. The job dictionary overrides the main dictionary for that file only. A common trap: assuming a fix made during a job permanently teaches the system. If you want the entry for every future job, it must go into the main dictionary; if it belongs to one case, keep it in the job dictionary so you do not pollute your general vocabulary with a party's surname.
Untranslates versus mistranslates
An untranslate at least announces itself. A mistranslate - a homonym, a wrong brief, a proper noun that resolves to a common word - reads as clean copy and is far more dangerous. Fix untranslates three ways: define the outline, reassign it to a brief you can actually stroke, or spell it out. Then verify by writing the word again.
Conflicts and consistency
Each word should have one outline you write reflexively, and each outline should mean one thing. When a conflict appears, pick the outline you genuinely write under pressure and archive the alternative. Phrase briefs and punctuation strokes must be written identically every time or the software cannot predict them.
Rule of thumb: if you cannot write a brief three times in a row without thinking about it, it is not a brief - it is a future untranslate.