Arrival context is not destination ownership
Brussels can explain airports, international trains, first nights, and day-return pressure. Those are real reader questions, but they do not automatically make BelgianPremier a Brussels guide.
The hub should use Brussels to frame choices. If the reader wants a full Brussels trip, the Belgium routing layer should acknowledge that need without pretending the current destination portfolio owns it.
The handoff starts with time margin
A reader landing late, changing trains, or protecting a return connection needs a different answer from someone with two nights and a car. Brussels is where those timing pressures become visible.
That is why the map treats Brussels as context. It helps the reader decide whether a Flanders city, Dinant, or the Ardennes is still a clean move for the trip they actually have.
Do not let the hub collapse into the capital
Country hubs often drift toward the capital because it is the easiest place to explain. BelgianPremier should resist that. The Belgium product graph is stronger when Brussels clarifies routes instead of taking over every page.
When Brussels is only the staging point, the next click should move outward. When Brussels is the whole trip, the hub should keep the boundary honest.