Developer guide: conflict handling

Short answer: A conflict is a mapped field changed on both sides since the last sync (three-way comparison with stored per-field hashes). The policy of the mapping decides: PVology wins, the other system wins, review by a person, or skip. A record in conflict is never half-written; recommendations are never applied by themselves.

Verified for PVology 0.61.0 · updated 2026-10-11