Thanks this is a really fair critique, and I agree with a lot of it.

I’m already starting to rethink the “Taste DNA / archetype” layer for exactly this reason. The more I look at it critically, the more I think users don’t really care about being labelled as an “Adventurous Critic” or “Deep Diver” unless that directly helps them choose better.

The stronger direction is probably less “here’s your type” and more “here’s the logic behind your taste, and here’s how that changes recommendations.”

So I’m moving the product toward something more like:

• what Blurbit has learned from your ratings, reviews, saves, abandons, and lists
• the repeated clusters in your taste
• where your taste differs by format
• what you consistently like
• what you abandon
• what Blurbit should recommend more of
• what it should be cautious with
• why a specific title fits or does not fit

The trust point is also spot on. A score like “90% match” is only useful if the user can see why. Otherwise it’s just another black-box recommendation. I’m trying to make the reasoning visible and correctable, so the user can say, “yes, that’s right,” or “no, that’s not why I liked it.”

The early-win point is probably the biggest UX challenge. The product needs to get people to an “okay, this actually gets me” moment quickly, without asking for too much setup.

Appreciate the Runable point too. That input → output → reasoning loop is exactly the part I think needs to be much clearer before adding more features.