E.17.ID.CR:4.4 - Branch-discipline summary

This section is the compact governing-rule summary for ComparativeReviewUnit inside the Core. Use the fuller solution, boundary table, worked slices, and relations section here only when specific clause wording, full field set, or full reopen conditions matter.

1. Preserve the shared review frame. Keep the reviewed source episteme or source publication set, source references, declared comparison criterion, and distinct alternative identities visible. If contrastiveQuestion is doing real review work, state it.
2. Keep the lift bounded and comparative. The review unit can add one bounded comparative or asymmetry-bearing lift. It stops when that lift starts carrying a stronger crossed claim.
3. Name the crossed claim instead of repeating exclusions. When the case stops being bounded comparison, name the claim that crossed the boundary and apply the pattern that governs it; use E.17.ID.CR:4.5 to identify the relevant boundary.
4. Keep neighboring-pattern authority explicit. Bridge-mediated comparison requires an exact bridgeOccurrenceRef and a tuple-matched boundedUseClaimRef whose EntityOfConcern is that Bridge. Positive use requires affirmative polarity and, when A.10 or B.3 is triggered, current reliance for that exact use. Degraded reliance narrows the use; a negative, abstaining, reopened, evidence-needed, blocked, or mismatched result stops it. A Card and F.9.1 stance note remain optional and separate. Authorization and evidence that comparative-review Work occurred remain with their own patterns and records.
5. Keep reader-fit bounded. targetUserModel, interactionMode, contrastiveQuestion, boundedComparativeUse, and overreadRisk can be stated when they change actual review use, but they do not create authority that the unit does not carry.