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 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 14:45:10 UTC

SIE.2:4.1 - Pattern-Use Unfolding

  1. Take the source cut from the use contract. Add another source only when it can change an answer claim, test, loss, or stop condition.
  2. Identify the source asset and carrier. Record publisher or owning System, title or endpoint, profile/module, version or edition, publication and effectivity, retrieval location, and carrier kind. Keep the asset distinct from the concepts and claims it carries.
  3. Recover the local scheme and scope. State the domain, population, lifecycle state, configuration, jurisdiction, or Work context in which the source definitions apply.
  4. Recover exact meanings. For every load-bearing endpoint, record the designation, definition or operative rule, type/relation role, examples and counterexamples, units or codes, and unresolved ambiguity. Use source-local language before normalizing it.
  5. Separate identifiers and identified entities. Record the scheme, issuer or owner, syntax, resolution behavior where relevant, use restrictions, grain, interval, and what the identifier does not establish.
  6. Separate claims, data, and provenance. Record which claim a data item represents, its scope and time, how it was derived, who or what supplied it, and which uncertainty or status accompanies it. Provenance does not make the claim true.
  7. Recover authority and access. Name who may define the scheme, issue identifiers, decide authoritative values, approve local extensions, grant access, and authorize receiving use. Mark unsupported assumptions.
  8. Assess currentness and use adequacy. Compare the source premise with the contract. State whether it is adequate, adequate only under conditions, unresolved, obsolete for this use, inaccessible, or missing.
  9. Return an inadequate model honestly. If the required distinction cannot be expressed in the available source or supplied semantic model, request UseFitSemanticModel@Use; do not hide the gap in a mapping rule.
  10. Record dependencies and next results. Identify the exact definitions, editions, authority facts, and gaps consumed by SIE.4–SIE.10, plus observations that reopen this inventory.