{
  "authorship": "Original fictional writing briefs and sample directions; not vendor outputs",
  "cases": [
    "1. A suggested adjective is mistaken for an approved change\n\n**Fictional brief.** Mara writes a short song for an imaginary pottery studio. Revision R03 contains two authored lines: \u201cWe leave the blue cups by the door / And turn the sign to open once more.\u201d Her collaborator suggests replacing \u201cblue\u201d with \u201cbright,\u201d but Mara has not accepted that suggestion. The two copies now differ by one word, and both filenames contain \u201cfinal.\u201d\n\n**Authored decision.** Keep R03 as the approved text and record the adjective proposal separately. The handoff card reads: \u201cLyric R03 approved by Mara for the next demo; R04 proposal pending; use blue cups.\u201d The approved file contains only the two accepted lines, with no alternative in parentheses. No real approval or real collaborator is implied by this exercise.\n\n**Check and stop rule.** Read the actual attachment and compare its first line with R03. Do not rely on the message saying \u201cattached the final one.\u201d If the collaborator wants the proposed word, obtain a new decision and assign a new revision. The change note can remain one sentence: \u201cR04 replaces blue with bright; not yet accepted.\u201d The purpose is to make the decision visible, not to create paperwork for every keystroke.\n",
    "2. A clean text draft is paired with the wrong demo\n\n**Fictional brief.** Leon's imaginary train-station song changes from \u201cI missed the last train home\u201d in R06 to \u201cI let the last train go\u201d in R07. His folder includes a demo called station-A. In this constructed scenario, its preparation note identifies R06 as the input. The newer line changes the narrator's agency; a polished audio file would not settle which meaning Leon intended.\n\n**Authored decision.** Deliver R07 as the approved lyric text and label station-A \u201colder lyric input R06; reference arrangement only.\u201d Do not rename the demo R07 simply because it sits next to the newer text. A separate audio-to-lyric field says \u201cR07 performance not checked.\u201d These are invented project records, not observations from an actual generated song.\n\n**Check and stop rule.** Before approving an audio take, listen to the changed passage and record what is actually sung. Until that happens, distinguish a recorded input label from an observed vocal result. If the old take remains useful for rhythm, keep it as a reference with the mismatch visible. Do not erase the old file to make the folder look consistent. The handoff has two honest states: accepted text and unresolved audio alignment.\n",
    "3. A chorus replacement leaves one old repeat behind\n\n**Fictional brief.** Inez's invented garden song repeats a two-line chorus twice. R02 uses \u201cLeave a little room for rain / Let the roots begin again.\u201d The proposed R03 replaces its second line with \u201cLet the dry ground breathe again.\u201d Her working document updates the first chorus but leaves the last chorus unchanged. This is a constructed text inconsistency, not a failure attributed to a lyrics service.\n\n**Authored decision.** First decide whether both appearances should change. In this exercise Inez chooses identical choruses, so the clean R03 contains the revised pair in both locations. The change note says \u201cChorus line two replaced in both occurrences; verse unchanged.\u201d If a different final chorus were intentional, the note would identify that exception instead of forcing uniformity.\n\n**Check and stop rule.** Expand every repeated section in the handoff copy and read its actual words. A shorthand instruction such as \u201crepeat chorus\u201d can be useful for writing, but it leaves the recipient dependent on the right reference. Stop when each intended occurrence matches the accepted decision. This checks the text handoff only. A later music generation could still omit, repeat, or change a line and needs a separate listening check.\n",
    "4. A performance note accidentally becomes lyric text\n\n**Fictional brief.** Theo's imaginary lighthouse song has these authored words: \u201cKeep one window facing east / I will watch until you sleep.\u201d A collaborator writes \u201csofter here, leave space after east\u201d directly below the first line. Theo wants the words unchanged, with that instruction treated as a performance suggestion. A pasted block now mixes words and direction without labeling either.\n\n**Authored decision.** The clean lyric file contains only the two lines. A separate brief says \u201cPerformance suggestion: soften the first line and leave a pause after east.\u201d The handoff identifies the lyric as approved and the performance suggestion as optional. This does not assume any generator understands a particular bracket or tag. Check the receiving tool's available fields before placing instructions there.\n\n**Check and stop rule.** Read the lyric-only file as if every visible word might be sung. Then read the brief independently and confirm that it never silently replaces a lyric. If the interface offers only one field, preserve the two-part source locally and document exactly what you pasted. Do not claim the direction was followed until you hear the output. Separating intention from words makes an accidental spoken instruction easier to diagnose later.\n",
    "5. An approval covers a verse but is used for the whole song\n\n**Fictional brief.** Noor drafts a fictional reunion song. The accepted verse ends \u201cYour coat still hangs beside the stair.\u201d A proposed bridge says \u201cI sold the house and left it there.\u201d Her imaginary collaborator approves the verse only; the bridge adds a major event that has not been agreed. A broad \u201capproved\u201d label would conceal both the scope limit and the unresolved story decision.\n\n**Authored decision.** Record \u201cR08 verse approved; bridge pending; not ready for a whole-song handoff.\u201d Keep the proposed bridge in the working draft, not in the approved excerpt. The next question is specific: should the narrator have sold the house? In this exercise no answer is invented. A pending state is the useful result because it prevents an unapproved event from becoming the apparent final story.\n\n**Check and stop rule.** Compare the approval scope with the material being handed over. If a full song is required, resolve the bridge before advancing that full-song state. If the recipient only needs the verse, send the approved excerpt and label its limits. Do not infer approval from silence, a downloaded file, or a positive comment about the melody. This is an editorial workflow example, not a legal interpretation of consent or ownership.\n"
  ]
}