Module 3 APPLY | Righteous Track Builder Project Control Guide

Free Creator Academy · Stage 1 · Module 3 · APPLY

Use this after Module 3 LEARN. The Project Control Guide is the practical control layer: identify one blocker, choose the route that owns it, return with evidence and record the next decision.

Review Module 3 LEARN →   Find Your Sound →

You are using: Project Control Guide — the working control layer for the Track Builder.

Righteous Track Builder · Project Control Guide

Keep one AI music project moving from decision to evidence to next step.

Use this working guide to capture where your project is now, identify the next blocker, choose the right Track Builder route, complete the work, and record what happens next. It is the control layer for the Righteous Track Builder—not a membership level or separate training product.

Working rule: protect what already works, name one primary blocker, choose one route, complete its required output, and return with evidence before changing direction.
1 · Project Snapshot

Record the project as it actually exists.

Starting something new?

Complete the snapshot before choosing a route. Use exact filenames, links or version identifiers wherever possible.

Resuming existing work?

Bring forward the current project status, latest approved asset, strongest element, evidence already gathered and one unresolved decision. Do not restart the project unless its goal or source material changed.

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:
Snapshot gate: another person should be able to identify the exact project, current asset, intended result and protected element without asking what you meant.
2 · 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 rule: when two blockers compete, solve the one whose answer changes what the other blocker requires.
3 · Choose the Route

Open only the route that owns the current problem.

4 · Define the Work Before Doing It

Approve one controlled piece of work.

APPROVED ROUTE: WHY THIS ROUTE NOW: PREREQUISITES ALREADY COMPLETE: PROTECTED ELEMENT: REQUIRED OUTPUT: EVIDENCE TO RETURN: QUALITY-CONTROL CHECKPOINT: NEXT DECISION AFTER COMPLETION:
Do not add another route because it looks useful. Add it only if the current blocker changes and you can explain why.
5 · Return With Evidence

Finish the route 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 work is not complete until the output is named, supporting evidence exists and the next decision is recorded.
6 · Decide What Happens Next

Continue only from the evidence you now have.

Retry

The required output is missing or the test did not answer the intended question. Stay in the same route and change one variable.

Continue

The route passed its checkpoint and the project now has a clear next stage.

Change route

The primary blocker genuinely changed. Update the snapshot and approve the new route before moving.

Hold or review

If the project is paused, record the restart trigger. If one focused judgment remains, prepare the evidence for review.

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

Your future self should be able to continue without reconstructing the project from memory.

The Project Control Guide succeeds when the project has one current status, one exact working asset, one protected element, one approved route, usable evidence and one next decision.

Module 3 handoff: when one developed working version is coherent enough to judge as a whole and its remaining issues are explicit, move into Module 4 EXECUTE to finish the work.

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.