Define and prove the Sound Identity that production work must protect.
Open FIND →AI Music Production Intelligence | Find Your Sound
AI Music Production Intelligence
Find Your Sound — Create and Finish the Work
Production Intelligence answers one question: How do I take a promising musical idea and make it controlled, intentional, finished, and production-ready?
Genre Intelligence = WHAT am I trying to make?
Production Intelligence = HOW do I make it well, finish it, and know it is ready?
This is not a 100-step course. JR Production Intelligence contains 100 specialist systems, organized here into a 10-stage professional production path. Use the stages to know what to do next; use the specialist systems when you need deeper technical control.
Before You Start
You should have a musical idea, creative direction, or promising draft. If you still do not know what style, genre, or sonic identity you are aiming for, start with Genre Intelligence first.
WHERE THIS FITS INSIDE FIND YOUR SOUND
Production Intelligence is specialist support, not a second Sound curriculum.
The active Find Your Sound stage owns the decision. Production Intelligence gives you deeper producer-level references when that stage exposes a technical question. Use the smallest relevant system, save what it teaches you, then return to the stage that owns the project.
Turn direction into a repeatable construction and comparison process.
Open BUILD →Diagnose, repair and verify the smallest useful changes without losing what works.
Open CONTROL →Finalize exports, files, evidence and the handoff-ready asset package.
Open PACKAGE →Deploy, measure and systemize audience growth using an approved package.
Open the Six-Gate Road →Use proven evidence to test one responsible commercial model after the work and rights position are ready.
Open the Six-Gate Road →Free Modules 1–4 →Track Builder →Tools Directory →
Verified paid-road language: the live Find Your Sound DEVELOP product defines the complete sequence as FIND → BUILD → CONTROL → PACKAGE → SCALE → MONETIZE. Legacy versioned page handles remain in place until each owner is deliberately migrated with redirects.
CURRENT IMPLEMENTATION · SUNO V6
Use v6 to test the production system. Do not rewrite the production system around v6.
JR’s paid Suno account currently shows v6 · Pro, v6-wild · Pro and v6-mini. That gives us a current implementation environment for real Find Your Sound work, but it does not change the production sequence below and it does not prove universal rollout timing.
v6 · Pro can be used as the current premium implementation lane while the same brief, Protect 3 and comparison criteria remain fixed.
v6-wild · Pro belongs where deliberate exploration serves the production question. It should be compared against the same project evidence rather than treated as automatically better.
v6-mini is Suno’s free model option. It is not Free Creator Labs, the free Genre Starter Kit or a JR training tier.
Evidence rule: pages that only need evergreen production logic can keep moving now. Pages that depend on actual v6 behavior, repair quality, reference response, version comparison or a real finish decision will wait for JR’s worked song examples rather than inventing evidence.
The Production Intelligence Path
1. Define Production Intent
Goal: turn the idea into explicit production requirements before generating or editing.
Complete: production intent, protected creative decisions, constraints, quality target, and first controlled test.
Pass when: you can state what must remain true, what may change, and what you are testing next.
If it fails: reopen the brief instead of adding more prompt complexity.
2. Analyze References & Translate Them Into Decisions
Goal: use references as evidence without copying identity.
Complete: useful observations translated into original production decisions.
Pass when: every retained reference finding has a reason, an implementation decision, and an originality check.
If it fails: replace the reference or reopen Stage 1.
3. Generate, Iterate, Compare & Select
Goal: create controlled candidates and choose a keeper using evidence rather than novelty.
Complete: a bounded candidate set, comparison criteria, diagnosis, and keeper-or-reject-all decision.
Pass when: the keeper wins against explicit criteria and you know what still needs production work.
If it fails: return to direction/reference. Do not plan to fix a weak source in mastering.
4. Shape Arrangement, Energy & Performance
Goal: make the chosen idea function as a complete performance over time.
Complete: section map, energy curve, transitions, instrumentation roles, and vocal/performance plan.
Pass when: structure has intentional contrast, progression, and transitions with no structural problem deferred to the mix.
If it fails: reopen arrangement or replace the weak source.
Song Structure Engineering → Vocal Direction & Performance Control →
5. Stabilize Vocals, Sources & Stems
Goal: establish usable, recoverable source material before detailed repair or mixing.
Complete: protected source version, stem/take choices, transformation/replacement decisions, and source lineage.
Pass when: critical sources are identifiable, usable, recoverable, and known extraction artifacts are documented.
If it fails: return to source selection or arrangement rather than stacking repair processes.
Suno Stems specialist implementation → Vocal Extraction specialist implementation →
6. Edit, Repair & Reconstruct
Goal: correct timing, noise, artifacts, alignment, and local defects before judging the mix.
Complete: bounded cleanup, timing/pitch/phase checks, fades, repairs, and replacement decisions.
Pass when: edits are not distracting and no known technical defect is being passed downstream.
If it fails: return to source/stem decision rather than repairing indefinitely.
Replace Section — Suno specialist implementation → Audacity 4 recording, repair, restoration & editing implementation →
7. Build the Mix
Goal: create balance, clarity, depth, impact, and intentional movement from stable sources.
Complete: balance hierarchy, gain/headroom, EQ, dynamics, low-end, spatial/stereo, routing, and automation decisions.
Pass when: the mix communicates at low and normal levels and the master chain is not hiding defects.
If it fails: reopen arrangement, source, or editing when extreme processing is the only way to make the mix work.
8. Master & Verify Translation
Goal: create a controlled final master without using mastering to conceal upstream defects.
Complete: master candidate, sensible reference comparison, metering/true-peak checks, playback translation, and correct exports.
Pass when: mastering introduces no new distortion, pumping, or harshness and the production translates acceptably.
If it fails: return to mix or earlier structural owner by cause. Do not simply limit harder.
9. Version, Document & Package
Goal: turn one approved production into controlled deliverables without losing source authority.
Complete: master-of-record, required alternates, consistent names, source/tool lineage, human-contribution notes, and export specs.
Pass when: every derivative points to an approved source and there is no version ambiguity.
If it fails: repair version/provenance; if an alternate requires creative restructuring, reopen Stage 4.
Project Proof & Version Evidence → Human Contribution Documentation →
10. Final Production QA & Release-Prep Handoff
Goal: prove the work is production-ready and package it for the next domain without turning Production Intelligence into distribution or monetization strategy.
Complete: final QA of masters, stems, required alternates, naming, provenance, file readability, and handoff state.
Pass when: the result is Ready, Ready with a documented limitation, or Not Ready with a named stage to reopen.
Next: hand the approved production to release/platform, communication, or future monetization workflow.
How the 100 Specialist Systems Fit
The specialist library remains intact. The numbers are an index for deeper technical work, not a required linear 100-step journey.
- #1–14: Direction & control language
- #15–34: Musical construction, vocals, hooks, and performance-fit controls
- #35–41: Reference → generation → selection → diagnosis → repeatable BUILD
- #42–47: Repair and version governance
- #48–56: Local revision, source transformation, and hybrid editing implementations
- #57–60: Studio control, production craft, mixing/mastering overview
- #61–70: Technical cleanup, standards, proof, provenance, delivery, and cross-tool handoff
- #71–91: Mixing and production specialist systems
- #92–94: Editing/reconstruction and hybrid performance
- #95–100: Metering, finalization, translation, and commit decisions
Platform Principle
The curriculum is platform-neutral. Suno, Udio, Musicfy, ElevenLabs, DAWs, stem tools, vocal tools, and mastering services are implementation branches. The production principle answers what decision must be made and how quality is verified; a platform branch answers how to implement that principle here. For Audacity specifically, use the Audacity Creator Production Hub rather than scattering software instructions across the 10-stage decision path.
Production Quality Rule
Do not push a known upstream failure downstream. Mixing is not a substitute for keeper selection. Mastering is not a substitute for arrangement. If a stage fails, reopen the stage that owns the failure.
Your Next Action
If you have an idea but no controlled production plan, begin with Stage 1: Define Production Intent. If you already have a draft, identify the earliest stage above that is still failing and start there.
