fpf.tools
Library / Semantic Integration Engineering Principles Framework
Jump to passage
In this reading
Source · lines 71–86

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 10:05:06 UTC

SIE-PROVIDERS - Compare live availability under semantic and access limits

  • Situation: Two provider APIs both expose an availability number, but their quantities and copying permissions differ from what a purchasing comparison assumes.
  • Question: Which qualified answer can the interface supply within the receiving and access conditions?
  • First useful result or blocker: Separately attributed quantities with the conditions needed for comparison, or a semantic or access limit that defeats the proposed answer.
  • Start with: SIE.2 and SIE.6 for unsettled meanings and comparison; SIE.8 when those premises are supplied and realization is the remaining question.
  • Stop or return: Exclude prohibited copying. Return an infeasible complete answer for a permitted narrower result or an access-owner decision. Reopen the affected meaning and interface when a provider changes the quantity it reports.

In the constructed provider case of APP-SIE-04 and SIE.6, Provider A reports 12 on hand and Provider B reports 9 available to promise. SIE.2 recovers the reservation and horizon rules behind the quantities. SIE.3 can reuse a model that keeps both measures, providers, units, times, and horizons distinct. SIE.4 supplies the qualified product-family relation. SIE.6 retains separate provider claims: the numbers do not support a common “21 available” total. For the question “Who can supply 8 now?”, A’s reservation check and B’s promise horizon must also support the receiving use.

Both providers prohibit replication. That prohibition is sufficient for SIE.8 to reject a copied availability store. If the question asks which remaining arrangement to use, compare query-time retrieval and any permitted hybrid with their latency, provenance, failure behaviour, and common resource demands. Develop only serious remaining alternatives. Obtain further evidence when its possible contribution to the choice justifies the burden and displaced work.

The shared-request example assumes four calls for A, four for B, and three for the required common trace, all under one ten-call allowance. The complete answer needs eleven calls before retries. With permission for an incomplete answer, A plus the trace needs seven: SIE.9 can expose “12 on hand at T” and “B not retrieved”, retaining the source and rule trace. B has not reported zero. SIE.10 still checks the other conditions needed for that narrower use; if both providers are mandatory, the result is a stop until the allowance or call demand is changed on supported grounds.

Suppose B keeps the same JSON field but changes its promise horizon. SIE.11 compares the meanings and finds the uses that consume them. An “available now” view returns to claim composition, mapping, interface, and receiving-use validation; a future-planning view may accept the new horizon after checking its own conditions. Product descriptions whose meanings are independent of that quantity can keep their earlier qualification. An inaccessible consumer interpretation remains unresolved. Purchasing decides how to act on the qualified or incomplete answer.