ARBA00028131 (GO:0004175)

id: ARBA00028131
description: 'An extremely complex mega-rule with 41 condition sets assigning GO:0004175 (endopeptidase activity) to proteins across virtually all major endopeptidase families including aspartic proteases (pepsin family), cysteine proteases (papain/cathepsin families), serine proteases (subtilisin family), and metalloproteases (aminopeptidase family). While biologically sound, the rule represents a maintenance nightmare due to its extreme complexity and loses functional specificity by applying a single broad term to mechanistically distinct protease families.'
status: COMPLETE
rule_type: ARBA
rule:
  rule_id: ARBA00028131
  condition_sets: []  # 41 condition sets covering diverse protease families
  go_annotations:
    - go_id: GO:0004175
  entries: []
  reviewed_protein_count: 0
  unreviewed_protein_count: 0  # Unknown from JSON
  created_date: 'Unknown'
  modified_date: 'Unknown'
review_summary: 'ARBA00028131 is a comprehensive but overly complex rule that technically assigns the correct molecular function term GO:0004175 (endopeptidase activity) to a vast array of endopeptidase families. The rule covers aspartic acid proteases (pepsin, cathepsin D), cysteine proteases (papain, cathepsins B/H/L), serine proteases (subtilisin family), and metalloproteases (aminopeptidases) across all domains of life. While the biological classification is sound and the GO term assignment is appropriate, the rule suffers from extreme complexity (41 condition sets), loss of functional specificity (single broad term for diverse mechanisms), and significant maintenance burden. The rule would benefit from decomposition into family-specific rules with more granular GO term assignments reflecting the distinct catalytic mechanisms and biological contexts of different protease families.'
action: MODIFY
action_rationale: 'While the GO term assignment GO:0004175 (endopeptidase activity) is biologically correct for all covered proteins, this mega-rule represents poor curation practice due to its extreme complexity and loss of functional granularity. The 41 condition sets covering mechanistically distinct protease families (aspartic, cysteine, serine, metalloprotease mechanisms) create an unmanageable maintenance burden and obscure important functional differences. Each protease family has distinct catalytic mechanisms, substrate specificities, and biological roles that merit more specific GO term assignments. The rule should be decomposed into mechanistically coherent, family-specific rules with appropriate granular annotations.'
suggested_modifications:
- 'Decompose into family-specific rules: separate rules for aspartic proteases (pepsin family), cysteine proteases (cathepsin families), serine proteases (subtilisin family), and metalloproteases (aminopeptidase family)'
- 'Add mechanism-specific GO terms: GO:0004194 (pepsin A activity), GO:0008234 (cysteine-type peptidase activity), GO:0004252 (serine-type endopeptidase activity), GO:0008237 (metallopeptidase activity)'
- 'Include biological process annotations: GO:0006508 (proteolysis) as general term, plus context-specific BP terms for digestive, lysosomal, or regulatory proteases'
- 'Standardize condition set structure across decomposed rules for consistency'
- 'Reduce condition sets per family-specific rule to <20 for maintainability'
parsimony:
  assessment: OVERLY_COMPLEX
  notes: 'With 41 condition sets covering fundamentally different protease mechanisms (aspartic acid, cysteine, serine, metalloprotease), this rule violates the principle that annotation rules should target mechanistically coherent protein sets. The rule attempts to unify proteases that differ in catalytic mechanism, cofactor requirements, pH optima, substrate specificity, and biological roles. This creates unnecessary complexity and obscures important functional distinctions.'
  supported_by:
  - reference_id: file:rules/arba/ARBA00028131/ARBA00028131-deep-research-manual.md
    supporting_text: 'The rule encompasses virtually all major endopeptidase families with fundamentally different catalytic mechanisms: Aspartic acid proteases with Asp-Thr-Gly catalytic triads, Cysteine proteases with Cys-His catalytic dyads, Serine proteases with Ser-His-Asp catalytic triads, Metalloproteases with metal-coordinated active sites. This mechanistic diversity suggests the rule is overly ambitious in scope.'
literature_support:
  assessment: STRONG
  notes: 'Excellent literature support exists for the fundamental classification of endopeptidases and their shared molecular function of cleaving peptide bonds internally within polypeptide chains. The biological basis for the GO term assignment GO:0004175 is unquestionable. However, literature also strongly supports mechanistic classification of proteases into distinct families based on catalytic mechanism, which argues for more granular annotation approaches.'
  supported_by:
  - reference_id: file:rules/arba/ARBA00028131/ARBA00028131-deep-research-manual.md
    supporting_text: 'The fundamental classification of endopeptidases based on catalytic mechanism is well-established and supported by decades of biochemical research. All major protease families covered (aspartic, cysteine, serine, metalloprotease) are extensively characterized with strong experimental evidence for their endopeptidase activity.'
  - reference_id: file:rules/arba/ARBA00028131/ARBA00028131-citations.md
    supporting_text: 'Comprehensive literature support including core protease reviews, family-specific studies, and mechanistic analyses. Key references demonstrate both the shared endopeptidase function and the distinct mechanistic specializations of different protease families.'
condition_overlap:
  assessment: MINOR
  notes: 'Despite the rule complexity, condition overlap appears minimal due to the use of distinct InterPro domains and PANTHER families specific to different protease mechanisms. However, the complexity makes comprehensive overlap analysis difficult. The taxonomic restrictions in various condition sets may create unintended gaps or overlaps that are hard to detect.'
  supported_by:
  - reference_id: file:rules/arba/ARBA00028131/ARBA00028131-deep-research-manual.md
    supporting_text: 'The rule uses distinct InterPro domains for different protease families (IPR001461 for aspartic proteases, IPR001096 for cysteine proteases, IPR003675 for serine proteases, IPR001915 for metalloproteases), which should minimize overlap between mechanistically distinct families.'
go_specificity:
  assessment: TOO_BROAD
  notes: 'The single GO term assignment GO:0004175 (endopeptidase activity) is technically correct but loses important functional specificity. Different protease families have distinct substrate specificities, pH optima, and biological roles that could be captured with more specific molecular function terms. The lack of biological process annotations is also a missed opportunity.'
  supported_by:
  - reference_id: file:rules/arba/ARBA00028131/ARBA00028131-deep-research-manual.md
    supporting_text: 'While GO:0004175 (endopeptidase activity) correctly captures the shared molecular function, more specific terms would better reflect functional diversity: GO:0004194 (pepsin A activity) for aspartic proteases, GO:0008234 (cysteine-type peptidase activity) for cysteine proteases, GO:0004252 (serine-type endopeptidase activity) for serine proteases, GO:0008237 (metallopeptidase activity) for metalloproteases.'
taxonomic_scope:
  assessment: APPROPRIATE
  notes: 'The pan-taxonomic scope is appropriate given that endopeptidases are fundamental enzymes found across all domains of life. The taxonomic restrictions in specific condition sets (Chordata, Haplorrhini, Ecdysozoa) appear to reflect genuine lineage-specific domain architectures or family distributions rather than arbitrary restrictions.'
  supported_by:
  - reference_id: file:rules/arba/ARBA00028131/ARBA00028131-deep-research-manual.md
    supporting_text: 'Endopeptidases are fundamental enzymes found across all domains of life - Bacteria, Archaea, and Eukaryota. The taxonomic restrictions in specific condition sets likely reflect genuine evolutionary patterns in domain architecture or family-specific distributions rather than inappropriate constraints.'