Controlled Two-Version Workflow
Use this only if you need a clearer comparison method. Keep the intended outcome fixed and judge what improved, what drifted, and whether either candidate actually serves the brief.
Review the Comparison MethodCompare AI Music Versions | Righteous Track Builder
Start where your project is now. Move forward when the required work is complete.
Righteous Track Builder · Compare
Choose the strongest version before you generate more.
This route is for creators who have two or more generated candidates built from the same song brief and need to decide which version deserves the next round of work.
Selection is not expansion. First choose the strongest core candidate. Only then decide whether to repair it, continue building it, approve it, or hold it.
Prerequisite
Bring comparable versions and the standard they were meant to meet.
- One approved song brief, Track Direction Statement, or written set of criteria
- Two to four candidates created for the same intended outcome
- Candidate names, links, or version IDs
- A willingness to reject a pleasant version that does not serve the brief
Compare With Evidence
Use only the resources that help you make the selection.
Candidate Comparison Worksheet
Compare candidates directly, record what each version does well, identify the lead candidate, and make the selection against written criteria rather than first impression.
Use the Free WorksheetAI Version Strategy Starter Kit
Use this only when a larger version set needs cleaner names, listening notes, selection records, or branch control. It is not another stage you must complete.
Open the Free Starter KitStop when the evidence is sufficient.
The Compare stage is complete when one lead candidate is selected, its protected strengths are named, its main remaining weakness is clear, and one next project action has been chosen.
Do Not Expand Yet
Alternate versions come after the core winner.
Do not branch into remixes, alternate arrangements, shortened cuts, instrumental versions, or other expansions until one core version has clearly won.
Correct order: compare → select → protect the strengths → choose one next action → expand only when a different version has a clear purpose.
Completion Evidence
Return with a decision record—not another folder of maybes.
- The brief or criteria used for the comparison
- The candidate names, links, or version IDs reviewed
- The selected lead candidate
- Why it won, tied directly to the brief
- The hook, groove, vocal, emotion, structure, or other strengths that must be protected
- The lead candidate's most important remaining weakness
- A short note explaining why each rejected candidate was not selected
- One next action: repair, continue, approve, or hold
Choose the Next Route
RepairUse Existing Song Diagnosis when one specific problem is preventing the selected version from moving forward.
ContinueReturn to Build when the selected candidate needs another controlled creative cycle.
ApproveMove to Release Readiness when the selected version no longer needs major creative changes.
HoldRecord the decision and state what evidence would justify reopening the song later.
If the comparison is complete but the next decision is still unclear, use ASK JACK from Member Home with the evidence above.
