Oncofusion

start / graph / mechanism-menin-chk1-stimulates-homology-directed-repair

Mechanismmoderate confidence 3 of 5: One strong study, or several smaller consistent ones.Q36-menin-residue-axis

Menin stimulates homology-directed repair through Chk1 and the region required is 1-228: a 2010 paper that is cited in no entry of this graph and in no reference list of the 2026 paper that reports the same conclusion

also called Gallo 2010 menin HDR · menin-Chk1 at the double-strand break · menin 1-228 HR region

In 2010 a group showed that menin makes human cells better at the accurate kind of DNA break repair, that menin piles up at the break together with the checkpoint kinase Chk1, and that removing menin's first 228 amino acids destroys both. Nothing in this knowledge graph cites that paper, and neither does the 2026 paper whose title says menin is a key scaffold for the same process.

The same thing, for a scientist

Gallo et al. (FEBS Lett 2010, PMID 20969866) report, in human cells with the I-SceI reporter assay, that **menin stimulates homology-directed repair**; that menin accumulates with Chk1 at the site of the double-strand break; that menin and Chk1 interact in vivo; and that **deletion of menin's first 228 amino acids impairs both the Chk1 interaction and the ability to stimulate HD repair** [E1]. Three consequences for this graph. **(1) It is uncited here.** A grep of all 2,176 node files returns zero files containing the PMID, while the sibling Farley 2006 ATR-CHK1 paper is cited in four and `gene-chek1` exists with eleven evidence items - so this is an absence in a covered area, not an uncovered area. **(2) It is uncited by Lian et al. 2026**, whose title asserts that *the tumor suppressor menin is a key scaffold mediator for homologous recombination repair*; their introduction reaches Chk1 through Farley 2006 instead [E2]. The 2026 result is not wrong and is far more detailed, but the field's priority on the core claim is 2010, and a reader of this graph could not have known that. **(3) It puts a THIRD, barely-overlapping region on menin's DNA-repair axis.** Gallo's 1-228 shares 15 residues with UniProt's FANCD2 region 214-390 and **zero** with the gamma-H2A.X motif 371-400 [E3]. Mapped onto the coordinate parse in `ana-q36-menin-residue-axis`, 1-228 is 88 residues of the NTD/palm lobe plus 134 of the thumb, and contains only 7 of the 21-26 residues any clinical menin inhibitor touches [E3]. **So three papers over sixteen years place menin's DNA-repair function in three different parts of the protein, and only one of the three regions is small enough to be an interface.**

What it looks like

No three-dimensional model is available for this protein, so the map above is the whole picture. That is itself informative: AlphaFold does not model chains this long, and the parts that have been crystallised are held under the entries for the individual domains.

Go deeper
What the 2010 paper establishes, graded separately
propositiongradewhy
menin stimulates homology-directed repair of an I-SceI break in human cellsstronga direct functional assay with a defined lesion, which is the right assay for the claim
menin accumulates with Chk1 at the break sitemoderatereported in the abstract without the method being stated there; full text not read here
menin and Chk1 interact in vivomoderatesame
deletion of menin 1-228 impairs bothmoderatea single large deletion in a compact single-domain protein is as likely to report folding as interface - see the caveat on E1

The fourth row is the one that carries the region claim and it is the weakest. Removing 228 of menin's 610 residues removes the entire NTD and the entire thumb, which between them supply 21 of the 29 menin residues that contact the KMT2A MBM1 peptide. A construct missing them is not menin with a surface removed; it is a different protein. The same objection is already recorded in this graph against the SvID's dN360 construct (interface-menin-suv39h1-svid-360-445, open question 1) and it applies here with more force, because 1-228 is a larger fraction.

Three regions, sixteen years, and almost no overlap
claimregionwidthobserved residuesspatial lobes it occupiesoverlap with the other two
Gallo 2010, Chk1 + HDR1-228228227NTD/palm 88, thumb 134, fingers 515 residues with FANCD2; 0 with gamma-H2A.X
Jin 2003, FANCD2 (via UniProt)214-390177173NTD/palm 75, thumb 19, fingers 7915 with Gallo; 20 with gamma-H2A.X
Lian 2026, gamma-H2A.X371-4003016fingers 160 with Gallo; 20 with FANCD2

Together the three regions cover residues 1-400, which is 66% of menin and essentially the whole ordered part of the protein visible in a crystal. That is what it looks like when a function is mapped three times by deletion in a single-domain protein: the union of the maps approaches the protein.

