F.9:16 - Revision law

1. Endpoint change. A changed by-value scheme, local expression, or local-sense claim identifies another F.17 cell and requires another Bridge test.
2. Profile change. A changed kind, symmetry or orientation, endpoint reading, relation-specific correspondence or difference condition, applicability or as-of basis, Boolean truth condition, or stop dependency identifies another profile and occurrence candidate.
3. Use-content change. A changed proposed use u, direction, use-specific rule, or permitted-loss tolerance identifies another C.2.1 claim while the fixed Bridge remains unchanged.
4. Polarity change. Affirmative versus negative is changed claim content; it is not a changed reliance disposition.
5. Evidence or reliance change. A changed evidence item, path, currentness window, independently established direct relation cited by the A.10 path, local RelianceDisposition, or B.3 AssuranceResult reopens reliance without reidentifying the fixed Bridge or fixed C.2.1 claim.
6. Obtaining change. New endpoint facts may establish, refute, or leave unresolved the predicate for a fixed occurrence candidate without silently changing its identity.
7. Description, Card, registry, or publication change. Apply C.2.1 to description/Card identity and E.24.PUB to publication occurrence, form, and carrier; none creates, removes, reidentifies, or recurs the Bridge.
8. Receiving occurrence change. Reidentify or revise the Work, assertion, publication, relation, application, or other receiving object under its subject pattern.