Patterns before components.
A short note on what a design system for AI actually is, and why most organisations are building the wrong one. Grounded in twelve years of design-system work at Shell, Roche, Philips and ING, and applied to the AI products I now build.
- Role
- Design lead and architect
- Duration
- Ongoing, applied in every AI product I build
- Vertical
- Any organisation building or rolling out AI tooling
When teams ask about a design system for AI, they usually mean components. Buttons, input fields, message bubbles, a streaming-text indicator. That is the easy part, and the vendors publish it for free.
The hard part is the system that decides how AI gets context, how it shows what it knows, where humans take over, and what gets remembered. The components live downstream of that. If the patterns underneath are not designed first, no UI saves the product.
Four pattern families
Context. How data flows into the AI's working memory, when retrieval happens, how recency and importance are weighted, what the user can see and edit, what the fallback is. Open Brain implements this in production, with three task-aware retrieval modes and explicit decay.
Trust. How confidence is shown, how sources surface inline, how the system signals an irreversible action, how it recovers from a mistake. At Memortium this is enforced in code. Every portrait validated against ArcFace cosine similarity before delivery. If in doubt, do not deliver.
Handoff. How the AI knows when to hand off, what context it passes, how the human sees that context, how the conversation resumes. The Memortium service bot does this. When the bot reaches its limit it hands the conversation off with full context attached. The customer never repeats themselves.
Memory. What gets remembered by default, what the user can see and edit, how memory is shown when it influences a response, how stale memory gets pruned. Open Brain again. Monthly decay, weekly consolidation, "remembered from" attribution.
Agent role design
Agent role design lives across all four. Knowing what role an agent is allowed to play, what model fits the role, where the safeguards sit when it reaches its limit. Right role, right model, right safeguard. That is the design system part. The components follow.
Why this matters
If you are building or rolling out AI tooling, the first investment is not picking a frontend framework. It is documenting these four families so your team can build against them consistently. That is the work, and it connects directly to the rollout in Case 03 and the governance program in Case 07.