F.8:7.1 - ReviewerRole Expression vs Review Report

The source label PatternReview_2026 is not a context object. Classify the actual claim before using it:

• ReviewWork-82 can be one dated U.Work occurrence under A.15.1;
• ReviewPlan-2026-v3 can be a separately constituted plan episteme or edition under its subject pattern;
• PatternReviewReferenceScheme-2026 can be an effective by-value U.ReferenceScheme for interpreting review terminology; and
• “used while deciding the label for the 2026 review method” can be claim content describing the decision-use setting without minting any context entity.

If the recovered ReviewerSystemRole kind needs a durable local designation, F.8 returns openDurableNamingSettlement: A.2 and C.3 keep governing the kind, F.5 governs its designation, and F.18 supplies the settlement. The recovered kind is the governed subject; F.4 enters only for a separately needed description, A.2.1 for an assignment, and A.15.1 for performed review Work.

The expression “review report has reviewer role” is a different case. ReviewReport-82 is an episteme. An evidence, source, or publication relation may later use it for an adequacy claim about a reviewed pattern; the report is not a U.System, is not classified by the review-system-role kind, and cannot enter its assignment relation. Its title establishes neither evidence use nor publication authority.