The honest reading is not that one of the three is right. It is that two of the three are truncation brackets around a globular domain and cannot be read as surfaces, which is exactly the argument ana-the-fancd2-region-is-a-third-of-menins-surface makes for 214-390 with numbers. The 30-residue motif is the only one of the three that is narrow enough to be an epitope, and it is also the only one supported by an internal deletion plus a sufficient peptide rather than by an N-terminal truncation.

Why this was invisible, and the query trap that hid it

The token is punctuated. Measured here with scripts/pubmed_safe.py on 2026-09-22, with the querytranslation read back for every line:

querytranslationcount
H2AX[tiab]"H2AX"[Title/Abstract]6,971
"H2A.X"[tiab]"H2A.X"[Title/Abstract]784
menin[tiab] AND H2AX[tiab]"menin"[Title/Abstract] AND "H2AX"[Title/Abstract]0
menin[tiab] AND "H2A.X"[tiab]"menin"[Title/Abstract] AND "H2A.X"[Title/Abstract]1 (PMID 42578372)
menin[tiab] AND "homologous recombination"[tiab]as written3
menin[tiab] AND "DNA repair"[tiab]as written19

The unpunctuated spelling returns a clean, confident zero on the single paper this whole axis rests on. Both operands are large - menin[tiab] is 1,264 and H2AX[tiab] is 6,971 - so the zero passes a rule-67 operand check and is still false. It is the recall half of the alias problem, and the fix is one character.

Gallo 2010 was reachable the whole time: it is one of the three records returned by menin[tiab] AND "homologous recombination"[tiab], alongside the 2026 paper and the chidamide/MI-3 combination paper (PMID 31590682) that this graph already cites in eleven entries. A three-record query on the beat's own topic had never been run, or had been run and its records not opened.

