Not every phantom is a disaster.
A made-up note can be a gift or a catastrophe — it depends entirely on what you're using the answer for.
It's tempting to conclude "the model makes things up, so never trust it." That's an overcorrection. The same invented chord that would ruin a chart the band reads on stage might be exactly the surprise you wanted jamming alone at midnight. The fabrication didn't change — the stakes did.
So the useful question is never "could this be wrong?" With a model, the answer is always yes. Ask instead: "what happens if it is?" When a wrong answer costs you nothing — or is even welcome — let the model run free. When it would mislead other people, or you can't easily take it back, slow down: ground it, cite it, and check.
Pick a task and see where it lands on the stakes meter — and what that means for how far you should trust the answer.
Match the caution to the cost.
Hallucination isn't a reason to abandon the model or to trust it blindly — both are lazy. It's a reason to think for a second about the downside. Low downside: let it play, your judgment is the safety net. High downside: bring the chart, ask for the source, and verify before you rely on it.
That single habit — scaling your caution to what a wrong answer would cost — is what separates people who get burned by these tools from people who get real work out of them. And when the cost is high, the surest fix is to stop asking from memory and hand the model the real material: retrieval, the next lesson.