Controlled Two-Version Workflow
Learn how to compare two generations without changing several variables at once. Use the brief to decide what improved, what drifted, and whether another generation is justified.
Open the Learn ArticleVersion Selection Route | Righteous Track Builder
Start where your project is now. Move forward when the required work is complete.
Righteous Track Builder · Generated Candidates
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 create useful alternate versions.
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
Learn → Apply → Build
Use the existing resources in this order.
Candidate Comparison Worksheet
Compare the candidates directly, record what each version does well, identify the lead candidate, and choose the next action without relying only on first impression.
Use the Free WorksheetAI Version Strategy Starter Kit
Use this when you have more than two versions or need cleaner version names, listening notes, selection records, and a controlled branch decision.
Get the Free Starter KitTP2 Chapter 7, then Chapter 8
Use Chapter 7 to run a repeatable builder loop. Move to Chapter 8 only after a winner has been chosen, so versioning and output discipline support the selected song instead of creating more indecision.
Open TP2 Chapter 7Then Open TP2 Chapter 8Do Not Expand Yet
Alternate versions come after the core winner.
The VIP AI Song Version Expansion System is designed to create useful alternate versions from a selected core song. It should not be used to avoid choosing the first winner.
Correct order: compare → select → protect the strengths → decide the next action → expand only when a different version has a clear purpose.
Later: Review the VIP Expansion SystemCompletion 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.
ContinueUse TP2 Chapters 7 and 8 to run the next controlled build cycle and maintain version discipline.
ApproveReturn to the Track Builder and choose Release Readiness when the selected version no longer needs major creative changes.
HoldArchive the decision record and state what evidence would justify reopening the song later.
ASK JACK is most useful after the comparison record is complete and the unresolved decision can be stated clearly.
