Oncofusion

start / graph / gene-hcfc2

Proteinweak confidence 2 of 5: Preliminary, small, indirect, or not yet peer reviewed.Q36-menin-interactome

HCFC2 — menin's other host cell factor, present in the founding paper by gel filtration and never mentioned again

also called HCFC2 · HCF-2 · host cell factor 2 · Q9Y5Z7

HCF-1 is a well-known part of the menin-KMT2A machine and has its own entry here. It has a less-studied sibling, HCF-2, which turned up in the very paper that founded this field and has essentially not been looked at since. The evidence for it is weaker than for HCF-1 and comes from a different kind of experiment.

The same thing, for a scientist

HCFC2 (UniProt Q9Y5Z7, 792 aa, primary gene name read back) is the paralogue of HCFC1, the host cell factor that this graph already carries as `gene-hcfc1`. Its only appearance in menin biology is in **PMID 15199122** — Yokoyama, Wang, Wysocka, Sanyal, Aufiero, Kitabayashi, Herr, Cleary, *Leukemia proto-oncoprotein MLL forms a SET1-like histone methyltransferase complex with menin to regulate Hox gene expression* (Mol Cell Biol 2004), the founding paper for this graph's entire WRAD and menin-complex position [E1]. **The evidence type matters and is easy to miss:** IntAct curates the MEN1-HCFC2 row from that paper with the method **`molecular sieving`** — gel filtration co-elution — not co-immunoprecipitation [E2]. The same paper's MEN1-KMT2A row is an anti-bait co-immunoprecipitation. **Co-elution in a size-exclusion fraction is the weakest interaction evidence in the paper**, and it is the only evidence HCFC2 has ever had. A title/abstract search over `HCFC2` and `HCF-2` against `KMT2A`, `MLL` or `menin` returns exactly **one record — 15199122 itself** [E3]. In twenty-two years nobody has returned to it. This entry exists so that HCFC2 is filed at the strength of its evidence rather than by association with its much better-supported paralogue.

Go deeper
Why HCF-1 and HCF-2 are not interchangeable

HCFC1 reaches the KMT2A complex through a defined route this graph already documents: the HCF-binding motif (HBM) in KMT2A, which is among the domains lost in the fusion (subtraction-kmt2a-hcf-binding-motif), and HCF-1's association with menin-containing SET1-family complexes. HCF-1 is also a proteolytically processed, chromatin-associated cell-cycle regulator with a large literature.

HCFC2 shares the Kelch domain architecture and the capacity to bind HBM-containing proteins, but is expressed differently, is not processed the same way, and has a literature that is perhaps two orders of magnitude smaller.

What follows for this graph: an HBM-based argument about the fusion applies to HCF-1 by direct evidence and to HCF-2 only by inference. There is no HCFC2 co-immunoprecipitation with menin, no mapped region, no structure, no functional experiment, and no leukaemia experiment. Every claim about HCF-2 in a KMT2A context would be an extrapolation from a paralogue plus a 2004 gel-filtration fraction.

Closing a forward reference in the graph's most-cited paper

PMID 15199122 is cited in 27 entries of this graph — more than almost any other paper — and is the founding citation for the WRAD position, the menin-MLL complex, and this project's adjudication entries about what that paper does and does not show (concept-founding-wrad-negative-is-a-deletion-mutant-not-a-fusion, concept-adjudication-the-graph-does-not-contradict-its-founding-citation).

HCFC2 is a partner reported in that paper which no entry in the graph had ever named. That is a small but real instance of the pattern the adjudication entries exist to police: a heavily cited paper accumulates a settled summary, and the parts of it outside that summary stop being read.

This entry does not claim HCF-2 is important. It claims that a partner in the field's founding paper should be visible in the graph with its evidence type attached, so the next reader can see that it is a gel-filtration co-elution and decide accordingly.

