Naming Engine: How Kora Understands Stems, Versions, Keys, and BPM

Kora includes a sophisticated naming system that does far more than "rename files."
It functions like a domain-aware parser + classifier + audit engine for music deliverables.

What the Naming Engine does

Kora's naming stack can:

• parse filenames into structured meaning (title, version, stems, mix type, BPM, key)
• detect common production-music conventions
• infer missing details from context (project/album)
• log confidence + reasons
• flag issues and propose fixes
• learn patterns over time (local learning primitives)

What this means in plain English

Kora can look at a pile of exports like:

• MyCue_MAIN_v3_120bpm_Am.wav
• MyCue_STEM_DRUMS.wav
• MyCue_ALT_NoDrums.wav

…and reliably understand:

• which is the "main"
• which are stems
• which are alternates
• what the BPM/key/version are
• whether naming is strong enough for delivery
• what to fix to reach "delivery confidence 100%"

What are Quick Answers?

Q: Does Kora automatically understand stems and alternate mixes?
A: Yes—Kora parses filenames into structured meaning (stems, versions, mix types, BPM, key) and flags issues.