Library / Semantic Integration Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:40:10 UTC

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. Bind source endpoints. Reference each SIE.2 identifier scheme, issuer/owner, syntax, resolution behavior, restrictions, identified-entity claim, edition, and source provenance.
  4. Separate candidate relation kinds. Consider same individual at the stated grain, different individuals, part/whole, earlier/later version or specialization, variant, alternate description, family membership, or unresolved. Do not use one boolean until the use truly 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. Name who may decide scheme-local identity, master identity, authoritative values, or the domain relation. SIE may record and use a bounded disposition; it does not acquire 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. Propagate the premise explicitly. 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.