Facts and figures
uniprotQ9Y5Z7
length AA792
uniprot resolutiongene_exact:HCFC2 AND organism_id:9606 AND reviewed:true; exactly one reviewed record; primary gene name read back as HCFC2; length 792 aa checked against the entry on 2026-09-20
forward reference closedPMID 15199122 is cited in 27 entries of this graph and HCFC2, a partner it reports, was named in none of them
subnuclear localizationNUCLEOLUS - and it is the SHARPEST subnuclear answer in this tranche, because it is a positive assignment in human cells with the targeting determinant mapped. HCF-2 is nucleolar, conferred by one and a half C-terminal Fibronectin type 3 repeats and inhibited by the HCF-1 NLS, and the same paper states that HCF-1 by contrast IS EXCLUDED FROM NUCLEOLI [E_q93_hcfc2_loc2]. THE TWO PARALOGUES HAVE OPPOSITE SUBNUCLEAR ADDRESSES. That is the single most important thing this entry can say, because the entry's existing argument is that HCF-1 and HCF-2 are not interchangeable and the evidence for HCF-2's menin contact is a different kind of experiment from HCF-1's: the compartment now separates them too. NOTE FOR gene-hcfc1: that entry currently records 'NOT MEASURED. No subnuclear compartment has been published for HCFC1 in any system' - and this paper publishes a subnuclear statement about HCFC1, namely nucleolar exclusion. A negative assignment is still an assignment; see the correction note in data.contradicts_an_existing_entry.
localization shown for fusionNO - nobody has localised HCF-2 in any fusion, in any lineage. The fusion-context literature for this gene is exactly ONE record, and it is PMID 15199122, the Yokoyama 2004 founding paper that this entry already cites for the gel-filtration co-fractionation and which contains no HCF-2 localisation of any kind [E_q93_hcfc2_loc3]. The relevant unasked question follows from the nucleolus: the fusion's address is a KMT2A property and this graph carries localization-nucleolus-kmt2a-fusion as an open compartment question, so whether a NUCLEOLAR HCF family member can reach a fusion complex at all is a topological question nobody has posed.
paralogue
{
  "gene": "HCFC1",
  "graph_entry": "gene-hcfc1",
  "relationship": "host cell factor paralogues; HCFC1 is the one with a defined route into the KMT2A complex via the HCF-binding motif"
}
menin contact
{
  "method": "molecular sieving (gel filtration co-elution)",
  "interaction_type": "physical association",
  "source_pmid": "15199122",
  "n_source_publications_in_intact": 1,
  "coip_exists": false,
  "binding_region_mapped": false
}
literature
{
  "kmt2a_menin_records_raw": 1,
  "kmt2a_menin_records_excluding_the_source": 0,
  "aliases_searched": [
    "HCFC2",
    "HCF-2"
  ],
  "query": "(HCFC2[tiab] OR \"HCF-2\"[tiab]) AND (KMT2A[tiab] OR MLL[tiab] OR menin[tiab])"
}
depmap kmt2a selectivity
{
  "chronos_mean_kmt2a_rearranged": 0.1418,
  "chronos_mean_other_leukaemia": 0.0888,
  "difference": 0.053,
  "pan_essentiality_all_lines": 0.126,
  "selectivity_rank": 14972,
  "rank_denominator": 17728,
  "provenance": "Joined 2026-09-21 from analyses/depmap-kmt2a-selective-scan-full (generated 2026-09-19T10:12:06Z), the project's own genome-wide scan over 11 KMT2A-rearranged and 43 other leukaemia DepMap lines. NOT re-fetched and NOT independent of that scan: every caveat it carries applies here, including that the KMT2A-rearranged arm is a small number of lines drawn from nine individuals, that the rank denominator is 17,728 genes, and that a difference is not a dependency. Added because only 26 of 308 gene entries carried this number, which made any KMT2A-selectivity question answerable for 8% of the corpus.",
  "how_to_read": "A negative difference means MORE required in KMT2A-rearranged lines than in other leukaemia lines. A rank near 17,728 is ANTI-selective. Neither is evidence of a fusion-driven dependency on its own: check pan_essentiality_all_lines before calling anything selective, and note that a paralogue-redundant gene can score near zero for reasons that have nothing to do with this disease - see ana-the-paralogue-redundancy-excuse-is-not-tested-and-my-proxy-decided-the-answer."
}
localization
{
  "CONSTITUTIVE": "NUCLEUS AND CYTOPLASM. UniProt Q9Y5Z7 (fetched live 2026-09-21) carries two location values, 'Cytoplasm' and 'Nucleus', both on the same single ECO:0000269, PubMed:10196288 [E_q93_hcfc2_loc1]. That paper is the founding HCF-2 report - Johnson, Mahajan and Wilson, Herpes simplex virus transactivator VP16 discriminates between HCF-1 and a novel family member, HCF-2 - so for once UniProt's coded citation IS about the fact and IS the founding observation. Rule 91 passes here.",
  "AND_UNIPROT_IS_NINETEEN_YEARS_OUT_OF_DATE": "The far better measurement is absent from the record. Gudkova, Dergai, Praz and Herr localised HCF-2 directly and found that UNLIKE HCF-1, WHICH IS EXCLUDED FROM NUCLEOLI, HCF-2 IS NUCLEOLAR - an activity conferred by one and a half C-terminal Fibronectin type 3 repeats and INHIBITED BY THE HCF-1 NUCLEAR LOCALIZATION SIGNAL, in human and mouse cells [E_q93_hcfc2_loc2]. UniProt cites neither this paper nor the nucleolus. So the compartment record for this protein was one paragraph in a 1999 virology paper until this tranche opened the 2019 one.",
  "how_shown": "the 1999 call is from the founding HCF-2 characterisation; the nucleolar call is direct localisation in HEK-293 and mouse cells with domain mapping (the Fn3 repeats) and a dominance test against the HCF-1 NLS",
  "systems": "HEK-293 and mouse cells; herpesvirus-derived cell biology for the 1999 work. NO haematopoietic cell, no leukaemic cell, no KMT2A-rearranged cell",
  "node": "localization-nucleolus-kmt2a-fusion"
}
cell type
{
  "measured_in": "HEK-293 for the nucleolar localisation and the overexpression phenotypes, plus mouse cells for the expression survey [E_q93_hcfc2_loc2]; the 1999 founding work is herpesvirus cell biology [E_q93_hcfc2_loc1].",
  "expression": "UniProt Q9Y5Z7 tissue specificity: 'Highly expressed in testis. Detected at lower levels in spleen, thymus, prostate, ovary, small intestine and colon.' SPLEEN AND THYMUS ARE NAMED, so the haematopoietic compartment is at least on the list - the same situation as MAP3K14 in tranche 3 - but at low level and with no cell type resolved. Gudkova et al. additionally show HCF-2 is BROADLY PRESENT in human and mouse cells, which contradicts a reading of the UniProt comment as testis-restricted.",
  "in_leukaemia": "NOTHING. HCF-2's only appearance in this disease is by gel filtration in PMID 15199122, this entry's existing E1, and that is a biochemical co-fractionation and not a cellular measurement of any kind. There is no HCF-2 image, fractionation or compartment measurement in any leukaemic cell."
}
cell state
{
  "STATE_IS_PROLIFERATION_VERSUS_DIFFERENTIATION_AND_HCF_2_PUSHES_TOWARDS_DIFFERENTIATION": "Elevated HCF-2 in HEK-293 cells produces phenotypes REMINISCENT OF HCF-1-DEPLETED CELLS - inhibition of cell proliferation and mitotic defects - and inhibits cell-proliferation and metabolism gene-expression programmes while activating differentiation and morphogenesis programmes [E_q93_hcfc2_loc2]. So HCF-2 behaves as a functional ANTAGONIST of HCF-1's proliferative role, not as a redundant paralogue.",
  "why_that_is_pointed_for_this_graph": "HCF-1 is a founding member of the WILD-TYPE KMT2A complex that the fusion cannot bind (gene-hcfc1's central argument), and the defining state of this disease is a DIFFERENTIATION BLOCK. A paralogue of that subunit which raises differentiation programmes and lowers proliferation programmes when its level goes up is, on its face, the more interesting one to measure in a KMT2A-rearranged blast - and nobody has. The direction is not a prediction this entry can make: the experiment was overexpression in HEK-293, which is neither the lineage nor the dose.",
  "bounded": "No HCF-2 cell-state measurement exists in any haematopoietic or leukaemic cell."
}
localization bounded absence
{
  "date": "2026-09-21",
  "tool": "NCBI E-utilities esearch, db=pubmed",
  "run_by": "Q93",
  "queries": [
    {
      "query": "(\"HCFC2\"[tiab] OR \"HCF-2\"[tiab] OR \"HCF2\"[tiab])",
      "querytranslation": "\"HCFC2\"[Title/Abstract] OR \"HCF-2\"[Title/Abstract] OR \"HCF2\"[Title/Abstract]",
      "count": 88,
      "role": "operand control"
    },
    {
      "query": "HCFC2[tiab] AND (nucleolus[tiab] OR nucleolar[tiab])",
      "querytranslation": "\"HCFC2\"[Title/Abstract] AND (\"nucleolus\"[Title/Abstract] OR \"nucleolar\"[Title/Abstract])",
      "count": 0,
      "role": "THE DECISIVE ALIAS MEASUREMENT, half one"
    },
    {
      "query": "\"HCF-2\"[tiab] AND (nucleolus[tiab] OR nucleolar[tiab])",
      "querytranslation": "\"HCF-2\"[Title/Abstract] AND (\"nucleolus\"[Title/Abstract] OR \"nucleolar\"[Title/Abstract])",
      "count": 2,
      "role": "THE DECISIVE ALIAS MEASUREMENT, half two - 0 against 2, and the 2 are the only two subnuclear papers this protein has"
    },
    {
      "query": "(gene clause) AND (subnuclear clause of twelve terms)",
      "count": 2,
      "title_check": "PMID 31049581 (HCF-2 is nucleolar) and PMID 14629117 (C. elegans HCF compartmentalises to nucleus or mitochondria). Both on topic; zero noise.",
      "bound_not_reproducible_as_stored": "NOT REPRODUCIBLE AS STORED, flagged 2026-09-23. This `query` field records a SUMMARY of the search rather than the search: the clause text it names was never written down, so the string cannot be re-run and this bound could not be included in the cycle-71 audit that re-ran 40 of the corpus's other zero-bounds against the live index (all 40 still returned zero). The clauses have deliberately NOT been reconstructed - guessing them would manufacture a query that was never run, which is worse than an abbreviated one because it would look auditable. This flag does not dispute the count or the absence; it records that this particular bound is not independently checkable."
    },
    {
      "query": "(gene clause) AND (KMT2A/MLL fusion clause of nine terms)",
      "count": 1,
      "title_check": "PMID 15199122 only - the Yokoyama 2004 founding paper, already this entry's E1, with no localisation content.",
      "bound_not_reproducible_as_stored": "NOT REPRODUCIBLE AS STORED, flagged 2026-09-23. This `query` field records a SUMMARY of the search rather than the search: the clause text it names was never written down, so the string cannot be re-run and this bound could not be included in the cycle-71 audit that re-ran 40 of the corpus's other zero-bounds against the live index (all 40 still returned zero). The clauses have deliberately NOT been reconstructed - guessing them would manufacture a query that was never run, which is worse than an abbreviated one because it would look auditable. This flag does not dispute the count or the absence; it records that this particular bound is not independently checkable."
    },
    {
      "query": "(gene clause) AND (localisation clause) AND (fusion clause)",
      "count": 0,
      "bound_not_reproducible_as_stored": "NOT REPRODUCIBLE AS STORED, flagged 2026-09-23. This `query` field records a SUMMARY of the search rather than the search: the clause text it names was never written down, so the string cannot be re-run and this bound could not be included in the cycle-71 audit that re-ran 40 of the corpus's other zero-bounds against the live index (all 40 still returned zero). The clauses have deliberately NOT been reconstructed - guessing them would manufacture a query that was never run, which is worse than an abbreviated one because it would look auditable. This flag does not dispute the count or the absence; it records that this particular bound is not independently checkable."
    }
  ],
  "alias_measurement_verdict": "DECISIVE, and in the direction the brief said not to assume. The CURRENT symbol HCFC2 returns ZERO nucleolar records; the PROTEIN NAME HCF-2 returns TWO, and those two are the entire subnuclear literature for this protein. A beat that had searched only the HGNC symbol would have written 'no subnuclear compartment has been published' - which is exactly what gene-hcfc1 says about the paralogue, from the same missing paper. Tranche 4 measured that the retired-or-alternate-symbol question is a per-gene hypothesis: SKIC8/WDR61/SKI8 was decisive at 2:9:43, CCDC101 versus SGF29 was worthless at 4 versus 44. HCFC2 versus HCF-2 is 0 versus 2 on the decisive fact, which is the most consequential form of the trap - small numbers on both sides, and one of them is the whole answer.",
  "reading": "Titles and abstracts only; supporting figures not searched (brief rule 80).",
  "absence_class": "measured-not-curated"
}
contradicts an existing entry
{
  "entry": "gene-hcfc1",
  "field": "data.subnuclear_localization and data.localization.subnuclear",
  "currently_says": "NOT MEASURED. No subnuclear compartment has been published for HCFC1 in any system. ... SAY IT PLAINLY: UNPUBLISHED, not not-applicable.",
  "should_say": "A subnuclear STATEMENT about HCFC1 has been published and it is a negative assignment: HCF-1 is EXCLUDED FROM NUCLEOLI, stated as the direct contrast in the paper that establishes HCF-2 is nucleolar. That is not the same as a positive compartment - HCF-1 still has no body or domain assigned to it - but 'no subnuclear compartment has been published in any system' is too strong, and the correct wording is that the only published subnuclear fact about HCF-1 is where it is NOT.",
  "citation": {
    "pmid": "31049581",
    "doi": "10.1093/nar/gkz307",
    "read": "abstract only, fetched from efetch 2026-09-21; the exclusion statement is in the abstract's own words ('Unlike HCF-1, which is excluded from nucleoli, HCF-2 is nucleolar')"
  },
  "note": "Reported, not edited - gene-hcfc1 belongs to the interactome3 beat. This is a narrowing of an absence claim, not a factual error, and it is worth the coordinator's minute because gene-hcfc1's absence claim is load-bearing for that entry's argument that a wild-type-complex subunit has never been compared between fusion and non-fusion cells."
}
How this could bite us back
  • Nothing in this entry supports an intervention. It is recorded specifically so that a future reader does not upgrade a gel-filtration fraction into a menin partner by association with HCF-1.
  • If HCF-2 did substitute for HCF-1 in some cells, an HCF-1-directed strategy would have a built-in escape that nobody is measuring.
