<!--
  Full-page Markdown export (rendered HTML → GFM).
  Source: https://neotoma.io/ca/conflicting-facts-risk
  Generated: 2026-04-28T13:35:55.930Z
-->
# Conflicting facts risk

Conflicting facts risk is the likelihood that contradictory statements coexist without deterministic resolution. In production this causes unpredictable agent behavior.

## Before vs after

Before: both "office is in New York" and "office is in London" remain active with no canonical winner. After: merge rules choose one canonical value and preserve conflicting history for audit.

\# Store two conflicting facts
neotoma store --json='\[{"entity\_type":"contact","name":"Ana Rivera","office\_city":"New York"}\]'
neotoma store --json='\[{"entity\_type":"contact","name":"Ana Rivera","office\_city":"London"}\]'

# Query canonical resolved state
neotoma entities search --query "Ana Rivera" --entity-type contact

Deterministic merge logic resolves conflicts reproducibly. [Schema constraints](/schema-constraints) support typed conflict handling, and [deterministic state evolution](/deterministic-state-evolution) guarantees the same result on replay. See [silent mutation risk](/silent-mutation-risk).