PN placement:Ubiquitin Proteasome System|Proteasome and associated proteins|adaptors|Akirin ; PN-node mapping: Akirin type no_mapping; group (adaptors) mapped→GO:0070628 (proteasome binding, propagate); class context_only→GO:0000502. Projection: GO:0070628 new_to_goa.
Consistency: Contradiction between PN projection and review. PN projects proteasome binding (GO:0070628) onto AKIRIN1 via the shared "Akirin" adaptor bucket. The review and deep research (falcon) argue this is paralog over-transfer: the proteasome-import adaptor activity is established for AKIRIN2 (PMID:34711951), not AKIRIN1. UniProt and the review explicitly contrast AKIRIN1 (nuclear transcriptional cofactor, promyogenic) with AKIRIN2's proteasome role. The review does NOT adopt GO:0070628 and flags the projection as unsupported.
PN story / NEW pressure: PN asserts proteasome binding not in GOA. GO:0070628 is a real term and genuinely absent from AKIRIN1 GOA, but there is no AKIRIN1-specific primary evidence for it; the only direct binding datum is an IntAct GOPC interaction (review MODIFY→GO:0044877 protein-containing complex binding). Verdict: over-reaches — this is family/paralog propagation (PLI-like: the wrong Akirin paralog), not a defensible ADD for AKIRIN1.
Mapping strategy: The Akirin type node groups AKIRIN1+AKIRIN2; the parent "adaptors" group→GO:0070628 propagation is correct for AKIRIN2 but wrong for AKIRIN1. The mapping should split the Akirin type so proteasome binding propagates only to AKIRIN2, or mark AKIRIN1 as a no_mapping/excluded member.
Evidence alignment: Dossier lists no PN reference titles for AKIRIN1. Review cites PMID:18066067 (conserved nuclear cofactor), PMID:23516508 (promyogenic), and pointedly PMID:34711951 as a negative contrast (AKIRIN2-specific). Divergence is in interpretation, not citation.
Recommended edits: [MAP] Split the adaptors|Akirin type so GO:0070628 proteasome binding propagates to AKIRIN2 only; mark AKIRIN1 as no_mapping (nuclear transcription cofactor, no proteasome-binding evidence).