Field Resolution
When a document is processed, each extracted field is resolved against the registry using a three-band matching model. The bands determine whether a match is accepted automatically, flagged for confirmation, or treated as a new field.
| Parameter | Type | Description |
|---|---|---|
| Auto band | ≥ 0.80 similarity | High-confidence match. The field is linked to the existing registry entry and its occurrence count is incremented. |
| Confirm band | 0.50 – 0.79 | Candidate match. The field is linked but flagged for manual review in the reconciliation queue. |
| New band | < 0.50 | No match found. A new Tier 3 field and cluster are created in the registry. |
Resolution runs concurrently across documents. Each document's fields are resolved in an isolated transaction to prevent lock contention. Occurrence rates are updated after each transaction commits, keeping the registry eventually consistent without blocking concurrent ingestion.
Pending confirmations from the confirm band appear in Resolution → Pending Confirmations. Accept to merge into an existing cluster, or reject to create a new field.