family_id: PANTHER:PTHR24251
family_name: OVOCHYMASE-RELATED
preferred_name: CUB-domain extracellular and membrane proteins
summary: CUB domains occur in extracellular recognition proteins, cubilin, procollagen-processing factors,
  metalloproteases and membrane receptors. A common extracellular interaction module is distinct from
  the activity of additional catalytic domains or a reproductive role.
functional_coherence: HETEROGENEOUS
coherence_reason: The sponge target is a short CUB-domain protein. The domain is compatible with an extracellular
  interaction, but single fertilization is not a family-wide process. Ovomucin/ovochymase-style names
  must not imply protease activity or fertilization for cubilin, procollagen enhancers and unrelated CUB
  architectures.
subfamilies:
- subfamily_id: PANTHER:PTHR24251:SF37
  label: CUB DOMAIN-CONTAINING PROTEIN
  description: Recorded placement of A0A2G9RZF1. The sponge target is a short CUB-domain protein. The
    domain is compatible with an extracellular interaction, but single fertilization is not a family-wide
    process. Ovomucin/ovochymase-style names must not imply protease activity or fertilization for cubilin,
    procollagen enhancers and unrelated CUB architectures.
  representative_members:
  - id: UniProtKB:A0A2G9RZF1
    gene_symbol: A0A2G9RZF1
    organism: Aquarana catesbeiana
    gene_review: genes/AQUCT/A0A2G9RZF1/A0A2G9RZF1-ai-review.yaml
term_assessments:
- assessed_term:
    id: GO:0007338
    label: single fertilization
  scope: UNRESOLVED
  scope_reason: CUB domains occur in reproductive recognition proteins but also in complement, matrix
    processing and other extracellular systems. The short sponge CUB-domain target does not establish
    a fertilization role, and the original CUB comparison explicitly describes functionally diverse proteins.
    The full set of reproductive branches is unresolved; sperm-associated examples cannot define the whole
    family.
  supported_by:
  - reference_id: PMID:8510165
    supporting_text: '31 copies of an extracellular

      domain, here called CUB'
  - reference_id: file:genes/AQUCT/A0A2G9RZF1/A0A2G9RZF1-uniprot.txt
    supporting_text: DR   InterPro; IPR000859; CUB_dom.
  - reference_id: file:genes/AQUCT/A0A2G9RZF1/A0A2G9RZF1-uniprot.txt
    supporting_text: FT   DOMAIN          31..147
  - reference_id: file:genes/AQUCT/A0A2G9RZF1/A0A2G9RZF1-uniprot.txt
    supporting_text: FT                   /note="CUB"
- assessed_term:
    id: GO:0005576
    label: extracellular region
  scope: UNRESOLVED
  scope_reason: The original CUB-domain comparison and the benchmark domain architecture support an extracellular
    interaction-module hypothesis. Secreted proteins and membrane-receptor ectodomains must still be distinguished
    from truncated or untargeted products. An extracellular CUB module supports location by comparison,
    but does not establish every full-length family architecture as a soluble extracellular protein.
  supported_by:
  - reference_id: PMID:8510165
    supporting_text: '31 copies of an extracellular

      domain, here called CUB'
  - reference_id: file:genes/AQUCT/A0A2G9RZF1/A0A2G9RZF1-uniprot.txt
    supporting_text: DR   InterPro; IPR000859; CUB_dom.
  - reference_id: file:genes/AQUCT/A0A2G9RZF1/A0A2G9RZF1-uniprot.txt
    supporting_text: FT   DOMAIN          31..147
  - reference_id: file:genes/AQUCT/A0A2G9RZF1/A0A2G9RZF1-uniprot.txt
    supporting_text: FT                   /note="CUB"
references:
- id: PMID:8510165
  title: The CUB domain. A widespread module in developmentally regulated proteins.
- id: file:genes/AQUCT/A0A2G9RZF1/A0A2G9RZF1-uniprot.txt
- id: file:interpro/panther/PTHR24251/PTHR24251-entries.csv
- id: file:interpro/panther/PTHR24251/PTHR24251-paint.tsv
review_status: COMPLETE
reviewed_by: codex
review_date: '2026-09-10'
notes: 'AQUCT/A0A2G9RZF1: requested accession A0A2G9RZF1; current record A0A2G9RZF1; sequence length 156;
  source cohort ARGO50. Family boundaries were assessed using the fetched member set and the cited domain,
  literature and analytical evidence. Gene-review verdicts and ARBA assertions are not independent validation.
  PANTHER subfamily labels and membership are recorded from the frozen UniProt records and panther.obo;
  they do not by themselves prove functional uniformity within a subfamily. PAINT rows were inspected
  as ancestral assertions, but node placement is not adjudicated without the relevant descendant tree/alignment.
  No residue requirement is encoded without a verified sequence-version anchor. A target-level refutation
  is not a family-wide NOT_APPLICABLE judgment. Exact protein-name-only predictions are treated as family-identification
  hypotheses rather than invented GO predictions.'