Facts and figures
mechanism classDNA double-strand break repair; homology-directed repair
absence classmeasured-not-searched
absence class noteFor the Gallo paper specifically: it was published, indexed and reachable by a three-record query the whole time. This graph's failure to hold it is a search-space failure, not a data failure, which is what `measured-not-searched` names.
shown for fusionNO - nobody has looked in any fusion. The I-SceI HDR assay was in human cells with no fusion; there is no KMT2A-rearranged experiment in any of the three papers that map menin's DNA-repair function.
epigenetic readoutnone in the 2010 paper; the 2026 paper places H3K36me3 downstream of the same axis via SETD2
domains
menin region required for…1.000menin region required for the Chk1 interaction and HDR stimulation (Gallo 2010, N-terminal truncation): 1union of all three DNA-re…1.000union of all three DNA-repair region claims: 1FANCD2 interaction region…214.0FANCD2 interaction region (UniProt, from PMID 12874027): 214gammaH2A.X motif (PMID 42…371.0gammaH2A.X motif (PMID 42578372): 371
partners
[
  "gene-men1",
  "gene-chek1"
]
domains — the numbers behind the chart
[
  {
    "name": "menin region required for the Chk1 interaction and HDR stimulation (Gallo 2010, N-terminal truncation)",
    "start": 1,
    "end": 228
  },
  {
    "name": "FANCD2 interaction region (UniProt, from PMID 12874027)",
    "start": 214,
    "end": 390
  },
  {
    "name": "gammaH2A.X motif (PMID 42578372)",
    "start": 371,
    "end": 400
  },
  {
    "name": "union of all three DNA-repair region claims",
    "start": 1,
    "end": 400
  }
]
region comparison
{
  "gallo_2010_1_228": {
    "width": 228,
    "observed": 227,
    "lobes": {
      "ntd_palm": 88,
      "thumb": 134,
      "fingers": 5
    },
    "overlap_with_fancd2_region": 15,
    "overlap_with_gammah2ax_motif": 0,
    "menin_inhibitor_contact_residues_inside": [
      155,
      177,
      178,
      179,
      180,
      181,
      182
    ]
  },
  "jin_2003_214_390": {
    "width": 177,
    "observed": 173,
    "lobes": {
      "ntd_palm": 75,
      "thumb": 19,
      "fingers": 79
    },
    "overlap_with_gallo": 15,
    "overlap_with_gammah2ax_motif": 20
  },
  "lian_2026_371_400": {
    "width": 30,
    "observed": 16,
    "lobes": {
      "fingers": 16
    },
    "overlap_with_gallo": 0,
    "overlap_with_fancd2_region": 20
  },
  "union_covers_pct_of_menin": 65.6
}
bounded absence
{
  "date": "2026-09-22",
  "tool": "PubMed E-utilities esearch via scripts/pubmed_safe.py, querytranslation read back",
  "queries": {
    "bleximenib[tiab]": 19,
    "JNJ-75276617[tiab]": 5,
    "JNJ75276617[tiab]": 5,
    "bleximenib[tiab] OR JNJ-75276617[tiab] OR JNJ75276617[tiab]": 20,
    "bleximenib[tiab] AND H2AX[tiab]": 0,
    "bleximenib[tiab] AND \"H2A.X\"[tiab]": 0,
    "bleximenib[tiab] AND \"DNA repair\"[tiab]": 0,
    "bleximenib[tiab] AND \"DNA damage\"[tiab]": 0,
    "bleximenib[tiab] AND \"homologous recombination\"[tiab]": 0,
    "JNJ-75276617[tiab] AND \"H2A.X\"[tiab]": 0,
    "ziftomenib[tiab] AND \"DNA damage\"[tiab]": 0,
    "revumenib[tiab] AND \"DNA damage\"[tiab]": 1,
    "menin[tiab] AND H2AX[tiab]": 0,
    "menin[tiab] AND \"H2A.X\"[tiab]": 1,
    "menin[tiab] AND \"homologous recombination\"[tiab]": 3,
    "menin[tiab] AND \"DNA repair\"[tiab]": 19,
    "H2AX[tiab] (operand control)": 6971,
    "\"H2A.X\"[tiab] (operand control)": 784,
    "revumenib[tiab] (operand control)": 103,
    "ziftomenib[tiab] (operand control)": 46
  },
  "statement": "No title or abstract in PubMed pairs bleximenib, under any of three spellings, with any DNA-repair readout. Titles and abstracts only; supporting figures not searched."
}
How this could bite us back
  • If menin stimulates homologous recombination, a menin inhibitor given to a child is a partial, reversible HR inhibitor, and HR inhibition is the mechanism by which several agents cause secondary malignancy. That risk is invisible in a response-rate endpoint and in a two-year follow-up.
  • The converse is a missed opportunity rather than a harm: if menin loss impairs HR, menin inhibitors plus a PARP inhibitor or a crosslinker is a synthetic-lethal combination nobody has tested in KMT2A-rearranged disease, and the graph already holds `ana-the-menin-parp-experiment-survives-and-gains-a-rival-rationale`.
  • Building either argument on a 228-residue deletion is the weak point. If that construct is simply unfolded, the HR rationale loses one of its three legs and the remaining two are a paywalled 2003 co-immunoprecipitation and one 2026 paper in a lung line.
Still open
  1. Is the menin 1-228 deletion construct folded? A thermal shift on it against full-length menin would separate 'lost interface' from 'lost protein' in an afternoon, and until somebody runs it the 1-228 region claim cannot be used.
  2. Does menin bind Chk1 directly, and if so where? The 2010 abstract reports an in vivo interaction and a truncation; there is no structure, no affinity and no reciprocal mapping on Chk1.
  3. Do the 2010 I-SceI result and the 2026 DR-GFP-class result agree quantitatively? Both measure homology-directed repair with an endonuclease-induced break, sixteen years apart, in different cells, and nobody has put the two numbers side by side.
  4. Does the 2010 result survive in a KMT2A-rearranged cell? Every menin DNA-repair experiment in the literature is in a fibroblast, a lung line or a generic human line, and the disease this graph is about is not represented in any of them.
Every source behind this entry (4)
  1. E1moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper

    In human cells, menin stimulates homology-directed DNA repair induced by the rare endonuclease I-SceI and accumulates with Chk1 at the site of the double-strand break; menin and Chk1 interact in vivo; and deletion of the first 228 amino acids of menin impairs both the Chk1 interaction and the ability to stimulate HD repair.

    Menin stimulates homology-directed DNA repair. · Gallo A, Agnese S, Esposito I, Galgani M, Avvedimento VE · FEBS Letters 2010
    What this evidence cannot show

    ABSTRACT ONLY - the full text was not retrieved in this beat and no route beyond PubMed was attempted, so n, cell line, the localisation method and the deletion construct's expression and stability are all unknown. `moderate` rather than `strong` for that reason and for one substantive one: deleting menin's N-terminal 228 residues removes the whole NTD and the whole thumb, 37% of the protein and 21 of the 29 residues that contact the KMT2A MBM1 peptide, so the construct may be reporting misfolding rather than a lost interface. The paper is not a leukaemia paper, contains no KMT2A fusion and is not in a haematopoietic cell. The authors' own wording for the model is 'suggesting'.

    Evidence that argues against this (1)
    • A Drosophila study designed to test whether MEN1 acts with the Fanconi pathway in crosslink repair found different mutation spectra and no genetic interaction, so menin's contribution to repair is not a single coherent pathway claim and the 2010 result should not be read as confirming the 2003 one. Marek LR et al. 2008
  2. E2strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    The 2026 paper asserting that menin is a key scaffold mediator for homologous recombination repair does not cite the 2010 paper titled 'Menin stimulates homology-directed DNA repair'; it reaches the Chk1 connection through a 2006 paper on menin localisation to chromatin via an ATR-CHK1 pathway, in one introductory sentence grouping RPA, FANCD2 and Chk1.

    The tumor suppressor menin is a key scaffold mediator for homologous recombination repair. · Lian A, Zhu X, Jin B, Gu G, Xu B, Zhang L, et al. · Nucleic Acids Research 2026
    What this evidence cannot show

    Bounded to the reference list as served by Europe PMC in the PMC13458390 full text (96,530 characters), searched for the author surname, for 'febslet' and for 'homology-directed'; the only 'homology-directed' hit in the reference list is Pierce et al. 1999 on XRCC3. A reference list can be incomplete in a converted full text, and an uncited paper is not a hidden paper - the 2010 work is indexed in PubMed and the omission may be an ordinary oversight rather than anything more. This entry records the omission, not a motive.

    Evidence that argues against this (1)
    • The 2026 paper's claim is narrower than its title and is about a specific scaffolding mechanism - sequential recruitment of SETD2, LEDGF and CtIP with H3K36me3 reprogramming - which the 2010 paper does not address. On that mechanism there is no priority question at all, and reading the omission as a priority dispute would overstate it. Gallo A et al. 2010
  3. E3established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    Menin 1-228 comprises 88 residues of the NTD/palm spatial lobe, 134 of the thumb and 5 of the fingers; it overlaps UniProt's FANCD2 region 214-390 by 15 residues and the gamma-H2A.X motif 371-400 by none; and it contains only 7 of the 21-26 menin residues contacted by any of the four clinical menin inhibitors, all seven in the 155-182 stretch.

    What this evidence cannot show

    Lobe assignment is a contact-graph clustering of one crystal form with the stated boundary uncertainties in `ana-q36-menin-residue-axis`; the NTD|thumb boundary in particular is a convention that cuts a helix. Residue 1 is unmodelled in the reference deposit. The overlap arithmetic is exact and needs no structure; only the lobe composition depends on the parse.

    Evidence that argues against this (1)
    • Three regions failing to overlap is equally consistent with menin having three separate repair-relevant surfaces as with two of the three maps being artefacts of large deletions. This entry argues the latter from the widths, which is an argument from study design and not a measurement of either surface. Huang J et al. 2012
  4. E4established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    PubMed returns 0 records for menin[tiab] AND H2AX[tiab] and 1 for menin[tiab] AND "H2A.X"[tiab], with non-empty query translations in both cases and both operands large (menin 1,264; H2AX 6,971; "H2A.X" 784), so the unpunctuated spelling produces a genuine-looking zero on the only paper that maps the menin-gamma-H2A.X contact; menin[tiab] AND "homologous recombination"[tiab] returns 3 and menin[tiab] AND "DNA repair"[tiab] returns 19.

    What this evidence cannot show

    Counts move as PubMed indexes. All three records from the homologous-recombination query were opened and their titles read, per the registry row warning that a non-zero hit count is not evidence the token is in any document you can read. The name list searched for the compound arm of the related bounded absence was bleximenib, JNJ-75276617 and JNJ75276617; for the readout arm, H2AX, "H2A.X", "gamma-H2A.X", "DNA repair", "DNA damage" and "homologous recombination". This is a title/abstract bound only - a gamma-H2A.X western in a supplementary figure of a bleximenib paper would be invisible to it (brief rule 80).

    Evidence that argues against this (1)
    • The spelling asymmetry may be partly an artefact of which journals use which style rather than a general trap, and 6,971 against 784 suggests the unpunctuated form is the majority usage - so for most questions H2AX is the better token and it is only this one paper that is reachable solely through the punctuated form. Lian A et al. 2026
Connected to