SYNTHETIC TECHNICAL DUBBING REFERENCE — not a recording or product-test result
Purpose: create a permitted, harmless training-kit video for a shared-clip evaluation.
Revision: example C. Replace details only before freezing your evaluation reference.
Arrange permission for any recording and speakers. Have a qualified target-language reviewer approve the reference meaning.

Segment 1 — Presenter:
"This training kit contains part BX-17, revision C. Please use the printed reference card to confirm the identifier."

Segment 2 — Presenter:
"The tray contains twelve sample pieces, not twenty. We are discussing the training kit; this video does not describe equipment operation."

Segment 3 — Reviewer:
"Is the review scheduled for September 18?"

Segment 4 — Presenter:
"Correction: September 19 at 15:00 Japan time. We have not assigned an owner yet."
[Pause; show a blank owner field on a harmless training card.]

Reference meaning:
- Identifier exactly BX-17; revision C.
- Quantity twelve; twenty is explicitly rejected.
- Final review Sep 19 at 15:00 JST; Sep 18 superseded; year unspecified.
- Owner unassigned; do not invent a person.
- The material concerns a training kit, not operational instructions.

Before use:
Record source-file version, target language, permission basis and reviewer.
Create a reviewed target-language reference without relying on the evaluated output itself.
Keep the same clip and reference across products; label any changed-source round separately.

Fictional correction-cost example used in the article and CSV:
After an initial target-language output, segment 2 audio and SRT say twenty.
The approved source and visible label still say twelve. A generic editable workflow
repairs target text, produces replacement audio, corrects the SRT and reassembles media.
Assumed active minutes: edit 2; SRT 1; assembly 2; review 2; revision record 1 = 8.
Assumed service wait: 3 minutes. At USD 60/hour plus an assumed USD 2 generation
charge, the incremental correction is USD 10. Subscription and first production excluded.
R2 approved and R1 superseded are fictional example states, not actual file artifacts.
No named vendor is assigned these times, costs or outcomes.