The right reading order is not “open every screen and hope they agree.” It is: first check whether the pin is plausible, then widen to the strongest ring, then decide whether the next few days are good enough to act.
Step 1: Predict is about attention, not certainty
Predict should tell a user whether a pin deserves further thought at all. It is not the promise of mushrooms. It is a disciplined filter against weak places that only look tempting because of one weather event or one personal hunch.
Step 2: Area Scan turns one point into a practical first pass
Once a pin is interesting, the next real question is where to begin around it. Area Scan should help compare rings or neighboring terrain bands so the user does not wander randomly through a large forest block. This is where habitat structure starts to matter much more than pin-level curiosity alone.
Step 3: Time Scan decides whether the outing is actually worth it
Even a good ring still fails when the date is wrong. Time Scan is the step that turns a plausible area into a go or no-go decision for an actual weekend. The useful output is not hype. The useful output is whether the next 2 to 4 days look better than waiting.
Where region context enters
The same product workflow should feel slightly different in Germany than it does in alpine or Mediterranean territories. Region pages therefore exist to explain how local forest structure, terrain, and access norms change the way users read the workflow.
Where regulation context enters
A promising place can still become a bad outing if the rule layer is ignored. Country, municipal, and protected-area restrictions should sit beside the workflow, not below it as legal fine print added too late.