Lyria music prompt rejected by policy: what to change, what to keep

When a Sume music job is rejected by policy, change the content that was flagged and keep the rest of the musical brief. The Music 1.0 page says it in one rule: after a policy rejection, change the flagged content, keep the brief, retry only inside the budget you were authorized to spend, and do not reduce the request to a generic bed. A stripped-down prompt gets you a track, but it is not the track you were briefing.

What counts as the brief

The brief is the seven axes in the prompt: emotion, genre, tempo as a number, key and mode, instruments with texture, an arc with one named moment, and era or production. Most flagged prompts fail on one phrase, often a named artist or a request for a recognizable voice. The other six axes are not the problem, so leave them alone.

A before and after

Say the first prompt asked for a track that sounds like a named singer. Keep everything else and describe the sound: a hushed vocal-free line, the same 72 BPM, the same D minor, the same Rhodes and muted trumpet. The edit touches one clause. The second request is still recognizably the first one.

Before: Hushed neo-soul nocturne in the style of a named singer, 72 BPM, D minor. Rhodes through tape wow, muted trumpet. Instrumental, no vocals.

After:  Hushed and slightly melancholic neo-soul nocturne, 72 BPM, D minor. Rhodes through tape wow, soft sub bass, one muted trumpet line answering at 0:12. Late-night, dry and close, 1998 production. Instrumental, no vocals.

Retry rules

If the second attempt is rejected too, change the next most likely part of the prompt, not everything at once. One edit per attempt tells you what the check objected to.

• Retry only inside the budget you were authorized to spend. Each accepted generation costs the fixed Music price, $0.125 per the Music 1.0 page.
• Use a fresh Idempotency-Key for the edited prompt, so it is a new request and not a replay of the rejected one.
• Keep metadata on the job for your own record of which prompt version this was. Sume stores it and does not send it to the provider.
• Check job.request.routed_model after a pass, so you know which engine ran the new prompt.