Conflicts
What happens when a new reference contradicts something Krafa already believes, and how to resolve it.
Taste changes, and taste is also inconsistent. You can genuinely prefer dense monochrome tooling and airy pastel marketing sites at the same time. A system that silently overwrote one with the other would be wrong; a system that stored both without noticing would hand your agent contradictory instructions.
So when a new reference disagrees with an existing memory, Krafa stops and asks.
What you see
A dialog titled Conflicting design taste appears with a neutral question, something like "Your saved taste favors near-black surfaces, but this reference is built on soft pastels. Which is right?", and two cards side by side:
- Saved taste: the existing memory, its category, and its evidence
- New reference: what the incoming paste suggests instead
Your three options
| Choice | Result |
|---|---|
| Keep saved | The existing memory stands. Nothing is written. |
| Keep both | The new observation is added alongside the old one. Both go into your profile. |
| Use new | The existing memory is marked superseded and the new one takes its place. |
Dismissing the dialog with Esc or a click on the backdrop is treated as Keep saved. The safe default is to change nothing.
If several references land at once, conflicts queue up and are presented one at a time, with a 1 of 3 counter in the title so you know how many are left.
Which one to pick
Keep both more often than you'd think. Two memories that look contradictory in isolation usually aren't. "Surfaces are near-black" and "surfaces are warm off-white" both being true means you work in light and dark, and an agent reading both will handle both. Contradiction in a profile is only a problem when it's genuinely unresolved.
Use new when your taste actually moved. You changed accent colors, adopted a new type scale, stopped using a pattern. Superseding is the honest record of that, and it's what keeps a profile from being an archaeological dig through everything you've ever liked.
Keep saved when the incoming reference was aspirational rather than directive: something you pasted because it's interesting, not because you'd ship it.
If you're resolving conflicts constantly on one board, that's a signal the board is doing two jobs. Split it. Separate boards get separate MCP tokens, so pointing one project at your dense-tooling profile and another at your editorial profile costs nothing.
Superseded memories
Choosing Use new doesn't delete the old memory. It marks it superseded. Superseded memories vanish from the taste panel and are excluded from everything served over MCP, so your agent only ever sees what's currently true.
What conflicts don't cover
Conflict detection only fires when the model recognizes a direct contradiction with a memory that still exists on the board. It won't catch slow drift, where twenty references gradually pull a profile somewhere you didn't intend and no single one contradicts anything.
That's what the taste panel is for. Reading through your own profile occasionally is the only reliable way to catch it. See Curating.