UMAD1 is a poorly characterized 137 amino acid human protein containing a predicted C-terminal UMA domain. Its name and domain architecture place it in the UBAP1/MVB12-associated UMA-domain protein family, but current local evidence does not establish a specific ESCRT-I complex, endosomal sorting, autophagy, membrane fission, or viral budding function for UMAD1. UniProt lists no FUNCTION comment or GO cross-references for UMAD1, and GOA currently contains only broad IntAct protein-binding evidence from a large-scale binary interactome map.
| GO Term | Evidence | Action | Reason |
|---|---|---|---|
| GO:0005515 protein binding | IPI PMID:32296183 A reference map of the human binary protein interactome. | MARK AS OVER ANNOTATED | Summary: This annotation comes from IntAct records based on the HuRI human binary interactome map, with UMAD1 interactions to TH isoform 3 and GABARAPL1 present in the local UniProt record. The interaction-screen evidence supports that UMAD1 can score in binary protein-interaction assays, but the GO term "protein binding" is too generic to represent a meaningful molecular function, and the partners do not establish a coherent UMAD1 core role. Reason: Generic protein binding is discouraged because it does not describe the actual activity or pathway role of the gene product. Here, the evidence is a large-scale interactome screen rather than a targeted functional study, and no more specific UMAD1 molecular function can be assigned from the local evidence. The Falcon deep research report proposes a specific ESCRT-I-adaptor molecular function for UMAD1 (selective binding to TSG101, VPS28, and VPS37C/VPS37B via a VPF motif), but that proposal derives from a single uncached primary study (Glover et al. 2023) that could not be verified here, and the report itself concedes that several UMAD1-specific roles "remains an important area for future investigation." This does not provide a verifiable basis to replace the generic protein-binding term, so the over-annotation call is retained. Supporting Evidence: UniProt:C9J7I0 CC C9J7I0; Q9H0R8: GABARAPL1; NbExp=3; IntAct=EBI-10989060, EBI-746969; UniProt:C9J7I0 CC C9J7I0; P07101-3: TH; NbExp=3; IntAct=EBI-10989060, EBI-12001016; PMID:32296183 To map the reference interactome, we performed nine screens of Space III, followed by pairwise verification by quadruplicate retesting and sequence confirmation. file:human/UMAD1/UMAD1-notes.md The existing `GO:0005515 protein binding` annotation is supported as a broad interaction-screen observation, but it is uninformative as a molecular function and should be marked as over-annotated. file:human/UMAD1/UMAD1-deep-research-falcon.md though direct experimental demonstration of UMAD1-specific roles in endosomal cargo sorting, autophagosome closure, or membrane repair remains an important area for future investigation. |
Loading supporting contentβ¦
Download this section (compressed HTML)Q: Does endogenous UMAD1 assemble with TSG101, VPS28, and any VPS37 paralog into a stable ESCRT-I complex in human cells?
Q: If UMAD1 forms an ESCRT-I variant, what cargoes, membranes, or tissues require the UMAD1-containing complex rather than MVB12A, MVB12B, or UBAP1 variants?
Q: Are the HuRI interactions with GABARAPL1 or TH isoform 3 reproducible at endogenous expression levels and relevant to a cellular process?
Experiment: Perform endogenous tagging or validated-antibody co-immunoprecipitation of UMAD1 followed by targeted immunoblotting or mass spectrometry for TSG101, VPS28, VPS37 paralogs, MVB12A, MVB12B, and UBAP1.
Hypothesis: UMAD1 may assemble into a specific ESCRT-I variant, but this must be shown directly before ESCRT-I complex annotations are justified.
Experiment: Use CRISPR knockout or acute depletion of UMAD1 with assays for ubiquitinated cargo sorting, intralumenal vesicle formation, and endosome morphology.
Hypothesis: If UMAD1 is a functional ESCRT-I fourth subunit, loss of UMAD1 should cause a measurable defect in at least one ESCRT-dependent endosomal sorting workflow.
Experiment: Validate the HuRI GABARAPL1 and TH isoform 3 interactions with reciprocal co-immunoprecipitation or purified-protein binding assays.
Hypothesis: The binary-interactome partners may be reproducible physical interactors, but they do not yet define UMAD1 molecular function.
What is not known β curated, literature-grounded statements of the open unknowns (the inverse of core functions).
Gap: It is unresolved whether endogenous UMAD1 assembles into a stable human ESCRT-I complex, and if so which TSG101/VPS28/VPS37-containing complex it joins and what molecular role its UMA domain performs.
OPEN BIOLOGYCURATION MF_DARK
What is known: UMAD1 has a predicted UMA domain and is listed by Flower et al. 2020 among possible UMA-domain fourth subunits of human ESCRT-I. Local evidence does not verify a UMAD1-containing ESCRT-I complex, and the only GOA evidence is broad HuRI protein binding to GABARAPL1 and TH isoform 3.
Significance: ESCRT-I complex membership would be the key molecular anchor for all more specific UMAD1 process annotations. Without direct assembly evidence, adding ESCRT-I, membrane-fission, ubiquitin-binding, or adaptor-function terms would overstate the local evidence.
What would resolve it: Endogenous UMAD1 tagging or validated-antibody immunoprecipitation with TSG101, VPS28, VPS37 paralogs, MVB12A/B, UBAP1, and ALIX, plus purified UMA-domain binding assays and motif mutants, would establish whether UMAD1 is an ESCRT-I subunit and define its molecular partners.
Provenance (the field's own admissions):
Gap: The biological process in which UMAD1 acts is unresolved. Cytokinetic abscission is proposed by an uncached 2023 primary study summarized in Falcon deep research, while endosomal sorting, autophagosome closure, membrane repair, and viral budding remain family-level ESCRT inferences rather than locally verified UMAD1 functions.
OPEN BIOLOGYCURATION BP_DARK
What is known: The Falcon report identifies a potentially decisive Glover et al. 2023 cytokinesis paper, but that paper is not in the local cache and was not read for this review. The locally cached Flower et al. paper supports UMA-domain ESCRT-I architectural context but does not establish a UMAD1-specific process.
Significance: UMAD1 currently cannot be assigned a defensible biological-process term beyond treating protein-binding evidence as over-annotated. Resolving this gap would determine whether UMAD1 belongs in cytokinesis, endosomal MVB sorting, autophagy, membrane repair, or no currently supported ESCRT-dependent process.
What would resolve it: Cache and review the Glover et al. 2023 article, verify its UMAD1-specific supporting text, then test UMAD1 perturbation in cytokinetic abscission, endosomal cargo sorting, autophagosome closure, and membrane repair assays with rescue by wild-type and ESCRT-binding-defective UMAD1.
Provenance (the field's own admissions):
Gap: The compartment where UMAD1 acts is unresolved. Midbody localization is asserted in the unverified cytokinesis model, while endosomal localization is inferred from ESCRT-I family context; neither compartment is established from locally reviewed endogenous UMAD1 evidence.
OPEN BIOLOGYCURATION CC_DARK
What is known: UMAD1's domain architecture places it among UMA-domain ESCRT-I-associated proteins, and the Falcon report describes context-dependent midbody and expected endosomal localization. The local review does not accept those locations as established cellular-component annotations.
Significance: Distinguishing midbody, endosomal, autophagosome-associated, or other pools is essential for deciding whether UMAD1 should receive ESCRT-I complex, midbody, endosome, or autophagy-related location annotations.
What would resolve it: Use endogenous tagging or validated antibodies for UMAD1 localization through the cell cycle and during ESCRT-dependent endosomal/autophagy perturbations, paired with CEP55, TSG101, VPS37, ALIX, endosome, and autophagosome markers.
Provenance (the field's own admissions):
Loading supporting contentβ¦
Download this section (compressed HTML)Loading supporting contentβ¦
Download this section (compressed HTML)Loading supporting contentβ¦
Download this section (compressed HTML)Loading supporting contentβ¦
Download this section (compressed HTML)