Brief
GVD links document versions and resolves rule conflicts locally, without an LLM
A new paper describes GVD, a pipeline that treats versioning, duplicate detection and contradiction detection as one cross-document problem rather than isolated pairwise tasks — and runs entirely locally. The abstract reports its methods and results but gives no code, licence or availability detail, so treat the numbers as the authors' reported figures, not an independently reproduced result.
GVD assigns incoming documents to version families using bidirectional rule alignment, then compares each document's rules against the family memory to sort them into duplicates, contradictions, asymmetric refinements and new knowledge. A technique called Counterfactual Span Probing handles related pairs that inference misclassifies as neutral. Relation-specific policies then suppress duplicates and escalate only consequential changes for review, keeping version lineage as an audit trail.
The reported evidence comes from 120 enterprise documents processed as 140 ingestions across 59 version families: an F1 of 0.97 for version-family construction and 0.94 for rule-level consistency, with CSP lifting rule consistency from 0.90 to 0.94. The pipeline runs fully locally, with no large language model.
Our reading
Anyone maintaining a policy, guideline or procedure repository has the same recurring problem: the same rule appears in several wordings, and newer documents quietly refine or contradict older ones. Doing that comparison pairwise, and stopping once a pair is labelled, misses the collection-level picture. A local, LLM-free option is relevant to teams that cannot send regulated or internal document…
What to do or watch
Watch for a code release or replication on your own repository before planning adoption; the unresolved question is whether GVD is available to run and how it behaves outside the tested enterprise document set.
Source details and supporting facts
Each line is stated by the page named above it.
Stated by arXiv
- GVD unifies cross-document version linking with rule-level conflict resolution under an auditable update policy.
- The pipeline runs fully locally, with no large language model.
- On 120 enterprise documents processed as 140 ingestions across 59 version families, GVD reaches an F1 of 0.97 for version-family construction and 0.94 for rule-level consistency.
- Counterfactual Span Probing raised rule consistency from 0.90 to 0.94.
- Relation-specific policies suppress duplicates and escalate only consequential changes for review, retaining version lineage as an audit trail.
Sources
- arXivText stored 17 September 2026
How this story was checked. Written from the 1 page listed above, stored 17 September 2026; claims checked against that stored text on 17 September 2026.
What that means
- 5 of 5 reported statements were confirmed against the page that carries them; the rest were removed rather than published.
- Figures in the text were required to appear in the stored source text: yes. Identifiers: yes.
- The check reads stored text only: no claim rests on a fresh look that did not happen.
- Where the reporting was silent, the text says so instead of filling the gap.