Still open
  1. Is HCFC2 in the menin complex at all, or was it a co-eluting contaminant in a 2004 gel filtration? One endogenous co-IP would settle twenty-two years of silence.
  2. Does HCFC2 bind the KMT2A HCF-binding motif, the domain the fusion loses? If it does, it belongs in the subtraction beat; if it does not, it has no route into fusion biology.
  3. Is HCFC2 expressed in KMT2A-rearranged blasts at levels where it could matter, and does it compensate for HCFC1?
Every source behind this entry (7)
  1. E1moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper

    The founding paper establishing that MLL forms a SET1-like histone methyltransferase complex with menin to regulate Hox gene expression reports HCFC2 among the components of that complex.

    Leukemia proto-oncoprotein MLL forms a SET1-like histone methyltransferase complex with menin to regulate Hox gene expression. · Yokoyama A, Wang Z, Wysocka J, Sanyal M, Aufiero DJ, Kitabayashi I, Herr W, Cleary ML · Mol Cell Biol 2004
    What this evidence cannot show

    `moderate` rather than `established` because the evidence for HCFC2 specifically within this paper is gel filtration co-elution (see E2), which is the weakest method it uses. The paper's headline conclusions rest on co-immunoprecipitation and are correspondingly stronger. This paper is readable only through the PMC HTML route (PMC480881, about 69,400 characters) - Europe PMC fullTextXML returns HTTP 500 and efetch db=pmc returns a document with no body element.

    Evidence that argues against this (1)
  2. E2established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    IntAct curates the MEN1-HCFC2 interaction from PMID 15199122 with the method 'molecular sieving' and interaction type 'physical association'. The MEN1-KMT2A rows from the same publication are curated as anti-bait co-immunoprecipitation. IntAct holds no other source publication for MEN1-HCFC2.

    What this evidence cannot show

    Molecular sieving establishes that two proteins appear in the same size-exclusion fraction. Two proteins of similar hydrodynamic radius co-elute whether or not they touch, and a complex of many subunits places every subunit in the same fraction regardless of which contacts which. It is evidence of co-complex membership at best, never of a binary interaction. INTERACTION PROVENANCE (Q76, 2026-09-21, live IntAct REST): IntAct says so itself in a field this entry did not read. The single MEN1-HCFC2 record, EBI-592758, carries the expansion flag psi-mi:MI:1060 SPOKE EXPANSION - the binary pair was derived by a curator from an n-ary experiment and was never asserted as an observation. This entry's reasoning about molecular sieving was therefore right, and the database agrees with it explicitly. The related KMT2A-HCFC2 pair is six records, all six spoke-expanded, from PMIDs 15199122, 28514442 and 33961781, and no PDB entry contains Q9Y5Z7 at all - HCFC2 has none. NOTE ALSO that the record was reached here through the IntAct REST endpoint; the PSICQUIC id: query used by this project's older interactome analyses reaches only 43.6% of MEN1's record, so any re-check of this entry should use REST. See ana-two-thirds-of-the-curated-interactome-is-a-row-nobody-observed and ana-psicquic-id-queries-miss-half-of-kmt2as-intact-record.

    Evidence that argues against this (1)
    • No subsequent interaction proteomics has recovered MEN1-HCFC2, including BioPlex's dual proteome-scale network, which does recover HCFC1 partners routinely. Huttlin EL et al. 2021
  3. E3strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database

    A PubMed title/abstract search over HCFC2 and HCF-2 against KMT2A, MLL or menin returns exactly one record, which is PMID 15199122 itself. HCFC2 has never been the subject of a second paper in this field.

    What this evidence cannot show

    'HCF-2' is a short alias that also denotes heparin cofactor II (SERPIND1) in older literature, which would inflate rather than deflate this count; it did not, because the count is one. A complex-level query such as 'host cell factor' plus 'MLL' was not run and could in principle return work that frames at the complex level.

    Evidence that argues against this (1)
    • A title-checked search count is two judgements stacked: the query decides what is reachable, and the reader decides what is 'on-beat'. Both are recorded here, which is the right practice, but neither is a measurement. This project has since established that field-scoped queries can return zero regardless of the literature, and that a symbol-level count misses work indexed under the pathway or the complex rather than the gene - so a small count bounds what was found, not what exists. Shan X et al. 2017
  4. E4established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    HCFC2 is UniProt Q9Y5Z7, 792 aa, primary gene name read back as HCFC2, recommended name Host cell factor 2; its paralogue HCFC1 is the host cell factor already carried in this graph as gene-hcfc1.

    What this evidence cannot show

    A database record. The accession was resolved with gene_exact, which matches synonyms, so the primary gene name and the 792 aa length were both read back off the entry; exactly one reviewed human record was returned.

    Evidence that argues against this (1)
    • A reviewed database record fixes the canonical sequence and primary symbol on the date it was read, and nothing more. It does not establish that the protein is expressed in KMT2A-rearranged blasts, which isoform is present, or that the subunit acts in this disease. Accession and length are asserted so that a swap fails verify-accessions.py - a defence this graph needs because IKK-family and NF-kB subunit names collide heavily in the older literature - not because the record carries biological weight. Xiu Y et al. 2018
  5. E_q93_hcfc2_loc1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    UniProt Q9Y5Z7 carries exactly two subcellular locations, Cytoplasm and Nucleus, both attributed to the same single ECO:0000269 PubMed:10196288 - the founding HCF-2 paper, in which VP16 is shown to discriminate between HCF-1 and the newly identified HCF-2 - so the coded citation here is genuinely about the fact and is the founding observation.

    What this evidence cannot show

    Rule 91 passes on the pointer and fails on the currency. The cited paper is about HCF-2 and does contain its localisation, but it is from 1999, it is a virology paper, and UniProt does not cite the 2019 study that localised HCF-2 properly and found it nucleolar. A reader filtering Q9Y5Z7 on ECO:0000269 gets a true but twenty-year-stale answer and no hint that a better one exists.

    Evidence that argues against this (1)
    • The reason not to treat the 1999 nucleus-plus-cytoplasm call as settled is that the HCF family's C-terminal targeting signal is genuinely PROMISCUOUS, not merely under-studied. The single C. elegans HCF orthologue, which is most closely related to human HCF-2, accumulates in nuclei in the worm with NUCLEOLAR SPARING in larvae and adults but diffusely in the nucleoplasm earlier in development - and the same GFP fusion accumulates in the MITOCHONDRIA of a stable HeLa line, with the determinants for both destinations interdigitated in the last 23 residues. So 'nucleus and cytoplasm' for an HCF protein may be reporting a mixture of destinations set by species, stage and expression level rather than one address, and a mitochondrial pool for human HCF-2 has never been excluded. Izeta A et al. 2003
  6. E_q93_hcfc2_loc2strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    In HUMAN HEK-293 and mouse cells, HCF-2 is NUCLEOLAR - an activity conferred by one and a half C-terminal Fibronectin type 3 repeats and inhibited by the HCF-1 nuclear localization signal - while HCF-1 by contrast is EXCLUDED from nucleoli; elevated HCF-2 in HEK-293 inhibits cell proliferation, causes mitotic defects, and inhibits proliferation and metabolism gene-expression programmes while activating differentiation and morphogenesis programmes.

    HCF-2 inhibits cell proliferation and activates differentiation-gene expression programs. · Gudkova D, Dergai O, Praz V, Herr W · Nucleic Acids Res 2019
    What this evidence cannot show

    HEK-293, an embryonic kidney line, and mouse cells - not haematopoietic, not leukaemic, no fusion (brief rule 73, and the claim names the system first). The proliferation and gene-programme phenotypes come from ELEVATED HCF-2 rather than from loss, so they establish what excess HCF-2 does and not what endogenous HCF-2 does; the authors' own framing is that the phenotypes are reminiscent of HCF-1 DEPLETION, which is a comparison rather than an equivalence. This claim is bounded by the abstract: the full text was not read.

    Evidence that argues against this (1)
    • The strongest objection is the one the brief warns about for every overexpression compartment result: a protein pushed above its physiological level can reach a compartment it does not normally occupy, and the nucleolus is the classic destination for over-expressed basic proteins. The determinant mapping argues against pure artefact - a specific one-and-a-half Fn3 repeat unit confers it and the HCF-1 NLS dominantly suppresses it, which is hard to get from a non-specific overload - but the experiment that would settle it, endogenous HCF-2 co-stained with fibrillarin or nucleophosmin at exposure adequate for a minority pool, has not been done. That is the same missing experiment gene-paf1 names for its own contested nucleolar question, which is the second time in this tranche that the resolving experiment is identical. Johnson KM et al. 1999
  7. E_q93_hcfc2_loc3strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database

    Bounded 2026-09-21: HCFC2[tiab] AND (nucleolus[tiab] OR nucleolar[tiab]) returns 0 records while "HCF-2"[tiab] AND the same clause returns 2, and those 2 are the entire subnuclear literature for this protein; the gene clause over HCFC2, HCF-2 and HCF2 returns 88 records; and the gene clause against a nine-term KMT2A/MLL fusion clause returns exactly 1, PMID 15199122, which contains no localisation.

    What this evidence cannot show

    Titles and abstracts only; supporting figures not searched (brief rule 80). The 88-record operand control is inflated by HCF2 as a string in unrelated contexts and was not exhaustively title-checked; the counts that carry weight here are the zero and the two, both of which were title-checked in full.

    Evidence that argues against this (1)
    • The measurement argues against the generalisation it is tempting to draw from it. This graph has now measured the alias question on four genes and the results are 2:9:43 (decisive), 4 versus 44 (worthless), 102 with and without a retired symbol (no effect on count, decisive for provenance), and 0 versus 2 here. There is no rule in that - which is precisely why the brief demotes it to a per-gene hypothesis. What IS general is the cost asymmetry: an alias search that adds nothing costs one query, and an alias search skipped on a gene like this one costs a false 'nobody has published a subnuclear compartment', which is the exact sentence sitting in the paralogue's entry right now. Gudkova D et al. 2019
Connected to