"Confidently wrong is the worst thing a learning tool can be. Honestly unsure, then corrected, is the best."
Automatic Analysis Is Genuinely Fallible
Tier A is mature, not infallible. Chord and key detection get jazz tensions wrong, miss fast modulations, and waffle on songs with ambiguous tonal centers. This isn't a bug to be eventually fixed away — it's the nature of inferring harmony from audio. Capo has the same limitation, and Capo's users routinely correct its output. Pretending otherwise would mean teaching learners wrong harmony with total confidence — the worst possible failure for a tool whose whole job is to teach.
Make the Fallibility a Conversation
So Bonfire treats analysis as a proposal, not a verdict. The engine produces its best guess with a confidence; Pippa surfaces it as a question — 'I hear E minor here, does that match your ear?' — and the human confirms or corrects. The model updates from the human's answer. The human is always the final authority on the music. That loop turns a limitation into a teaching moment: the learner is invited to listen critically instead of passively trusting a label.
Honesty as a Design Value
This is a stance, not just a UX pattern. A learning tool earns trust by being honest about what it doesn't know. 'I'm 70% sure this is E minor' builds more trust than a silent, confident 'E minor' that's wrong one time in four. Human-in-the-loop isn't a fallback for when the AI fails — it's the correct shape for a tool whose user is supposed to be developing their own ear. Being correctable is the feature.