Why the memory layer matters
A design system used to be a snapshot: a set of tokens, components, and documentation frozen at the point a team wrote them down. That worked when humans were the only ones reading it. It does not work when agents are writing against it all day.
Snapshot vs. memory
A snapshot is a point-in-time artifact. Figma libraries, static docs sites, shared style guides: they all describe how the system looked when someone described it. They carry no direction, no sequence, no record of what changed or why.
A memory is longitudinal. It records not just the current state but the history that led there: what superseded what, which decisions held, which drifted, where the pattern was adopted and where it was skipped. Memory gives an agent, or a reviewer, a way to reason about the system across time, not just a frozen frame.
What memory unlocks
Concretely, the memory layer gives preset AI four capabilities a snapshot can't:
- Identity across change. When a token is renamed or a preset splits, the memory tracks the lineage. An agent referencing the old name still resolves correctly.
- Drift as a signal, not a bug. The memory knows what used to be canonical. When an agent deviates, preset AI can tell the difference between a deliberate change and a mistake.
- Governance that ages well. Forbidden primitives, context rules, and enforcement decisions carry their own history. A new team member sees the reason, not just the rule.
- Deprecation without erasure. Removing a pattern does not delete its record. The supersession is preserved, and every agent that encounters the old name gets pointed at the replacement.
How preset AI stores memory
The memory is a typed, versioned graph. Every artifact (preset, pattern, token, rule) has a stable identity independent of its current name or location. Edges record supersession, composition, and usage. The graph is queryable via MCP, shipped to every agent in your stack.
This is the move that separates preset AI from smarter prompt pasting. A prompt is a snapshot an agent takes home; the memory is a shared surface an agent returns to every time it works.
If you are familiar with design tokens as a format (Style Dictionary, Design Tokens Community Group), preset AI is the layer above: it treats your tokens as one kind of memory and adds identity, history, and governance to the rest of your system.