# Contradiction flagging

A reusable skill the "Synthesize interview transcripts into JTBD themes" recipe pulls in. Add it once and every agent on the team can use it.

Compare this batch's findings against stored synthesis memory and surface disagreements instead of overwriting them.

## Method
1. Load the running JTBD/theme inventory from memory before rolling up this batch.
2. For each new theme or JTBD, check whether a prior synthesis made a claim that conflicts with it.
3. If it reinforces a prior finding, increment its supporting-interview count in memory.
4. If it conflicts, do not silently replace the prior finding — record both, with their respective evidence and dates.
5. Write a short contradiction note explaining what changed: new segment, new context, or a genuine reversal.
6. Leave the resolution of a contradiction to the PM — this skill surfaces it, it does not decide which finding wins.

## Rules
- Never overwrite a prior synthesis finding without a flagged contradiction note — silent overwrites are a hard fail.
- A contradiction needs its own supporting quote, same verbatim standard as any other finding.
- Low-confidence disagreement (one interview against many) is still flagged, just labeled with its weight of evidence.
- Contradictions accumulate in memory across batches; do not delete a past contradiction once logged, even after it's resolved.

## Output
A contradictions list: each entry names the prior finding, the new finding, supporting evidence for both, and a status (open/resolved).