WAV AI 中曲風混音前的歌詞草稿提示詞骨架設計

If your short-form pipeline treats “AI lyrics” and “AI remix” as interchangeable buttons, you will over-generate and under-learn from listens. A prompt spine is a typed contract for the lyric pass: it decides which variables reviewers may change later. This note frames lyric spines as an interface, then shows where a genre remix belongs—after the text graph is stable—inside WAV AI.

Background: text and audio are different review graphs

Music information work often studies lyrics and audio as related streams with their own evaluation problems. Open resources such as the DALI dataset (aligned lyrics with audio) make that separation explicit. Downstream product tools compress the loop, but your pipeline still needs typed steps: meaning first or arrangement first—not “more AI.”

Spine as an interface contract

Think of the lyric call like an endpoint:

spine = {
  promise: string,          # one-sentence chorus meaning
  must_keep: string[],      # title line / hook fragments
  sections: ["verse","pre","chorus",...],
  constraints: string[]     # syllable budget, banned clichés, VO overlap rules
}
→ lyric_draft
→ rewrite(single_named_flaw)
→ freeze_keepers
→ (optional) remix_bed

Field	Why it exists	Failure if omitted
promise	Gives reviewers a pass/fail besides “feels cool”	Endless vibe arguments
must_keep	Protects identity across rewrites	Chorus mutates every pass
sections	Forces structure over sticky one-liners	Orphan hooks with no verse job
constraints	Encodes picture/VO reality	Beautiful lines that do not fit the cut

A minimal pipeline sketch

brief → build_spine → lyrics_generate → rewrite_once
      → freeze_keepers
      → remix_if_bed_gap
      → ship_max_2_candidates

build_spine / lyrics_generate

Use the AI Lyrics Generator only after spine is filled. Cap rewrite to one named flaw (rhyme collision, syllable overrun, unclear promise). Multi-knob rewrites destroy causal learning.

remix_if_bed_gap

Call the AI Music Remixer only when keepers are frozen and the remaining bug is energy, genre, or instrumental density. Preview under VO. Reject remixes that force lyric rewrites—that is a signal you unfroze the wrong layer.

Rights as a pipeline gate

Adaptation permissions are not a model parameter. Creative Commons’ CC license overview is a practical reference when the source work actually carries a CC grant; commercial releases without that grant still need clearance. Put the rights check before public export, same as any other ship gate.

Practical defaults for small teams

Default: lyrics spine → one rewrite → freeze → remix only if bed fails.
Escalate remix early: only when the brief names “wrong genre/energy” and the lyric promise already ships.
Candidate cap: two beds per frozen lyric; log one-line failure reasons.
No invented KPIs: your picture length and phone-speaker listen are ground truth.

What this note is not

It is not a bake-off of generative architectures, and it does not cite product marketing percentages. Treat lyric and remix as typed stages with explicit freeze points—then your failure logs start teaching something useful.