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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:55:15 UTC

SIE.11:4 - Solution

Follow the changed proposition through actual semantic dependencies to the results and receiving uses it can alter. Complete supported branches at their proper scope. Assemble a wider account only for a receiver that needs it.

SIE.11:4.1 - Pattern-Use Unfolding

  1. Compare the relied-on meaning. Identify what the receiving question depended on in the earlier source or premise and what the later content says. Include changed applicability, subject grain, interval, assumptions, or limits where relevant. An inaccessible later definition leaves that comparison unresolved.
  2. Finish a compatible repair when sufficient. If content, applicability, and access remain compatible for the use, make the needed reference repair and retain matching results. A version or URL change alone does not require every downstream Method to run again.
  3. Find affected uses when their scope is unsettled. Apply A.10.1 to discover actual reliance within the question’s scope, using source-side and receiver-side evidence or an index that adequately covers both. Distinguish a material dependency from a mention. Retain coverage gaps that limit the intended conclusion.
  4. Select the integration result that the change can alter. Use the domain returns below. Follow a further consumer only when the changed result can alter its action or claim. The physical proximity of files is not a dependency rule.
  5. Repair or revalidate that result. Apply its defining Method to the changed premise. Reuse earlier evidence whose actual conditions still match. Return a supported continuation, repair, permitted narrower use, or scoped gap. Source truth, master identity, product release, and application decisions go to the owners of those decisions.
  6. Return the completed branch. Give the receiver the result it needs, with the changed premise and remaining limits where those affect reliance. A completed direct result is sufficient for its own receiving question.
  7. Combine results when a receiver needs the wider answer. State the covered uses, their relevant results, unresolved uses or discovery gaps, and the continuation that those results support. A broader no-impact conclusion requires the corresponding coverage; completed local branches cannot supply unexamined ones.

When additional evidence is being considered, apply C.11.DUA to compare its attainable contribution to the receiving decision with its cost, delay, downside, and displaced work. A gap can remain a qualified gap when further inquiry cannot support a worthwhile next action; that limitation does not warrant a stronger claim.

SIE.11:4.2 - Domain Returns

Changed relianceIntegration result to revisit
A concept, relation, or model constraintSIE.3 model adequacy and any affected SIE.4 correspondence.
Identifier meaning, scheme, grain, or intervalSIE.5 identity disposition and the results that actually use it.
Source-claim scope or interpretationSIE.6 composition, conflict, or non-comparability result.
A transformation premiseSIE.7 mapping and its affected outputs.
Availability, permissions, freshness, or service conditionsSIE.8 realization choice or SIE.9 receiving interface, according to the changed condition.
Receiving meaning or acceptance conditionSIE.9 interface contract and the corresponding SIE.10 validation.

This table locates the defining result; the actual dependency determines which returns are needed and their useful order.

SIE.11:4.3 - Record the Result

For a direct repair, use the result already needed by its consumer. For a common account, retain the following content at the scope the receiver needs:

Account positionReceiving content
Change and relianceEarlier relied-on meaning, later meaning, and the affected question.
Covered usesActual dependencies and the basis for the stated discovery scope.
Direct resultsCompleted repairs, revalidation, permitted continuation, or narrowed uses under their defining Methods.
Unresolved reachUnexamined or inaccessible reliance, discovery gaps, and their effect on the conclusion.
Continued useWhat the receiver can now rely on and which changed conditions would reopen it.

The account summarizes its constituent results. It does not serve as a circular input that those results must await before they can be completed.

SIE.11:4.4 - What Changes in Practice

The maintainer can say which interface meaning changed, which mapping or identity result was revisited, and what can continue. A corrected local reference can finish immediately. A broader claim remains bounded by the uses actually discovered and assessed.