Conflict Detection

Woxpas automatically finds contradictions in your notes and surfaces them so you can keep your knowledge accurate.

How it works

Every time you add a file, note, or capture to your vault, Woxpas extracts structured claims — facts like dates, statuses, roles, and relationships. It then compares each new claim against everything already in your vault using semantic matching. When two claims about the same thing disagree, a contradiction is created and queued for your review.

This happens automatically in the background. You don't need to configure anything — contradictions will appear in the Contradictions page in the sidebar whenever they're detected.

What gets extracted

Claims are structured as (subject, predicate, value) triples. Woxpas extracts these from several sources within your notes:

Events — Scheduled times, descriptions, and locations from extracted calendar entries.
Follow-ups — Due dates, assignees, and statuses from commitments and action items.
Knowledge claims — Free-form facts about roles, technologies, definitions, relationships, quantities, policies, preferences, and more.

Types of conflicts

Not all contradictions are the same. Woxpas classifies each one so you know exactly what's going on:

Value mismatch

Two claims about the same thing have different values. For example, one note says the meeting is at 2 PM while another says 3 PM. These are the most common contradictions.

Temporal update

Values conflict but represent a change over time. For example, a project status went from “in progress” to “completed”. Woxpas flags these so you can confirm the update is intentional.

Entity uncertain

The system isn't sure if two names refer to the same person or thing. For example, “John Smith” and “J. Smith” might be the same person — or might not. You'll see a “Did you mean?” prompt with Yes/No buttons to clarify.

Updated version

A newly uploaded file is detected as an updated version of an existing file. Woxpas shows a side-by-side diff so you can see exactly what changed and decide whether to keep the old version or archive it.

The Contradictions page

All detected conflicts live in Contradictions, accessible from the sidebar. The page is split into two tabs:

  • •Unresolved — conflicts waiting for your input, grouped into three sections: updated versions, needs your input (entity uncertain), and regular conflicts.
  • •Resolved — conflicts you've already dealt with, shown as a historical record.

You can filter by type (events, commitments, entities) and sort by urgency, date, or number of conflicting claims. Each conflict card shows the subject, the conflicting values, which files they came from, and an urgency indicator.

Resolving conflicts

Click any conflict card to open the detail modal. You'll see all the evidence — each claim's value, its source file, the date it was captured, and the surrounding context from the original text.

Choose one of the resolution options:

Pick a winner — One claim is correct. The others are marked as superseded. If the winning claim updates something like an event time, Woxpas updates the source data too.
Both valid, different context — The claims are about different things that happen to share a name. Woxpas can split them into separate entities — for example, splitting "Emma" into "Emma (marketing)" and "Emma (engineering)".
Temporal sequence — The conflict is just an update over time. Both claims stay active as a valid timeline.
None correct — All claims are wrong. Optionally provide the correct value and Woxpas creates a new authoritative claim.
Merge — Combine information from multiple claims into one. Useful when each claim has part of the full picture.

File version detection

When you upload a file that Woxpas recognises as an updated version of something already in your vault, it creates a special “updated version” conflict. The detail modal shows a side-by-side diff of both files so you can see exactly what changed.

If you confirm the new file replaces the old one, Woxpas archives the old version and automatically resolves any related claim-level conflicts between the two files.

Cross-agent conflicts

If you use multiple AI assistants through MCP (like Claude and ChatGPT), Woxpas tracks which agent contributed each piece of evidence. When a conflict involves claims from different agents, it's tagged as a cross-agent conflict with a badge showing which agents are involved.

This helps you understand when different AI tools are giving you contradictory information.

Urgency levels

Each conflict gets an urgency level based on its type and what it affects:

  • •High — conflicts involving events (wrong meeting times matter) or contradictions with previously resolved claims.
  • •Medium — conflicts involving commitments, file version updates, or knowledge claims about deadlines and statuses.
  • •Low — other knowledge conflicts where the stakes are lower.

Daily digest integration

The top 3 highest-urgency unresolved conflicts are included in your daily digest. Updated file versions appear in their own section, while knowledge conflicts are listed with their conflicting values and source files.

If you have recurring contradictions in a particular area (like dates or statuses), the digest also surfaces pattern nudges — for example, “Date details keep conflicting in your notes (5 cases)”.

Using via MCP

Connected AI assistants can interact with conflicts through two MCP tools:

  • •list_conflicts — browse unresolved contradictions in your vault.
  • •resolve_conflict — resolve a specific conflict by choosing a resolution type and winner.
PreferencesSettings