Routes

Routes are outcome paths. They describe what a user is trying to get done, and the practical path through software that gets them there.

A tag can be broad, like email. A Route is more specific, like API email send. It should point toward tools that fit the job, not just tools that match one word.

API email send Find transactional email options before general office suites.
Logging to cold storage Find blob-backed log storage paths before full log platforms.
Blocked data source replacement Find alternate sources when the direct source is weak, closed, or too expensive.

Search is still a stub, but Routes are the direction: outcome-first entries that can sit above normal tags, vendors, and categories.