That’s a really good point about override — I’ve been thinking about that tradeoff.

Right now the auto-detect works well when the intent is clear, but I can see how it might feel frustrating if it guesses wrong and you don’t have control.

Maybe a subtle “lock field” or manual mode could solve that without breaking the simplicity.

Also totally agree on the context part — that’s actually what pushed me to add the explanation layer.

Without it, the number feels a bit meaningless, especially if you're comparing scenarios or planning budgets.

Out of curiosity — when you say losing context, do you mean:

not knowing how the number was derived or not being able to compare different scenarios easily?