A residue axis for menin, derived from coordinates: three spatial lobes, not four named ones, and the sharpest seam in the protein runs through the drug pocket
also called menin thumb palm fingers boundaries · menin domain parse · O00255 residue axis
Everyone describes menin as a curved left hand with a thumb, a palm and fingers, but nobody writes down which amino acid each part starts and ends at, so no claim about them can be checked. Measuring the actual atomic coordinates of 69 menin structures gives numbers for the first time in this graph - and shows the protein really has three lumps, not four, with the cleanest division falling right inside the pocket that every menin drug binds.
The same thing, for a scientist
Menin's `NTD / thumb / palm / fingers` nomenclature comes from Huang et al. (Nature 2012). Its main text - read in full here from PMC3983792 - gives **no residue numbers**, deferring them to Supplementary Fig. 4 and Supplementary text, which are not retrievable [E1]. Every domain-level menin claim in this graph therefore sits on an unfalsifiable axis. This analysis derives one from coordinates. Over all 69 O00255 PDB deposits, residues were counted as covered only where the deposited number carries the UniProt residue identity in a majority of its +/-3 neighbourhood; **6S2K fails that test completely (verified fraction 0.000) and eight bleximenib-series deposits renumber residues 458-489** [E2]. On the best-covered deposit, 3U84 (505 verified observed residues, whole-chain numbering readback clean at 504 of 505 positions, the single mismatch being a cloning-artefact residue 1), a 5 A heavy-atom residue contact graph was cut two independent ways. **Unconstrained spectral bisection returns three substantial spatial lobes plus one detached C-terminal helix, and 92.8% of all contacts stay inside a lobe**: lobe 1 = 2-90 + 239-312 (163 residues), lobe 2 = 91-232 (143), lobe 3 = 315-386 + 402-459 + 520-581 (186), lobe 4 = 596-608 (13) [E2]. **Lobe 2 is the thumb and lobe 3 is the fingers, but the NTD and the palm come out as one lobe**, so the four names describe sequence order, not four separable structural units. A sequence-contiguous cut scan agrees on where the fingers begin and disagrees about nothing else: the deepest single boundary in the whole protein is **after residue 317** (64 crossing contacts, normalised score 6.72 against a median of 14.21 over all cuts, and 41% fewer crossings than the median random contiguous bipartition of the same shape), and it falls in the four-residue loop between helix 297-313 and helix 318-331 [E2]. The parse this analysis defends is **NTD 1-90, thumb 91-232, palm 233-317, fingers 318-610**, with the boundary uncertainties stated below and one of them large. The consequence that matters for this project: **the clinical menin-inhibitor pocket straddles all three lobes and is not the same surface as the KMT2A MBM1 footprint** - revumenib and the MBM1 peptide share only 15 of the 37 menin residues in their union (Jaccard 0.405), and 43.5% of revumenib's footprint and 46.2% of ziftomenib's lies in the fingers lobe against 17.2% of the peptide's [E2].
Tell me more about this picture
3U84 is the best-covered menin deposit: 505 residues whose deposited numbers were each verified to carry the UniProt residue identity.
Tell me more about this picture
The pocket residues are within 4.5 A of ziftomenib in 8VA6, mapped onto 3U84 numbering; the two structures share the same numbering frame.
Tell me more about this picture
Residues 389-397, 462-519, 530-533, 540-543, 590-595 and 609-610 are in no deposit and cannot be drawn.
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.
What the field actually states, and why a coordinate parse was necessary
Huang et al. 2012 is the founding structural paper and the source of the hand metaphor. Its full text, retrieved here through the PMC HTML route after fullTextXML returned HTTP 500, says:
"Menin consists of four associated domains, an N-terminal domain (NTD) characterized by a long beta-hairpin, a transglutaminase-like domain that forms the thumb, a helical palm domain that contains three TPR motifs, followed by a C-terminal fingers domain (Fig. 1c, Supplementary Fig. 4 and Supplementary text)."
No residue numbers appear anywhere in the main text or in the figure legends 1. Q34 tried and failed to retrieve the supplementary; this beat did not repeat the attempt.
The field's downstream usage is qualitative in exactly the same way. Lian et al. 2026 - the paper that maps the gamma-H2A.X motif - writes "menin interacts with gamma-H2A.X through its Palm and Fingers domains" and "We generated truncations of the Palm/Fingers domains", with the constructs in a supplementary figure 3. So the only place the numbers exist is inside supplementary material.
One published table does carry numbers, and it cannot be used as it stands. Nelakurti et al. (Cancers 2020) Table 1, Coordinates and functions of MEN1 domains and interacting proteins, tabulates NTD, Thumb, Palm and Fingers as "Crystal structure identified domain" with coordinates. In both the Europe PMC JATS and the raw bytes served by that endpoint the cells read 1-100, 101-1230, 231-1300, 301-1305, 479-1497, 588-1608, 219-1395 4. Three of those are independently known: NLS1 is 479-497 and NLS2 is 588-608, and the FANCD2 row is UniProt's 214-390 shifted by the +5 isoform-1 offset the same paper uses elsewhere (it writes "D423N (D418N in isoform 2)"). So a spurious 1 follows the dash, and the decoding is 101-230, 231-300, 219-395. Applied to the Fingers row it yields 301-305, which is impossible, and the same paper's MYC row reads 360-615 (fingers). The table is internally inconsistent about which isoform it numbers in and its rendering is corrupt. It is recorded here as evidence that somebody has tried, not as a source of boundaries.
Method, in the order it was run, and what each step can and cannot support
analyses/q36-menin-residue-axis/run.py. Every number is computed at run time; nothing is read off a deposit and nothing is from recall.
- UniProt O00255 fetched live, primary gene name asserted to be
MEN1and length asserted to be 610 before anything else runs. - Coverage sweep over all 69 O00255 deposits.
_pdbx_poly_seq_schemegives, per residue, whether it is in the construct and whether it is observed in the coordinates - two different facts. Every residue number is verified against the UniProt residue identity. See the next section for why. - Reference frame. The deposit with the most verified observed residues is 3U84 (505). Its numbering was read back at every observed position, not at a sample.
- Secondary structure from 3U84's own
_struct_confand_struct_sheet_rangeloops - 28 helices and 6 strands. - Two independent parses of the same contact graph (5 A heavy-atom, contacts closer than 4 in sequence excluded so the backbone does not dominate): an unconstrained spectral bisection, which is allowed to produce non-contiguous lobes, and a dynamic program over strictly sequence-contiguous blocks of at least 40 residues.
- A null for the contiguous parse (rule 84): 2000 random contiguous partitions of the same shape, seed 20260922.
- Shrake-Rupley solvent accessibility on the isolated chain, 256 sphere points.
- Ligand footprints per chain pair, so a crystal-packing contact between two copies is not reported as an interface.
What this method cannot do. It parses one crystal form of a construct that deletes an internal loop. It cannot see 83 residues that no deposit models. It has no access to dynamics, so a lobe boundary here is a boundary in a static structure. And a contact-graph parse is a statement about packing, not about folding independence or evolutionary origin - the transglutaminase-like assignment of the thumb is a fold-recognition claim from Huang et al. that this analysis neither tests nor needs.
The instrument defect this beat found: a deposited residue number is not a UniProt residue number
The first version of the sweep trusted _pdbx_poly_seq_scheme.pdb_seq_num, and it produced two findings that are false. In 9WKU the residues numbered 460-489 read QSEKMKGMKELLVATKINSSAIKLQLTAQS, which is O00255 520-549 - the deposit renumbers after an engineered internal deletion. Trusting that gave "nine deposits model NLS-1 (479-497)". In 6S2K the whole chain is renumbered and it gave "6S2K models the entire 460-519 loop". Both were written down in this session and both are wrong 2.
Corrected by verifying every residue's identity, with a neighbourhood rule so that an engineered point mutation (a lone mismatch) is kept and a renumbered block is rejected:
| before verification | after | |
|---|---|---|
| residues never observed in any deposit | 25 | 83 |
| deposits modelling any part of NLS-1 479-497 | 9 | 0 |
| deposits with any rejected residue | - | 51 of 69 |
| deposits below 90% verified | - | 1 (6S2K, 0.000) |
The eight bleximenib-series deposits 9WKU, 9WKV, 9WKW, 9WKX, 9WN9, 9WNA, 9WNI and 9WNJ each reject 64-66 residues over the range 458-489; 9C92, 9C93 and 9C94 carry a 40-residue expression tag numbered -17 to 2 2.
This is the same defect class as item 4 of the brief's "Four ways the PDB will give you a confident wrong answer", one level deeper. That item warns about a constant offset between a paper's numbering and UniProt's. This is a piecewise offset inside a single chain, which no single readback position can detect: 9WKU reads back correctly at residues 20, 50, ... 440 and lies from 458 onward.
It also bounds the sibling analysis. analyses/q34-menin-surface-geometry/run.py verifies numbering inside its contact routine but not inside its coverage routine, so its per-residue counts over 371-400 carry the same exposure. Re-measured here with verification, they do not move - 389-397 is observed in 0 of 69 either way, because none of the mis-numbered deposits happens to fake coverage there. The Q34 numbers survive; the method that produced them would not survive a different window.
The parse, with its boundaries and their uncertainty stated separately
| lobe | residues by contact clustering | the field's name | boundary confidence |
|---|---|---|---|
| 1 | 2-29, 32-33, 36-90, 239-312 (163 res) | NTD ("heel") and palm together | - |
| 2 | 91-138, 145-216, 221-232 (143 res) | thumb | - |
| 3 | 315-386, 402-459, 520-528, 534-539, 548-581 (186 res) | fingers | - |
| 4 | 596-608 (13 res) | a detached C-terminal helix; NLS-2's core | - |
92.8% of the 2,684 residue-residue contacts in 3U84 fall inside one of these four sets.
The sequence parse that follows, and how far each boundary can be trusted:
| boundary | value | uncertainty | basis |
|---|---|---|---|
| NTD | thumb | 90/91 | +/- 11, and soft in principle | helix 82-101 spans it, so no cut here leaves a helix intact. The clustering puts 82-90 in lobe 1 and 91-101 in lobe 2, i.e. it cuts a helix in half. This boundary is a convention, not a seam. |
| thumb | palm | 232/233 | +/- 7 | lobe 2 runs to 232 with stragglers at 234-235 and 238; lobe 1 starts at 233 and 236-237 and becomes solid at 239. Helix 231-242 spans the boundary. |
| palm | fingers | 317/318 | +/- 3 | the deepest cut in the protein, in the four-residue loop between helix 297-313 and helix 318-331. Second-best cut is 331, third-best in that neighbourhood is 360. |
| fingers | C-term | none | - | the fingers run to the end of the modelled chain; 596-608 detaches in 3U84 but is the same sequence block. |
So: NTD 1-90, thumb 91-232, palm 233-317, fingers 318-610. One of those four boundaries is measured (317/318), one is reasonable (232/233), one is a convention inside a helix (90/91), and the fourth does not exist.
And the honest negative the brief asked for: the four-name language does not survive the parse. Menin is one compact globular domain, radius of gyration 26.3 A, and the NTD and the palm are a single spatial lobe. The correct statement is that menin has three structural lobes, of which one is described in the literature as two.
Where the drug pocket sits on the axis, and why that is the point
Menin residues within 4.5 A of the ligand, per chain pair, measured here:
| ligand | deposit | n menin residues | span | lobe 1 | lobe 2 | lobe 3 |
|---|---|---|---|---|---|---|
| revumenib (OQ4) | 7UJ4 | 23 | 155-371 | 5 | 8 | 10 |
| ziftomenib (K5O) | 8VA6 | 26 | 155-371 | 6 | 8 | 12 |
| KMT2A MBM1 peptide | 4GQ6 | 29 | 135-363 | 10 | 14 | 5 |
The pocket is not in a domain. It is the seam between all three lobes, and the deepest structural boundary in menin - after residue 317 - runs through it, with 319, 322, 323, 325, 326, 329, 330, 341, 363, 366, 367 and 371 on the fingers side and 135-155, 177-182, 238-249 and 276-285 on the other.
Two measurements follow that this graph did not have:
- Revumenib and the KMT2A MBM1 peptide share only 15 of the 37 menin residues in their union - Jaccard 0.405. Ziftomenib against MBM1 is 0.410. Eight residues are revumenib-only (276, 285, 325, 326, 341, 366, 367, 371) and fourteen are peptide-only (135-138, 153, 154, 244, 246-249, 279, 282, 359).
- The drugs lean into the fingers and the peptide does not. 43.5% of revumenib's and 46.2% of ziftomenib's footprint is in lobe 3, against 17.2% of the MBM1 peptide's.
The second of those is the one with a consequence. The fingers lobe is where the SvID (360-445, entirely lobe 3), the gamma-H2A.X motif (371-400, entirely lobe 3) and the nucleosome face all live. The clinical compounds occupy more of that lobe than the interaction they were designed to block does, which is a structural reason - not merely an epidemiological one - to expect menin-inhibitor effects that are not KMT2A-displacement effects.
What 69 deposits cannot see
83 of menin's 610 residues (13.6%) are observed in no deposit at all: 389-397, 462-519, 530-533, 540-543, 590-595 and 609-610 2. The 58-residue run 462-519 is the loop Huang et al. deleted to crystallise the protein ("we genetically deleted an unstructured loop (resides 460-519) in menin", their Methods) 1, and it contains NLS-1 entirely.
450 residues are observed in at least 60 of 69 deposits, in four runs: 2-53, 74-385, 402-457 and 552-581.
One correction to an existing entry falls straight out of this. interface-menin-nls1-479-497-and-nls2-588-608 states in data.structures_absent that "no menin deposit models past residue 587 (8GPN is the maximum); NLS-2 at 588-608 is outside every coordinate set", and its title says both signals are "outside every structure ever solved". 3U84 models menin 596-608, thirteen of NLS-2's twenty-one residues including the KRQRK at 604-608 that the entry itself nominates as a monopartite candidate, and 3U84's _struct_conf calls 597-608 a helix. Verified residue-for-residue against O00255 here 2. Twenty-nine further deposits model residue 588 and five model 588-589; 8GPN's maximum is 587, so that clause is right about 8GPN and wrong about the deposit set. The entry's NLS-1 claim is correct and this beat's first attempt to refute it was the instrument error described above.
| script | analyses/q36-menin-residue-axis/run.py |
|---|---|
| status | run |
| result summary | Three spatial lobes, not four named ones; NTD and palm are one lobe. Deepest boundary after residue 317. Proposed parse NTD 1-90, thumb 91-232, palm 233-317, fingers 318-610. The drug pocket straddles all three lobes and overlaps the KMT2A MBM1 footprint at Jaccard 0.405. |
| figure | |
| uniprot | O00255 |
| length AA | 610 |
| reference deposit | 3U84 |
| n PDB deposits swept | 69 |
| n deposits usable after numbering verification | 68 |
| domains method | Contact-graph parse of PDB 3U84, 5 A heavy-atom, contacts closer than 4 in sequence excluded. Boundaries from unconstrained spectral clustering cross-checked against a sequence-contiguous minimum-cut dynamic program with a 2000-draw random-partition null. NOT read off any publication. |
| fraction of contacts internal to a lobe | 0.928 |
| supersedes | gene-men1 |
| supersedes note | Supersedes gene-men1 data.domains, which is labelled in its own `domains_provenance` as binding regions and annotations and NOT a structural domain parse. The replacement array for the four structural domains is `data.domains` above; the seven binding-region entries currently in gene-men1 should be MOVED to a separate key rather than deleted, because they are correct and are a different kind of object. This entry does not edit gene-men1. |
| shown for fusion | NO for the parse itself - a domain parse is a property of the protein, not of a fusion, and menin is not part of any fusion in this graph. The pocket-footprint comparison is shown for KMT2A::AFF1 only indirectly: 4GQ6 models the KMT2A MBM1 peptide, residues 4-15, which is retained in every KMT2A fusion including KMT2A::AFF1, but no structure of menin with any fusion protein exists. |
| absence class | measured-not-analysed |
inputs
[ "UniProt O00255 (fetched live, primary gene name and length asserted)", "all 69 RCSB deposits whose polymer entity references O00255", "7UJ4 ligand OQ4 (revumenib), 8VA6 ligand K5O (ziftomenib), 4GQ6 entity 2 (KMT2A MBM1 peptide)" ]
domains — the numbers behind the chart
[
{
"name": "NTD (N-terminal domain, \"heel\")",
"start": 1,
"end": 90
},
{
"name": "Thumb (transglutaminase-like domain)",
"start": 91,
"end": 232
},
{
"name": "Palm (helical, TPR-containing)",
"start": 233,
"end": 317
},
{
"name": "Fingers (C-terminal domain)",
"start": 318,
"end": 610
}
]domains uncertainty
{
"NTD|thumb 90/91": "+/- 11 and soft in principle - helix 82-101 spans it, so this boundary necessarily cuts a helix",
"thumb|palm 232/233": "+/- 7 - helix 231-242 spans it; lobe membership is mixed over 221-238",
"palm|fingers 317/318": "+/- 3 - the deepest cut in the protein, in the loop between helix 297-313 and helix 318-331",
"fingers C-terminal end": "not a boundary; the fingers run to the modelled end of the chain"
}spatial lobes measured — the numbers behind the chart
[
{
"lobe": 1,
"n_residues": 163,
"runs": [
[
2,
29
],
[
32,
33
],
[
36,
90
],
[
239,
298
],
[
300,
305
],
[
307,
312
]
],
"field_name": "NTD and palm, together"
},
{
"lobe": 2,
"n_residues": 143,
"runs": [
[
91,
138
],
[
145,
216
],
[
221,
223
],
[
225,
232
]
],
"field_name": "thumb"
},
{
"lobe": 3,
"n_residues": 186,
"runs": [
[
217,
220
],
[
315,
386
],
[
402,
459
],
[
520,
528
],
[
534,
539
],
[
548,
581
]
],
"field_name": "fingers"
},
{
"lobe": 4,
"n_residues": 13,
"runs": [
[
596,
608
]
],
"field_name": "detached C-terminal helix; NLS-2 core"
}
]deepest single boundary — the numbers behind the chart
{
"after_residue": 317,
"crossing_contacts": 64,
"normalised_score": 6.719,
"median_normalised_over_all_cuts": 14.207,
"random_contiguous_bipartition_median_crossings": 109,
"n_null_draws": 2000,
"seed": 20260922
}secondary structure 3u84
{
"helices": [
[
4,
9
],
[
15,
28
],
[
33,
49
],
[
82,
101
],
[
114,
129
],
[
142,
149
],
[
153,
167
],
[
187,
191
],
[
203,
207
],
[
211,
217
],
[
219,
226
],
[
231,
242
],
[
253,
270
],
[
276,
290
],
[
297,
313
],
[
318,
331
],
[
333,
349
],
[
354,
356
],
[
357,
370
],
[
370,
385
],
[
402,
405
],
[
406,
425
],
[
433,
446
],
[
448,
453
],
[
555,
561
],
[
561,
567
],
[
571,
579
],
[
597,
608
]
],
"strands": [
[
63,
67
],
[
75,
79
],
[
174,
177
],
[
182,
186
],
[
192,
194
],
[
228,
229
]
]
}never observed in any deposit
{
"n_residues": 83,
"runs": [
[
389,
397
],
[
462,
519
],
[
530,
533
],
[
540,
543
],
[
590,
595
],
[
609,
610
]
]
}observed in at least 60 of 69
{
"n_residues": 450,
"runs": [
[
2,
53
],
[
74,
385
],
[
402,
457
],
[
552,
581
]
]
}deposits with non uniprot numbering
{
"6S2K": "verified fraction 0.000 - the whole chain is renumbered; excluded",
"9WKU/9WKV/9WKW/9WKX/9WN9/9WNA/9WNI/9WNJ": "64-66 residues renumbered over 458-489",
"9C92/9C93/9C94": "40-residue expression tag numbered -17 to 2"
}pocket footprints 4.5A
{
"revumenib_7UJ4_OQ4": [
155,
177,
178,
179,
180,
181,
182,
238,
241,
242,
276,
278,
285,
319,
322,
323,
325,
326,
341,
363,
366,
367,
371
],
"ziftomenib_8VA6_K5O": [
155,
177,
178,
179,
180,
181,
182,
238,
241,
276,
278,
279,
282,
285,
319,
322,
323,
325,
326,
329,
330,
341,
363,
366,
367,
371
],
"kmt2a_mbm1_4GQ6": [
135,
136,
137,
138,
153,
154,
155,
177,
178,
179,
180,
181,
182,
238,
241,
242,
244,
246,
247,
248,
249,
278,
279,
282,
319,
322,
323,
359,
363
],
"jaccard_revumenib_vs_mbm1": 0.405,
"jaccard_ziftomenib_vs_mbm1": 0.41,
"pct_of_footprint_in_fingers_lobe": {
"revumenib": 43.5,
"ziftomenib": 46.2,
"kmt2a_mbm1": 17.2
}
}- If the clinical menin inhibitors occupy 43-46% of their footprint in the same lobe that carries the SvID and the gamma-H2A.X motif, then some of the class's on-target effects are effects on surfaces the KMT2A displacement rationale never named. Escalating dose or residence time to deepen KMT2A displacement escalates those too.
- A parse is a design tool, and this one is from a single crystal form of a loop-deleted construct. Designing a partner-selective menin ligand against boundaries whose largest uncertainty is +/- 11 residues, at a boundary that cuts a helix, will produce a compound whose selectivity argument rests on a convention.
- Menin is a single compact domain with no separable module. A degrader or a truncation-based tool cannot remove one function and leave the others, which is the usual escape route when a scaffold protein turns out to have more jobs than the programme accounted for.
- Does the palm|fingers seam after residue 317 move when menin is on a nucleosome? 8GPN models to 587 and the same parse could be run on it; if the seam closes or shifts, the drug pocket's three-lobe geometry is a property of the free protein only.
- Is there a conformational reason the two clinical compounds reach further into the fingers lobe than the KMT2A peptide does, or is it just that a small rigid molecule can occupy a subpocket a peptide backbone cannot? A shape-complementarity calculation on the same three deposits would separate these.
- Residues 462-519 are modelled in no deposit and contain NLS-1. Does the predicted structure (AF-O00255-F1) place them anywhere reproducible, and if so with what pLDDT? This analysis deliberately used only experimental coordinates and so cannot say.
- Does the transglutaminase-like assignment of the thumb (Huang et al.'s fold-recognition claim, untested here) survive a modern structure search, and if the thumb is a degenerate transglutaminase, is the catalytic triad position inside or outside the drug pocket?
- E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.paper
The founding structural description of menin as four associated domains - an NTD with a long beta-hairpin, a transglutaminase-like thumb, a helical palm with three TPR motifs and a C-terminal fingers domain - gives no residue boundaries in its main text or figure legends, deferring them to a supplementary figure and supplementary text; the same paper records that an unstructured loop, residues 460-519, was genetically deleted to obtain the crystals.
The same pocket in menin binds both MLL and JUND but has opposite effects on transcription. · Huang J, Gurung B, Wan B, Matkar S, Veniaminova NA, Wan K, et al. · Nature 2012What this evidence cannot show
Full text read here through the PMC HTML route (45,775 characters after tag-stripping) because `fullTextXML` returned HTTP 500 for PMC3983792. The supplementary material was NOT retrieved and is not cited. The absence of numbers is therefore bounded to the main text, figure legends and Methods of the article body - the boundaries may well be stated in Supplementary Fig. 4, which is exactly the problem, because nobody in this graph can read it.
Evidence that argues against this (1)
- A published table of numeric MEN1 domain coordinates does exist, described as crystal-structure-identified, so the claim is about retrievability rather than about whether anyone ever wrote numbers down. Its rendering is corrupt and its isoform frame is internally inconsistent - see E4 - but a reader with the print edition may have usable boundaries this analysis did not. Nelakurti DD et al. 2020
- E2strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.dataset
Across all 69 O00255 PDB deposits with per-residue numbering verified against the UniProt sequence, 83 of menin's 610 residues are observed in no deposit; a 5 A contact graph on the best-covered deposit 3U84 (505 verified residues) clusters into three substantial spatial lobes plus a detached C-terminal helix with 92.8% of contacts internal, the NTD and palm falling in one lobe; the deepest sequence-contiguous boundary is after residue 317, cutting 64 contacts against a random-partition median of 109; and the revumenib and ziftomenib footprints share only 40.5% and 41.0% of their union with the KMT2A MBM1 peptide footprint while placing 43.5% and 46.2% of their contacts in the fingers lobe against the peptide's 17.2%.
analyses/q36-menin-residue-axis/run.py - contact-graph domain parse, solvent accessibility and ligand footprints over all 69 RCSB deposits referencing UniProt O00255, run 2026-09-22 · RCSB PDB and UniProt, computed 2026What this evidence cannot show
`strong`, not `established`, and the reasons are structural rather than statistical. (1) The parse is of ONE crystal form of a construct missing residues 460-519; a different conformer could move a boundary. (2) A contact-graph cut is a statement about packing, not about folding independence - no thermodynamic or evolutionary criterion was applied. (3) The 40-residue minimum block size in the contiguous parse is a choice, and the k=4 contiguous solution ([2-317], [318-439], [440-552], [553-608]) is NOT the four named domains; its last two blocks are the sparsely-modelled C-terminal half and the program is exploiting that sparsity, which is why the spectral parse is the one reported. (4) The NTD|thumb boundary cuts helix 82-101 in half and should be read as a convention. (5) Solvent accessibility is computed on the isolated chain with no partners bound. (6) Deposits are not independent: 27 of the 69 share a construct and many are the same crystal form with different ligands, so 'observed in n of 69' is a statement about the deposit set, not about n independent experiments.
Evidence that argues against this (1)
- A cryo-EM structure of menin on a nucleosome exists and is a different conformational state from the crystal form parsed here; if menin's lobes reorient on chromatin, a parse built from 3U84 describes the free protein and may not describe the chromatin-bound one. That deposit, 8GPN, models to residue 587 but is not the best-covered deposit and was not used as the reference frame. Lin J et al. 2023
- E3established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.paper
The 2026 paper that maps the menin-gamma-H2A.X contact describes the mapped region qualitatively as lying in the Palm and Fingers domains and locates its truncation constructs in a supplementary figure, giving as its only numeric coordinates the 371-400 motif itself, the Pep-MH peptide covering 371-400 and the Pep242 peptide covering 231-248.
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 2026What this evidence cannot show
Full text read here (96,530 characters from Europe PMC `fullTextXML` for PMC13458390). The supplementary figures S2M and S2N that contain the truncation construct boundaries were not retrieved, so what the authors' Palm and Fingers constructs actually spanned is unknown. Their system is A549 lung adenocarcinoma and Men1-knockout mouse embryonic fibroblasts, not a KMT2A-rearranged haematopoietic cell, and nothing in the paper is a leukaemia experiment.
Evidence that argues against this (1)
- That paper's own domain language is inherited, not measured: it cites the nucleosome cryo-EM paper for 'menin binds to nucleosomes through its Palm and Fingers domains', so both papers use a vocabulary whose boundaries neither of them states. A reader who takes 'Palm and Fingers' as a coordinate has been handed a name twice and a number never. Lin J et al. 2023
- E4moderate confidence 3 of 5: One strong study, or several smaller consistent ones.review
A 2020 review tabulates numeric coordinates for the NTD, thumb, palm and fingers as crystal-structure-identified domains, but the served text of that table is corrupt - the cells read 1-100, 101-1230, 231-1300, 301-1305, 479-1497, 588-1608 and 219-1395 - and the numbering frame is internally inconsistent between the 610-residue and 615-residue isoforms.
Comprehensive Analysis of MEN1 Mutations and Their Role in Cancer. · Nelakurti DD, Pappula AL, Rajasekaran S, Miles WO, Petreaca RC · Cancers 2020What this evidence cannot show
`moderate` because the source cannot be read as intended. The corruption was confirmed at the byte level - the Europe PMC `fullTextXML` for PMC7565326 serves the literal bytes `101\xe2\x80\x931230`, a valid UTF-8 en dash followed by `1230` - so this is not a decoding fault at this end. The publisher's own HTML at mdpi.com returned HTTP 403 and the PMC HTML page returned a 20,406-character bot-detection stub, so the printed table was never seen. The decoding rule (a spurious `1` follows the dash) is confirmed on three rows whose true values are independently known and FAILS on the Fingers row, which is the row this beat most wanted. Nothing in this analysis's parse depends on this citation.
Evidence that argues against this (1)
- The same review's own body text places the palm|fingers boundary elsewhere than its table does - it says the P325L mutation 'sits right at the boundary of the palm and fingers domains' and notes that P325 in its numbering is P320 in the 610-residue isoform, i.e. a boundary near 320 rather than near 300. The internal disagreement is the reason this is evidence about the state of the literature and not evidence about menin. Biancaniello C et al. 2022
- E5moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper
Menin's four-domain description is used with a fifth name in at least one source, which calls the N-terminal domain the heel, and maps isoform-specific insertions and deletions onto the thumb and palm without giving those domains numeric boundaries either.
Alternative splicing generates isoform diversity in MEN1. · Ramachandran A, Le Quesne Stabej P, Boyle V, Elston MS, Pattison S, Lawrence B, et al. · Endocrine Oncology 2024What this evidence cannot show
Bibliographic fields taken from a PubMed esummary fetched in this session and the DOI cross-checked against `efetch_doi()`, which reads only the article's own ArticleIdList. The substantive point is a vocabulary observation, not a measurement: menin's N-terminal domain is called the NTD by Huang et al. and the heel here, so a beat searching on one name will miss the other. The isoform mapping in that paper is a prediction onto a crystal structure, not a new structure.
Evidence that argues against this (1)
- A naming variant in one paper is not evidence that the field is divided; 'heel' may simply be that group's usage, and no count of how often each term is used was made here. Huang J et al. 2012
supplies the structural residue axis gene-men1's data.domains explicitly says it does not have
re-runs the coverage sweep chain-wide with per-residue numbering verification; the 371-400 counts agree
all 71 observed SvID residues fall in one spatial lobe (the fingers)
all 16 observed residues of the gamma-H2A.X motif fall in the fingers lobe
places E366/D370/V371 on the fingers side of the deepest seam in menin, not in the palm
3U84 models menin 596-608 as a helix, so NLS-2 is NOT outside every coordinate set; the NLS-1 claim stands
8GPN is a different conformer and models to residue 587; the parse here is of the free protein
the KMT2A MBM1 footprint is 29 menin residues, 17.2% of them in the fingers lobe
Pep242 covers menin 231-248, which this parse places at the thumb-palm boundary rather than inside either
lobe assignment of every pocket residue comes from that parse
the lobe assignment and the accessibility numbers come from that parse
lobe composition of the 1-228 region comes from that parse
supplies the lobe decomposition of every pocket residue