Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:05:20 UTC

SIE.5:4 - Solution

Frame identity as a source-qualified, grain- and interval-specific disposition for one receiving use. Preserve every source identifier and the applicable context or assignment, including its issuer when it was issued. Compare the entity criteria, relation evidence, version/effectivity, and authoritative decisions that matter. Return same, different, part, version, variant, alternate-description, family, or unresolved only at the precision supported; do not force every useful relation into identity.

SIE.5:4.1 - Pattern-Use Unfolding

  1. Name the receiving identity question. State which mapping, claim composition, query, or decision needs an identity premise and what a wrong merge or split would change.
  2. Fix entity grain and interval. Name the relevant individual or occurrence kind, part-whole level, version/configuration, lifecycle state, jurisdiction or organization, and time/effectivity interval.
  3. Resolve each source entry. Use SIE.2 to establish what each entry can designate. Recover its assignment and issuing authority when it was issued, or the rule and context used to interpret it. Retain the applicable syntax, restrictions, source edition and provenance. If the evidence leaves several candidates or fails to identify one, record that outcome.
  4. Separate candidate relation kinds. Consider same individual at the stated grain, different individuals, part/whole, earlier/later version or specialization, variant, alternate description, an individual satisfying a type criterion, or membership in a declared product family. Keep the relation unresolved if more than one reading still fits. Do not use one boolean until the use needs only that distinction.
  5. Collect discriminating evidence. Use issuer records, source assertions, configuration/effectivity, provenance, physical or domain characteristics, event histories, and counterexamples. A shared string or co-occurrence is only candidate evidence.
  6. Recover authority. Identify who may bind a source identifier, govern the master identity, decide authoritative values or establish the domain relation. SIE records the disposition for its stated use under those authorities.
  7. Assign the narrowest warranted disposition. State conditions, confidence or uncertainty where meaningful, rejected alternatives, and unresolved evidence. Preserve source IDs even for accepted same-entity rows.
  8. Link consumers to the identity disposition. Reference the disposition from every mapping, claim composition, interface row, and identity test that relies on it. Never copy only the merged key.
  9. Test difficult cases and reopen. Include identifier reuse, split/merge, version/configuration change, part-whole confusion, contradictory source events, and absent-link cases. State the source or observation change that reopens the row.

SIE.5:4.2 - Record the Result

Identity positionRequired content
identity question and usereceiver, dependent action, wrong-merge/wrong-split consequence
entity boundarykind and grain, part-whole level, version/configuration, interval/effectivity, relevant context
source identifierseach source entry, the supported referent, remaining candidates or unresolved designation, the relevant rules and context or the assignment and its issuer, restrictions, edition and provenance
candidate relationssame, different, part, version/specialization, variant, alternate description, family, unresolved alternatives
warrantevidence, counterevidence, counterexamples, uncertainty/confidence, rejected alternatives
authorityscheme-local, master-data, domain, and receiving-decision scopes
dispositionnarrowest warranted relation or unresolved result, conditions, source-ID preservation rule
downstream and reopenmapping/composition/interface/test references and the change or observation that reopens the disposition

SIE.5:4.3 - What Changes in Practice

The integration stops minting a common key as proof of identity. Every load-bearing join points to a disposition with grain, interval, source identifiers, evidence, and authority. Unresolved identity becomes an explicit interface and validation branch instead of a row silently dropped or merged.