Skip to main content
Cross Compare stage showing multi-tier matching cascade between source and reference collections
The Cross Compare stage compares source documents against a reference collection using a cascading match strategy: exact → fuzzy → semantic → visual. Each match is classified using configurable rules, enabling drift detection, deduplication, and compliance checking workflows.
Stage Category: APPLY (Cross-collection comparison)Transformation: N documents → M finding documents (findings mode) or N documents → N enriched documents (enrich mode)

When to Use

When NOT to Use

Parameters

Core Parameters

Matching Configuration

Classification

Default classification rules:

Output Configuration

Visual Comparison

Reference & Source Configuration

Extraction Modes

Use the field value as a single element. Best for comparing whole content blocks.

Matching Cascade

The matching cascade tries each tier in order and stops at the first successful match:
If no tier matches, the element receives match_tier: "none" and the no_match_label classification.

Configuration Examples

Output Schema

Findings Mode

Each comparison produces a finding document:

Enrich Mode

Comparison results attached as a field on source documents:

Finding Fields

Performance

Reference documents are fetched once and reused across all source documents. The matching cascade short-circuits at the first successful tier, so ordering match_tiers from fastest to slowest (exact → fuzzy → semantic → visual) is optimal.
Limits:
  • Max source documents per execution: 50
  • Max reference documents fetched: 200 (configurable via reference_limit)

Common Pipeline Patterns

Drift Detection Pipeline

Catalog Match + Transform

Error Handling

vs Other Enrichment Stages