Consistency: Mostly consistent, with one structural gap. Review, PN annotation, and node mapping agree FBXL8 is an SCF substrate receptor. Non-canonical F-box: UniProt notes FBXL8 does NOT contain canonical leucine-rich repeats despite the "LRR" name — yet the PN places it under the ...|F-box|LRR subtype. The review captures this caveat in its description; the PN subtype label is therefore mildly inaccurate for this member (subtype is no_mapping, so no propagation harm). Falcon substrates (p53, phospho-Thr283 CCND3, Snail1, unphospho c-MYC) are UNVERIFIED leads, correctly not added as GO terms.
PN story / NEW pressure: PN asserts the generic adaptor MF. FBXL8 GOA has NO MF beyond protein binding (SKP1) and no SCF-process IDA. The review's core_functions assigns GO:1990756, but — unlike FBXL7/FBXL12 — it is NOT added as an action: NEW entry in existing_annotations. This is the one batch-pattern deviation: the adaptor MF that PN projects as new_to_goa is endorsed in core_functions but never materialized as a reviewable annotation. Conclusion: ADD GO:1990756 as NEW to existing_annotations for parity.
Mapping strategy: Gene does not change the group GO:1990756 (defensible on F-box + SKP1 grounds). FLAGS: (1) non-canonical F-box (no true LRRs) — PN |LRR subtype label is a misnomer here; (2) no PMID-validated substrate in existing_annotations — adaptor MF is inferred-only. Scope/status otherwise correct.
Evidence alignment: PN cites only "15340381/rev"; review uses SKP1 interactome PMIDs + PMID:33234069 + falcon leads. No PMID overlap with placeholder.
Verdict: MAPPING CONSISTENT but YAML gap. Recommended edits: [YAML] add GO:1990756 as action: NEW in FBXL8 existing_annotations (mirror FBXL7/FBXL12) so the PN-projected adaptor MF is materialized; [MAP] consider noting the non-canonical (no-LRR) status on the F-box|LRR subtype for FBXL8.