Consistency: Fully consistent. Deep research, notes, review YAML agree ASCC2 is the CUE-domain K63-polyUb reader serving BOTH (1) nuclear ASCC-ALKBH3 alkylation repair and (2) cytosolic hRQT/RQC. Both PN rows map onto these two arms cleanly. Review holds GO:0070530 (K63-linked polyUb-dependent binding) as the MF for both core_functions, plus full RQC term set.
PN story / NEW pressure: Row1 RQC role already captured by specific terms (GO:0072344, GO:0032790, GO:1990116, GO:0180022 ACCEPT; GO:0043130 ubiquitin binding MODIFY→GO:0070530). Notes correctly decline broad GO:0006515 as redundant. Row2 (UPS CUE / ubiquitin-reader) is honestly mapped no_mapping at leaf and context_only above (GO:0140036 ubiquitin-modified protein reader) — the actual reader function is captured more specifically by GO:0070530 in the review. Conclude: already captured. No NEW term needed.
Mapping strategy:ASCC2 supports both nodes but drives neither toward change. Broad GO:0006515 (RQC node) and GO:0140036 (UPS class) are both broader than the review's GO:0070530 — the TOMM20/HSPA8/RAB7A "too broad" precedent applies; do not project. Row2 leaf no_mapping is the right call.
Evidence alignment: PN rows carry no reference titles. Review CUE/K63 evidence (PMID:29144457, PMID:36302773, PMID:34971705 Lombardi, PMID:33139697 Jia ASCC2-ASCC3 interface) and RQC (PMID:32099016, PMID:32579943) align with both PN arms. No citation conflicts.
Verdict: Consistent and well-supported across both PN branches; specific GO:0070530 + RQC terms already capture the story. Broad projections correctly declined. No edits warranted.