Skip to content

6.7.2.5 ReconciliationRuleSet

6.7.2.5.1 Purpose

A versioned set of matching and identifier rules, together with the version of the resolver code that applies them. Changing a window or the reliability ranking creates a new version, and resolution is re-run from the evidence.

6.7.2.5.2 Questions it answers

  • Which rules produced a resolution?
  • Can a stored decision be checked by running it again?
  • Which version was in force at a given time?

6.7.2.5.3 Fields

Field Type Cardinality Description
id string (uuid) 1..1 Key.
version string 1..1 Unique.
effective_from datetime 1..1
event_rules string (JSON) 1..1 Per event type: window kind (fixed days, or one per calving interval), link days, grey-zone days (linked and flagged), incompatible values, documented classification hierarchies and attribute groups; dispatch and death are not equivalent.
Example windows are draft tolerances pending domain and country validation.
identifier_rules string (JSON) 1..1 Normalization rules for identifiers and the version of the country code list.
resolver_version string 1..1 Version of the resolution code that applies these rules. Rules + code + evidence at a write number give the same result, so a stored decision can always be checked by re-running it.
created_at datetime 1..1

6.7.2.5.4 Relationships

Referenced by

6.7.2.5.5 Rules & constraints

  • Versioned matching rules. Changing a window or the reliability ranking creates a new version; resolution is re-run from evidence.
  • Before a version is used, a sample of its automatic links is checked offline to measure precision.