Start a new project
Complete the intake summary below before choosing a route. Use exact filenames, links or version identifiers wherever possible.
Righteous Track Builder Guided Workflow | Complete Access
Complete Access · Member Workspace
Make one clear project decision, complete the right work, and return with evidence.
This workspace connects intake, diagnosis, route selection, completion evidence, review and the next decision. Use it for one active song project at a time.
Working rule: do not open several routes at once. Protect what already works, name one primary blocker, approve one route and complete its required output before changing direction.
Step 1 · Start or Resume
Resume an active project
Open your Creator Project Record. Bring back the current status, approved route, latest evidence and one next decision. Do not restart the intake unless the project goal or source material changed.
Step 2 · Member Intake Summary
Record the project as it exists now.
PROJECT NAME:
PROJECT GOAL:
INTENDED LISTENER:
INTENDED USE:
WHAT EXISTS NOW: idea / lyrics / reference / one generation / several versions / near-final track
EXACT CURRENT VERSION: filename, link or ID
PLATFORM, MODEL AND PLAN:
DEADLINE OR TARGET DATE:
STRONGEST ELEMENT TO PROTECT:
CURRENT CONCERN:
REFERENCE SOURCES:
KNOWN RIGHTS, PERMISSION OR DISCLOSURE GAPS:
Intake completion: another person must be able to identify the exact project, current asset, intended result and protected element without asking what you meant.
Step 3 · Primary Blocker
Choose the earliest unresolved decision—not every weakness you can hear.
Creative direction
Direction, lyrics, sound identity, reference translation, vocal concept or audience fit.
Execution
Performance, structure, arrangement, dynamics, generation control or production decisions.
Evaluation
Version selection, comparison, diagnosis, repair priority or quality control.
Completion
Documentation, rights, packaging, release readiness, delivery or next-use decision.
PRIMARY BLOCKER:
WHY THIS BLOCKER COMES FIRST:
WHAT MUST NOT CHANGE WHILE FIXING IT:
Decision gate: if two blockers compete, choose the one whose resolution changes the requirements for the other. That is the earlier blocker.
Step 4 · Route Approval Record
Approve one route before doing more work.
APPROVED ROUTE:
WHY THIS ROUTE NOW:
PREREQUISITES ALREADY COMPLETE:
PROTECTED ELEMENT:
REQUIRED OUTPUT:
EVIDENCE TO RETURN:
QUALITY-CONTROL CHECKPOINT:
NEXT DECISION AFTER COMPLETION:
Choose the Approved Route
Idea
Create a Track Direction Statement.
Open route →Lyrics
Create the Song Blueprint and lyric plan.
Open route →Reference
Translate reference evidence into original direction.
Open route →One Track
Diagnose and approve the first repair.
Open route →Several Versions
Compare candidates and approve one.
Open route →Nearly Ready
Complete release-readiness review.
Open route →Incomplete Records
Build the traceable Creator Project Record.
Open route →Step 5 · Completion Return
Return with proof, not a general progress update.
ROUTE COMPLETED:
EXACT OUTPUT OR VERSION:
WHAT CHANGED:
WHAT REMAINED PROTECTED:
COMPARISON OR EVIDENCE:
RESULT AGAINST THE CHECKPOINT: passed / partial / failed
UNRESOLVED ISSUE:
NEXT DECISION:
PROJECT STATUS: Starting / Building / Comparing / Repairing / Preparing / Reviewing / Ready / Held
PROJECT RECORD UPDATED: yes / no
Completion gate: the route is not complete until its output is named, the supporting evidence is available and the next decision has been recorded.
Step 6 · Retry, Escalate or Continue
- Required output missing: return to the same route. Do not select a new one.
- Evidence is weak or versions are too similar: run one controlled comparison or revision test.
- The primary blocker changed: update the Intake Summary and approve a new route.
- Two blockers still conflict: select the earliest unresolved decision and place the other in the Project Record backlog.
- One focused judgment remains: prepare the evidence and submit a focused review request.
- The project is paused: mark it Held and record the exact restart trigger.
- The song passed quality and documentation checks: continue to release readiness or delivery.
Project Status
Use one status at a time.
StartingBuildingComparingRepairingPreparingReviewingReadyHeld
End every session with: one saved decision, output, comparison, revision plan or next action in the Creator Project Record.
Complete the Loop
The workflow succeeds when the next person—or your future self—can continue without guessing.
Success means the project has one current status, one approved route, one exact working asset, one protected element, available completion evidence and one next decision.
This workflow improves direction, consistency and documentation. It does not guarantee copyright ownership, legal clearance, platform approval, release acceptance, audience growth, sales or commercial results.
