SIE.2:4 - Solution
Recover source semantics at the smallest grain that can change the receiving answer. Preserve term, concept, type, relation, schema, model, claim, data item, carrier, identifier, and world-side referent as different questions. Qualify each relied-on premise by source identity, edition/effectivity, authority scope, provenance, access, currentness, and known gaps.
SIE.2:4.1 - Pattern-Use Unfolding
- Take the source cut from the use contract. Add another source only when it can change an answer claim, test, loss, or stop condition.
- 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.
- Recover the local scheme and scope. State the domain, population, lifecycle state, configuration, jurisdiction, or Work context in which the source definitions apply.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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. - 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.
SIE.2:4.2 - Record the Result
| Inventory position | Required content |
|---|---|
| source identity | owning/publishing System, asset or endpoint, profile/module, carrier, location |
| edition and applicability | version/edition, publication, effectivity/configuration/interval, local extension status |
| local semantic endpoints | designation, definition or operative rule, type/relation role, scope, examples/counterexamples, units/codes |
| identifiers | scheme, issuer/owner, syntax, resolution behavior, restrictions, grain, interval, identified-entity claim |
| claims and data | source claim, represented data item, scope/time, uncertainty/status, derivation and provenance |
| authority and access | meaning, identifier, value, extension, access, and receiving-use authority scopes |
| qualification | adequate, conditional, unresolved, obsolete, inaccessible, missing, or model-gap return with reason |
| dependency and reopen | consuming package rows, known gaps, next result, and source/edition/meaning changes that reopen |
SIE.2:4.3 - What Changes in Practice
The team stops mapping from field names. A later correspondence or transformation can point to exact source-local endpoints and editions, and a failure can return to the owner of the missing meaning, authority, access, or model. An inventory row can be useful even when its disposition is unresolved or inaccessible.