| What use and loss boundary govern the integration? | SIE.1 | SemanticIntegrationUseContract@Use |
| What does each source mean and own? | SIE.2 | SourceSemanticInventory@Use |
| Are the available models adequate, or what content must change? | SIE.3 when adequacy is unsettled | UseFitSemanticModel@Use or exact blocker |
| Which endpoints correspond or remain incompatible? | SIE.4 | QualifiedCorrespondenceSet@Use |
| Which identifiers concern the same entity at this grain and interval? | SIE.5 | CrossSourceIdentityDisposition@Use |
| How can governed claims be composed without hiding conflict? | SIE.6 | SourceQualifiedClaimFusion@Use |
| Which executable rules implement the accepted semantics? | SIE.7 | ExecutableSemanticMappingSpecification@Use |
| Should the arrangement be virtual, materialized, or hybrid? | SIE.8 | SemanticRealizationDecision@Use |
| What interface carries the meaning into receiving Work? | SIE.9 | ReceivingSemanticInterface@Use |
| Is the result usable for the named receiver? | SIE.10 | SemanticIntegrationValidationAccount@Use |
| What follows from a changed semantic premise? | SIE.11 | qualified direct result, scoped gap, or a common affected-use account when needed |
| How should shared semantic modules be maintained? | SIE.12 for actual commons users | ModularSemanticCommonsAccount@Community or exact blocker |