SIE.4:4.1 - Pattern-Use Unfolding

Take the question from the contract. State the receiving answer and why this endpoint relation can change it.
Bind exact endpoints. Reference the SIE.2 source rows, schemes, definitions, editions, profiles, effectivity, units, codes, and local extensions. Do not map labels without their senses.
Generate candidates without promotion. Lexical, structural, instance, expert, historical, or matcher evidence may nominate a row. Record the candidate source and score where useful, but do not treat nomination as acceptance.
State the direct relation or difference. Use the narrowest warranted relation vocabulary. State direction and whether the inverse, symmetry, or transitivity is actually supported. If no positive relation is established, choose rejected, unresolved, or incompatible with reason.
Test examples and counterexamples. Include instances or cases that should satisfy the relation and cases that distinguish endpoints, including version, unit, code, granularity, lifecycle, and authority differences.
Qualify the receiving use. State which substitution, comparison, join, navigation, or transformation the row permits, what semantic loss it introduces, and which uses remain forbidden.
Preserve evidence and authority. Record justification, evidence source, reviewer or domain authority where required, uncertainty or confidence, and the owner of any unresolved domain judgment.
Assign a row disposition. Use accepted-for-use, accepted-with-loss, rejected, unresolved, or incompatible. A row can state a true broader/narrower relation yet be rejected for this use.
State dependencies and tests. Name whether SIE.5, SIE.6, or SIE.7 consumes the row, plus a test or observation that reopens it.