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.
- Resolve an identifier for this use. Identify the entry, the kind and grain of entity it can designate, and the restrictions on its use. For an issued identifier, recover the applicable assignment, its authority and its interval. For a designation resolved by a rule, establish that rule and the context in which it picks out an entity. If the sources form or resolve entries differently for this use, compare their languages of designations. When the rules agree, use that agreement and examine the particular bindings. State what remains unknown.
- 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. Identify who sets the source conventions, who can issue or reassign an identifier, who decides authoritative values and who may approve extensions, grant access or 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.
- Request a model that supplies the missing distinction. 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 | entry and applicable syntax, resolution rule and context or assignment and its authority, use restrictions, entity grain, relevant interval and supported or unresolved referent |
| 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
Mappings are grounded in the recovered source meanings. 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.