{
  "authorship": "Five self-authored fictional cases, not vendor results or actual observations.",
  "cases": [
    {
      "id": 1,
      "text": " 1. A repeated refrain disappears   Fictional setup:  The approved record contains \u201cLeave a light beside the door\u201d in both the first and final refrains. An imagined exported file contains that line only once. The editor has checked the first occurrence and is about to approve the file because the words look familiar.   Review decision:  Identify occurrences by their position in the song, not by unique text. Compare the final refrain separately and mark its missing cue as unresolved. Keep both occurrences in the source record even though their words match. Counting unique lines would conceal this mistake; a cue inventory with section names makes the missing event visible.   Proposed correction and evidence:  Restore the final occurrence from the approved source, then review its own start and end against the final video. Save the revised export identifier and the inspected final-refrain cue. Do not copy the first refrain's timestamps merely because its text matches. This fictional exercise demonstrates a completeness check, not a claim that any exporter removes duplicates. "
    },
    {
      "id": 2,
      "text": " 2. A singer label becomes visible markup   Fictional setup:  Two imaginary singers, Mira and Leon, alternate lines. The approved source associates \u201cI will wait beside the gate\u201d with Mira. In an imagined destination preview, an internal label appears as raw punctuation and tag text around her name instead of the intended readable speaker identification.   Review decision:  Separate the intended information from the mechanism used to encode it. The important handoff requirement is that viewers can identify the singer when that distinction matters. A label existing somewhere in the file does not establish that the player presents it usefully. Write down the observed display before changing the source.   Proposed correction and evidence:  Use a speaker-identification approach supported by the actual delivery format and player, then inspect the same exchange again. Preserve Mira's sung words while editing the label. Mark the case pending until a destination preview is available. The scenario does not assert that a particular format or player mishandles speaker tags; it supplies a question to check. "
    },
    {
      "id": 3,
      "text": " 3. A cue boundary changes while the text stays intact   Fictional setup:  The approved cue record assigns \u201cBring the morning home\u201d to an invented interval from 12.400 to 15.200 seconds. The imagined reopened file shows 12.000 to 15.000 seconds. Every word matches, so a text-only comparison reports no difference.   Review decision:  Compare the numeric cue fields independently from the lyric text. Record both pairs of timestamps. In this fictional record, the start moved 0.400 seconds earlier and the end moved 0.200 seconds earlier. These differences follow from the authored numbers; they are not measurements of a song or estimates of a universal acceptable tolerance.   Proposed correction and evidence:  Return to the intended timing record, investigate the export settings, and audition the corrected cue against the actual final vocal when available. Do not automatically shift all later cues by the same amount: this one example does not establish a global offset. Keep the numerical mismatch and listening status as separate fields so the file check cannot be mistaken for an audio review. "
    },
    {
      "id": 4,
      "text": " 4. A name changes during text handling   Fictional setup:  An imaginary song addresses a character named \u201cZo\u00eb.\u201d The approved cue says \u201cZo\u00eb, meet me after sunrise.\u201d In an imagined working copy, the name is displayed as \u201cZo?\u201d while the remaining line is unchanged. The file opens successfully and still contains the expected number of cues.   Review decision:  Check meaningful characters, not only word counts and file readability. Compare the name directly with the approved lyric source. Record the exact affected cue and the characters displayed. Do not infer that the songwriter approved a spelling change or normalize the name just to make a comparison pass.   Proposed correction and evidence:  Inspect the text encoding and the import/export path, correct the working copy from the approved source, and reopen the new export. Then check the name in the destination player too. If the stored text is correct but the display is wrong, retain that distinction for the next investigation. This scenario does not diagnose a real encoding failure or promise that changing an encoding setting will resolve every display problem. "
    },
    {
      "id": 5,
      "text": " 5. The correct file is attached to the wrong video revision   Fictional setup:  A caption file was reviewed for \u201cHarbor revision A.\u201d A later imaginary video edit adds an opening title sequence, but the delivery folder still contains the caption file named \u201cfinal.\u201d The caption words and timestamps match their old approved record exactly.   Review decision:  Check the relationship between files before accepting either file in isolation. The old comparison can remain valid for revision A while providing no approval for revision B. Mark the new video-to-caption pairing unreviewed and identify the new opening sequence as a reason to inspect the timing again.   Proposed correction and evidence:  Pair the captions with the intended final video, replay the opening, middle, and ending, and review all timing affected by the edit. Save the video identifier with the new caption revision. Do not rename the old file and treat that as a new review. The example explains why a handoff record needs a video identifier as well as a caption filename; it does not claim that any vendor selected the wrong file. "
    }
  ]
}