Consistency: Internally consistent but PN placement is contradicted by the gene's own evidence. Deep research, notes, and review YAML all frame ASCC1 as a nuclear ASC-1/ASCC subunit (transcription coactivation + ALKBH3-linked alkylation-damage repair); none place ASCC1 in cytosolic ribosome rescue. The notes explicitly flag the RQC projection as a workbook propagation artifact and cite PMID:38366554 that ASCC1 is dispensable for the cytoplasmic ribosome-splitting step. GOA confirms no RQC term on ASCC1.
PN story / NEW pressure: The PN asserts a ribosomal-rescue/RQC role not in GO and not supported by ASCC1-specific data. GO:0072344 and GO:0006515 are real terms, but projecting them to ASCC1 over-reaches: the RQC role belongs to the ASCC complex via ASCC3/ASCC2/TRIP4, with ASCC1 dispensable. Conclude: over-reaches (do not project to ASCC1). No defensible NEW GO term for ASCC1 from the PN node; the review already proposes the correct NEWs (GO:0060090 molecular adaptor; GO:0003713 transcription coactivator, contributes_to).
Mapping strategy: This gene is a counter-example for the RQC node, not a driver. The type/group mappings (GO:0072344/GO:0006515) are biologically sound for the node but must not be auto-projected to ASCC1. Status/scope of the node need not change for other members; ASCC1 should be exempted from propagation.
Evidence alignment: PN row carries no reference titles; the review's RQC-adjacent papers (PMID:37092320 translation initiation; PMID:38366554 disassembly) are complex/ASCC3-centric and were deliberately not used to add RQC terms to ASCC1. No PMID conflict — divergence is conceptual (node-level vs gene-level).
Verdict: Consistent review; PN RQC projection over-reaches for ASCC1 and is correctly rejected in-review. No edits needed beyond exempting ASCC1 from RQC propagation at the mapping layer.