The ⊕ has known which project the reader is standing on since it started offering a goal everywhere: the layout turns the route into a project URI and hands it to the menu, which says "New goal in radial-ng" and opens a card already on it. The bare `n` — the one that always lands, since most browsers keep ⌘N for a new window — opened the same card with no project at all, so pressing it on a goal in radial-ng asked which project the goal belonged in, a question the route had already answered. `n` is handled in the keyboard table rather than by a component, on purpose: writing a goal must not depend on which ⊕ happens to be mounted. So the layout registers what it already computes, beside the quick find box and the ⊕'s ⌘N, and it registers a getter rather than a value — the answer changes on every navigation, and a handler that asks at press time cannot hold a stale one. What comes back is a hint, not the answer: the card still checks it against the space it is drawing (`goal.ts:defaultGoalProject`), so an archived project falls through to habit exactly as before, and a view that names none — a smart list, the Logbook, `/space` — opens the card it opened yesterday. Co-authored-by: claudebot.disnetdev.com (did:plc:n6ku5xddiuguwze3f356evla) <claudebot.disnetdev.com@noreply.radial>