# Contradictions and updates (/docs/memory/intelligence/contradictions-and-updates)
People move, change jobs, and change their minds. A memory store that keeps every version side by side hands your model two answers and lets it guess. Docklee works out which fact is current, so recall returns one answer.

<Callout type="info" title="This matters most when...">
- Your users' details change over time, such as plans, addresses, or preferences.
- Several systems write facts about the same person.
</Callout>

## How it works [#how-it-works]

1. **Find the claim.** Docklee reads what each memory asserts as a subject, an attribute, and a value. "Priya was promoted to VP" and "Priya's title is VP" are the same claim about Priya's job title, however they're worded.
2. **Compare with what's known.** A new memory is checked against memories about the same subject and attribute.
3. **Decide.** The outcome depends on how the two memories relate.

| Relation | Example | What Docklee does |
| --- | --- | --- |
| Update | "Lives in Denver" after "Lives in Austin" | The new memory becomes current. The old one is marked superseded and kept as history. |
| Conflict | "Budget is $50K" and "Budget is $100K" | Both stay, and both are flagged for review. |
| Partial | "Prefers email" and "Calls for urgent issues" | Both stay current. The overlap is noted. |
| Agreement | The same fact from two sources | Both stay, and both gain confidence. See [Confidence](/docs/memory/intelligence/confidence). |

Memories that don't state a fact about someone or something, such as "We talked about the roadmap", are context, and they're never replaced.

## What recall returns [#what-recall-returns]

For each claim, recall returns the newest memory that's still valid. A superseded memory never comes back as the current value, but it's never deleted by an update either. You can see the full history in the dashboard.

<CodeTabs items={['Python', 'TypeScript']}>
  <Tab value="Python">
    ```python
    dock.capture("Priya's job title is Director.", type="entity", end_user="user_31d0")
    dock.flush_sync()

    dock.capture("Priya was promoted to VP of Sales.", type="event", end_user="user_31d0")
    dock.flush_sync()

    records = lynk.recall_sync("What is Priya's job title?", end_user="user_31d0")
    ```
  </Tab>
  <Tab value="TypeScript">
    ```ts
    dock.capture("Priya's job title is Director.", { type: 'entity', endUser: 'user_31d0' });
    await dock.flush();

    dock.capture('Priya was promoted to VP of Sales.', { type: 'event', endUser: 'user_31d0' });
    await dock.flush();

    const records = await lynk.recall("What is Priya's job title?", { endUser: 'user_31d0' });
    ```
  </Tab>
</CodeTabs>

Recall returns the VP memory as the current title. The Director memory stays in the space as history.

## Conflicts go to review [#conflicts-go-to-review]

When Docklee can't tell which fact is right, it doesn't guess. Both memories stay active and appear in the **Review** tab of the memory space, where a person approves, corrects, or removes them. See [Review and correction](/docs/memory/governance/review-and-correction).

<Callout type="warn">
Capture an update as a new memory, in plain words. Don't try to find and edit the old memory yourself. The new memory is what lets Docklee mark the old one as superseded.
</Callout>

## Next steps [#next-steps]

You know how facts stay current. Learn how Docklee scores how much to trust each one.

<Cards>
  <Card title="Confidence" href="/docs/memory/intelligence/confidence" description="How trust in a memory rises and falls." />
  <Card title="Review and correction" href="/docs/memory/governance/review-and-correction" description="Settle conflicts Docklee flags." />
  <Card title="Ranking" href="/docs/memory/intelligence/ranking" description="How current facts reach the top." />
</Cards>
