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

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-COMMONS - Govern shared semantic modules

  • Situation: Several organizations use a shared classification, and a proposed improvement would change which objects belong to one of its classes.
  • Question: How can the shared model evolve while each consumer can still identify the meaning its work needs?
  • First useful result or blocker: The proposed distinction and the users whose questions depend on it, or an unresolved definition or decision right that prevents the change.
  • Start with: SIE.12, with SIE.3 for changed model content and SIE.11 for actual consumer reliance.
  • Stop or return: Keep incompatible criteria in scoped modules when their users need them. A pair needing only one interface can complete that agreement; shared-module governance is useful when independently maintained modules and users create that further need.

In APP-SIE-05, two manufacturers and a service partner share equipment classes. A proposal replaces “equipment with a replaceable drive” with “equipment serviced through a replaceable drive module”. Equipment X has only a separately replaceable drive; Y also supports drive-module replacement. These cases expose the changed classification: X belongs to the earlier class but not the proposed one, while Y belongs to both.

SIE.3 uses those cases to make the meanings distinguishable. Under the constructed SIE.12 agreement, the authorized maintainers keep equip:DriveReplaceable for the earlier meaning and introduce equip:DriveModuleServiceable for the new one. Both definitions and their editions remain recoverable. Source owners continue to supply the product descriptions on which membership depends.

SIE.11 follows each consumer’s question. The service partner adopts the new class for module-replacement planning, so SIE.4 revisits its correspondences and the query uses the revised relation. SIE.10 checks the integration premises, including the result that admits Y and excludes X. Manufacturer A still needs its spare-drive query under the earlier meaning and can retain matching evidence. The release supplies the access, dependencies, migration information, and notice those uses need. These two completed outcomes leave other consumers’ migration to be established where it matters.