Document Your AI Music Project | Righteous Track Builder

Record what happened before memory replaces evidence. Use the route that matches what you already know about the project.

Righteous Track Builder · Creator Project Record

Give the project a memory.

This is a continuity layer for Complete Access. Keep a current record of what you are building, what has already been decided, what evidence supports those decisions, what is still unresolved and what you will do next.

The record is not extra homework or a gate. It prevents you from restarting the same thinking every time you return. Update only the fields that changed, and use it when preserving context is useful.
Coming from Bee Righteous Day 1?

Move your Creator Profile into the active project.

If you just completed Creator Profile v1.0, do not repeat the identity work. Transfer the approved decisions below and treat them as the starting context for the project.

Carry forward

  • artist or project name;
  • creator identity statement;
  • Core Pursuit;
  • intended audience;
  • primary genre and supporting influences;
  • three sonic pillars;
  • vocal identity;
  • creative boundaries;
  • first-song mission.

Bring forward unresolved items too

A useful record does not pretend every question is settled. Copy your unresolved-decision list into this record. You can use Track Builder or an already-known specialist route to work the next important issue.

Day 1 is not repeated. The profile becomes evidence for the project.
Core Project Record

Keep these fields current when they matter.

Project / artistName the one active project this record belongs to.
Current purposeWhat are you trying to make or move forward now?
Core PursuitPaste the approved statement from Creator Profile v1.0.
Intended audienceWho should this work serve or reach?
Identity controlsPrimary genre, vocal direction, three sonic pillars and creative boundaries.
First-song missionWhat must this first track communicate, demonstrate or test?
Strongest element to protectWhat is already working and should not be lost during revision?
Current asset / versionExact filename, link, generation ID or other identifier for the material you are judging.
Earliest unresolved blockerThe first meaningful decision preventing forward movement.
Evidence from this sessionWhat did you compare, test, create, revise or learn?
Approved decisionWhat changed, what was kept, or what was rejected—and why?
Next actionOne concrete next move. Avoid a vague task such as “work on song.”
Resume rule: when you return, use the current asset, last approved decision and next action if they help you re-enter quickly. If you already know the exact specialist job, you do not need to re-diagnose it first.
Session Update

End a working session with four useful lines.

1. I worked on…

Name the exact project stage, asset or question.

2. I learned / changed…

Record the evidence or meaningful difference.

3. I approved…

State the decision that now becomes project context.

4. Next I will…

Write one action specific enough that your next session can begin without reconstructing the previous one.

Evidence Layer

Add deeper documentation when the project needs it.

As the track develops, the Project Record can also carry the provenance and rights evidence needed for professional execution. You do not need every field on the first day.

  • approved primary version with exact filename, link or identifier;
  • AI platform, model, creation dates, prompts and generation links where available;
  • selected and rejected versions with the reason for the final choice;
  • human-written, performed, selected, edited, arranged or produced contributions;
  • source material, collaborator, voice, sample and artwork permissions or unresolved gaps;
  • version history and significant changes;
  • rights, disclosure, claim-scope and release decisions;
  • evidence index connected to real files;
  • status marked Draft, Reviewed or Final.
Reconstruct

Human Contribution Record Checklist

Use when contribution history is incomplete.

Open the Free Checklist
Organize

Rights + Contribution Master Tracker

Use when you need a reusable evidence and permissions workspace.

Build the Master Record
Important: documentation supports evidence and professional execution. It does not create rights, clear unauthorized source material or guarantee copyright registration, licensing approval or platform acceptance.
Continue the Project

Choose the next route based on what you already know.

If you are unsure what the next blocker is, use Track Builder. If you already know the job, use the specialist shortcut instead. Complete Access should reduce unnecessary navigation, not manufacture it.

Use Track BuilderCompare VersionsRepair a SongCheck Release Readiness
Use Track Builder when diagnosis is the problem. Use a specialist route when the problem is already obvious. Bring the result back to the Project Record when preserving that evidence will help the next session.

ASK JACK becomes useful when the relevant self-directed work is complete and one focused judgment still remains.