Translations
A Translation is a manufactured product artifact, built in the product's design language, to express something that exists in the product's logic but has no literal UI state. Translations make the Taste Graph visible: the aesthetic reasoning and professional reasoning that Visualist builds over time on behalf of the professional. They are not screenshots. They cannot be captured. They can only be constructed.
Translations occupy Q4 in the asset quadrant alongside Simplifieds and Recordings. They are the most editorial of the three product registers. Where a Simplified shows the real product with noise removed, and a Recording shows the real product in motion, a Translation shows what the product knows. One Translation per surface. It does not share a frame with any other product asset type.
Visualist builds a Taste Graph for every professional: an accumulated record of decisions, patterns, and judgments across their creative and professional practice. Translations are how that graph becomes visible.
The eye. What this professional's taste actually is, built from accumulated visual decisions. The colors that keep returning. The references that recur. The mood that runs through every moodboard they have ever built. The palette a client always approves even when they ask for something different.
The practice. How this professional works, communicates, and makes decisions. How they structure a proposal. How they manage a client relationship. The judgment calls they make repeatedly. That this professional always sends a check-in at the same point in a project. That a particular client takes four days to respond and asks for one revision, so the timeline has been flagged accordingly.
- Choose moments from the Taste Graph: aesthetic patterns, professional patterns, client contradictions, accumulated signals
- Use the Wolfe accent consistently to mark Vai's presence
- Keep the focal point singular and immediate
- Float the artifact with generous space on all sides
- Use Cotton or Parchment backgrounds as the default; use photo backgrounds only when the brief specifically calls for it
- Build in the product's design language: correct type, color, spacing, and border weight
- Show a screen a user can actually navigate to — that is a Simplified or Recording
- Add actions, buttons, or interactive states
- Use Tartuffo — stay in the product's type register
- Use more than one Translation per surface
- Combine with editorial photography in the same frame
- Use real client names or real client data
- Present as a screenshot or as documentation of how the product works
Run every Translation through these tests before submitting for approval. All must pass.
Does this Translation show something from the Taste Graph — a pattern, a connection, a contradiction, an accumulated signal? If the moment shown could exist as a literal product screen a user navigates to, it is not a Translation. It is a Simplified or a screengrab.
Does it create a feeling in under three seconds? "This understands me." "This noticed something I hadn't." "This is doing something I didn't ask for." If the viewer needs to read it carefully to understand what it is showing, the focal point is not clear enough.
Is the artifact floating with generous space on all sides? No bleed crop, no edge contact, no device chrome. If it looks like a cropped screenshot or a panel inside a larger interface, it is not framed correctly.
Instrument Serif, Instrument Sans, Roboto Mono only. Warm neutral palette. Correct spacing and border weight from the design system. No gradients, shadows, or effects. If a color, type style, or effect can't be found in the product design system, it does not belong.
Is Vai's presence marked with the Wolfe accent? A Translation without the Vai signal reads as a UI screenshot, not as an expression of the Taste Graph. The signal is not optional.
Are all names, data, and content fictional? No real client names, no real professional names, no real project data. Translations use representative examples only. If real data is present, replace it before the asset enters any external context.
Translations are built in code using the product's design language. The brief defines what the Taste Graph moment is and how it is expressed visually. The sequence matters: moment, then signal, then layout.
translation-[sequence]-[slug], for example: translation-001-client-color-patternAll approved Translations. Check here before building new work.
Each entry notes the Taste Graph dimension (aesthetic or professional) and the moment being expressed.