Substrate localization to autophagosome obsoletion

GO:0061753 → the cargo adaptor MF plus one selective-autophagy process per paper

AI Gene Review · projects/SUBSTRATE_LOCALIZATION_TO_AUTOPHAGOSOME_OBSOLETION · 2026

Bottom line

  • GO plans to obsolete GO:0061753 because it restates a molecular function (GO:0160247 cargo adaptor activity); there is no single replacement.
  • We traced 5 direct experimental rows, 5 MF extension rows and 10 ISS/ISO rows, mapped each to a cargo-specific process, and found 2 errors in the upstream table.
  • Scoped, not landed: GO:0061753 is still active; RETREG2 and STBD1 reviews here ACCEPT it and use it in core_functions.

A bridging activity, not a process

One term, five destinations

What we found upstream

  • Gabarapl1 (mouse Q8R3R8) also has a direct GO:0061753 row (ISO, MGI, PMID:21893048) that the issue's list of direct rows omits.
  • The Gabarapl1 MF row is ISO assigned by MGI, not an experimental GO Central row.
  • IRGQ routes misfolded MHC-I to lysosomes via GABARAPL2/LC3B; no selective-autophagy term fits, so it is a new-term candidate.
  • The MF re-parenting under GO:0160247 (go-ontology#31866) is already closed.

Repo impact

Review GO:0061753 rows In core_functions Specific BP already present
human/RETREG2 1 IEA, ACCEPT yes GO:0061709 reticulophagy
human/STBD1 1 IEA, ACCEPT yes GO:0061723 glycophagy
  • core_functions ids are strictly validated, so both reviews will fail validation once the validator's GO release includes the obsoletion.
  • The page's impact section predates the STBD1 review and lists RETREG2 only.
  • Not yet reviewed here: TOM1, IRGQ, SMURF1, GABARAPL1.

Next steps

  1. Drop GO:0061753 from core_functions in RETREG2 and STBD1; revisit their IEA rows; just validate human <gene>.
  2. Review IRGQ and draft a proposed_new_terms entry for MHC-I quality-control autophagy.
  3. Then SMURF1, TOM1, GABARAPL1; report the two table corrections to go-annotation#6497.

Siblings: VESICLE_TARGETING_OBSOLETION, SYNAPTIC_VESICLE_DOCKING_OBSOLETION, ER_EXIT_SITE_LOCALIZATION_OBSOLETION (same MF_in_BP rationale)
Upstream: go-annotation#6497 · go-ontology#32304 (open)