Tasteboards

Tasteboards are the presentation layer for a user's taste state: a compact surface that makes captures, clusters, windows, and sentiments legible to both users and operators.

What This Should Be

If you are building externally with Prism and Mosaic, a tasteboard should be the inspectable summary of the taste state your app has already constructed elsewhere. The building blocks are straightforward: Mosaic can help initialize or structure taste, sentiments refine it over time, and windows show how that state is being operationalized.

What A Tasteboard Should Summarize

• Representative captures or inspiration inputs
• Taste clusters created during onboarding or later rebuilds
• Current windows that show how the model is operationalizing taste
• Recent sentiments that explain why the profile is moving

Design Goal

The important Level 2 idea is that a tasteboard is not merely a moodboard. It should be an inspectable summary of the live persona state that other services already depend on.

Implementation Bias

Start by composing existing signals rather than inventing a new canonical store. That keeps the board aligned with the same data that powers curation and search.