Oncofusion

start / graph / gene-luzp1

Geneweak confidence 2 of 5: Preliminary, small, indirect, or not yet peer reviewed.Q90-pan-fusion-core3

LUZP1 / fimbacin (Q86V48) - the weakest index-fusion call of the nine, and the strongest non-index call: p = 0.127 against MLL-AF4 and 2.6e-10 against MLL-ENL

also called LUZP1 · fimbacin · Leucine zipper protein 1 · Filamin mechanobinding actin cross-linking protein · LUZP1_HUMAN · Q86V48

LUZP1 is a coiled-coil protein that cross-links actin filaments and sits at the base of the cell's antenna, the primary cilium. In the MLL fishing experiment it scored worse against the index fusion than any other protein in this batch - and better against a different MLL fusion than almost anything in the whole shared set, which is the clearest single demonstration that these scores are partly about the bait and not the prey.

The same thing, for a scientist

LUZP1 (Q86V48, 1,076 aa) is a leucine-zipper actin cross-linking protein that oligomerises through an N-terminal coiled-coil, binds the mechanosensing repeat 21 of filamin A only when its cryptic site is exposed, and localises to stress fibres, the centrosome, the cilium basal body, the midbody and the inner centromere. It co-purified with all seven MLL fusions in Skucha 2018, and its two numbers are the most informative pair in this tranche: **MLL-AF4 p = 0.127 with 6 spectra - rank 39 of 42, the weakest index-fusion call of the nine - and MLL-ENL p = 2.63e-10 with 69 spectra.** That is eight orders of magnitude between two baits for one prey, and it is the cleanest available demonstration of the bait-depth asymmetry this beat measured across the whole tranche. One further measurement: **LIMA1/EPLIN, LUZP1's own named direct interacting partner, IS in the 960 (n = 2)** - LUZP1 is the only protein of the nine whose named partner is present at all - though not in the MLL-AF4 column and only in two baits.

Go deeper
The Skucha row, stated in full

7 of 7 fusions. MLL-AF1p 0.0465 (4|3), MLL-AF4 0.127 (4|2), MLL-AF9 0.000318 (15|12), MLL-CBP 0.0384 (2|21), MLL-EEN 0.00263 (17|12), MLL-ENL 2.63e-10 (38|31), MLL-GAS7 0.00402 (12|12); negative control 0|0 1. Rank 39 of 42 by MLL-AF4 p, and the only rows below it are NOLC1 (0.134) and SMC3 (0.174), both of which already have entries here.

The eight-order-of-magnitude spread is the point. Same protein, same lab, same preparation, two baits: 0.127 with 6 spectra against MLL-AF4, 2.63e-10 with 69 spectra against MLL-ENL. Nothing about LUZP1 changed between those two columns. This is the single clearest case in the tranche that a weak index-fusion p-value is a statement about how deeply MLL-AF4 was purified, not about how strongly the prey associates.

Why the p > 0.05 deferral does not survive contact with the corpus

LUZP1 and DHX16 were deferred twice for exceeding p = 0.05 in the index column. Measured on 2026-09-21:

pan-fusion proteinMLL-AF4 pentryconfidence
SMC30.174gene-smc3moderate
NOLC10.134gene-nolc1weak
TRIM280.129gene-trim28weak
LUZP10.127deferred twice-
DHX160.0929deferred twice-

TRIM28, at 0.129, is worse than LUZP1 at 0.127 and is already written at weak. The Methods' selection rule was a rank cutoff, not a p threshold, and 63.9% of the MLL-AF4 column exceeds 0.05. The deferral was a judgement and the measurement does not support it 1.

What LUZP1 is, and the one partner that is present

LUZP1 depletion, like depletion of its interacting partner EPLIN, increases MyosinVa at the centrosome and increases primary cilium formation; LUZP1 localises to both actin filaments and the centrosome/basal body and is an actin-stabilising protein that mobilises ARP2 to centrosomes 2. Biochemically it is fimbacin: it does not bind canonical full-length filamin A, but binds filamin A repeat 21 once the cryptic integrin-binding site is exposed, it cross-links actin filaments itself through a site at residues 400-500, and it oligomerises as an estimated octamer through an N-terminal predicted coiled-coil 3. LUZP1 loss also contributes to Townes-Brocks syndrome.

Measured against the full 960-row table on 2026-09-21: LIMA1 (EPLIN) is present at n = 2 with a clean 0|0 control and no MLL-AF4 value; FLNA is at n = 1; ACTR2, ACTR3 and ARPC2 are at n = 1-2; LUZP2, MYO5A and WASL are absent. So LUZP1 is the only one of the nine whose named direct partner appears in the network at all - which is worth recording precisely because it is the kind of corroboration the other eight lack, and worth discounting because n = 2 with no index-fusion value is close to no corroboration.

The coiled-coil note, stated as an observation

LUZP1 oligomerises through an N-terminal coiled-coil, as does MAPRE1 - and a coiled-coil four-helix bundle is exactly what MAPRE1 contributes to the MLL-EB1 fusion. Coiled-coil proteins are known to behave awkwardly in affinity purifications: they are elongated, they self-associate, and they co-sediment. This entry records that as a shared property of two of the nine and does NOT build an argument on it, because no null was computed - the fraction of the 960, or of any prey list, that contains a coiled-coil is not known here, and reporting a tally without that fraction would be exactly the error rule 84 exists to prevent.

Verdict

Probably contamination, and the deferral was not justified on the stated ground. Against the interaction: a cytoskeletal, centrosomal, stress-fibre protein with no human experimental nuclear annotation (the 'Nucleus' line is ECO:0000250 from mouse Q9ESV1), the weakest index-fusion call of the nine, and no independent tie to any KMT2A fusion. For: a genuinely clean negative control, presence of its named partner in the network, and an MLL-ENL row at 2.63e-10 that is far too strong to be dismissed as noise - something is being recovered, even if what it is recovered by is a bait property. The p > 0.05 objection specifically is not the right reason to have deferred it, and this entry is written at the same weak tier the corpus already uses for TRIM28 at a worse p-value.

Facts and figures
uniprotQ86V48
length AA1076
accession resolutionResolved live 2026-09-21: `gene_exact:LUZP1 AND organism_id:9606 AND reviewed:true` returns exactly ONE reviewed row; gene_primary LUZP1, Q86V48, entry name LUZP1_HUMAN, 1,076 aa, protein name 'Leucine zipper protein 1 (Filamin mechanobinding actin cross-linking protein) (Fimbacin)', no gene synonyms. Matches the accession in Skucha's own table.
identifier hazardNOT IN data/symbol-collisions.json AS OF 2026-09-21 (registry read before searching, per rule 88). Two mild hazards. (1) `fimbacin` is a 2019 coinage that most of the LUZP1 literature does not use, so the biochemistry and the cell-biology literatures are partly disjoint by name - `LUZP1[tiab]` returns 29 records and the fimbacin work is reachable from the symbol, so no split was found here, but a fimbacin-only search would miss almost everything. (2) LUZP2 is a different gene and is absent from the Skucha 960; the two must not be merged. Rule 65 readback SUCCEEDS.
localizationCYTOPLASM, CYTOSKELETON, CENTROSOME AND CENTROMERE - all experimental - WITH A BY-SIMILARITY NUCLEUS. UniProt Q86V48, fetched live 2026-09-21 with per-location evidence codes read individually: centrosome ECO:0000269 PubMed:26638075, 32496561, 32553112; cilium basal body ECO:0000269 PubMed:32496561; midbody ECO:0000269 PubMed:32496561, 32553112; 'Chromosome, centromere' ECO:0000269 PubMed:38009294; spindle ECO:0000269 PubMed:38009294; stress fibre ECO:0000269 PubMed:30990684, 32553112, 38832964. 'Nucleus' is ECO:0000250 by similarity to MOUSE Q9ESV1, as are dendrite and perikaryon; tight junction is ECO:0000250 from Q8R4U7. So there are EIGHT experimental cytoplasmic/cytoskeletal citations and ZERO human experimental nuclear ones. Per rule 91 the by-similarity lines were read rather than discarded; the nuclear one is the only inferred compartment that matters here and it is not a measurement.
subnuclear localizationNOT APPLICABLE for the interphase nucleus - there is no human experimental nuclear annotation, only an ECO:0000250 inference from mouse. Recorded as not applicable rather than as an unmeasured absence, following the HLA-A / NRAS / B2M / PROM1 / CD33 / ELOVL1 precedent, so it does not enter the denominator of unmeasured subnuclear compartments. ONE GENUINE CHROMOSOMAL ASSOCIATION IS RECORDED AND IS NOT INTERPHASE: LUZP1 localises to the INNER CENTROMERE in metaphase and to the spindle (ECO:0000269 PubMed:38009294). That is a mitotic, chromosome-associated address in cells whose nuclear envelope has broken down, and it is a plausible route by which a cytoskeletal protein could contaminate an asynchronous nuclear preparation - which is a hazard for this whole tranche and is noted here because LUZP1 is where it is documented.
localization shown for fusionNO - nobody has imaged or fractionated LUZP1 in any cell expressing any KMT2A fusion.
shown for fusionCo-purification with all seven MLL fusions, but the index-fusion call is p = 0.127, above the conventional line and rank 39 of 42, while MLL-ENL gives 2.63e-10; shRNA-screened in MLL-AF9 MOLM-13, score unpublished. NO independent experiment ties LUZP1 to any KMT2A fusion.
selectivityUNKNOWN, and BARRED from any target list. Not named among the paper's controls and not known to be among the 40 re-screened. LUZP1 loss contributes to Townes-Brocks syndrome, a developmental disorder, so it is a gene whose loss has organismal consequence; and this entry's own verdict on the interaction is that it is probably an artefact.
absence classnever-measured
absence class noteNo instrument has been pointed at LUZP1 in a KMT2A-rearranged cell outside the two screen hosts, and there is no human experimental measurement of a nuclear LUZP1 pool in any cell. The MOLM-13 shRNA score is measured-not-reported. PRIDE checked: PXD009338 is the only relevant deposition.
graph contextLUZP1 appears in ZERO of this graph's 1,924 node files before this entry.
verdictPROBABLY CONTAMINATION, AND THE DEFERRAL WAS NOT JUSTIFIED ON THE STATED GROUND. p > 0.05 is not a criterion this corpus applies: TRIM28 at 0.129 is worse and is written at 'weak'. On the merits, the case against is strong - eight experimental cytoskeletal localisations and no human experimental nuclear one, an elongated self-oligomerising actin cross-linker, a documented mitotic chromosome association that offers a carryover route in asynchronous culture, and no independent KMT2A tie. The case for is the MLL-ENL row at 2.63e-10 with 69 spectra, which is far too strong to be noise, and the presence of its named partner EPLIN in the network.
skucha 2018
{
  "bait": "MLL-AF4 (= KMT2A::AFF1)",
  "p_value": 0.127,
  "above_conventional_threshold": true,
  "spectral_counts": "4|2",
  "n_fusions_of_seven": 7,
  "negative_control_counts": "0|0",
  "per_bait": {
    "MLL-AF1p": "0.0465 (4|3)",
    "MLL-AF4": "0.127 (4|2)",
    "MLL-AF9": "0.000318 (15|12)",
    "MLL-CBP": "0.0384 (2|21)",
    "MLL-EEN": "0.00263 (17|12)",
    "MLL-ENL": "2.63e-10 (38|31)",
    "MLL-GAS7": "0.00402 (12|12)"
  },
  "af4_spectral_rank_of_seven": 7,
  "af4_p_rank_within_the_42_pan_fusion": 39,
  "bait_spread": "EIGHT ORDERS OF MAGNITUDE for one prey: MLL-AF4 0.127 with 6 spectra, MLL-ENL 2.63e-10 with 69. The largest spread in this tranche and the clearest single demonstration that index-column weakness is a bait property.",
  "written_precedent_at_worse_p": "TRIM28 0.129 (gene-trim28, weak), NOLC1 0.134 (gene-nolc1, weak), SMC3 0.174 (gene-smc3, moderate) - all three already in this graph, and TRIM28's is worse than this row's. Measured 2026-09-21 by reading each entry's data.skucha_2018 block.",
  "source": "analyses/skucha-mll-fusion-interactome/results.json, re-derived from the cached MOESM4 xlsx 2026-09-21; run.py re-run, both controls PASS"
}
complex membership
{
  "complex": "actin cross-linking / centrosome-basal body (LUZP1 + EPLIN/LIMA1 + filamin A)",
  "partners_in_the_960": {
    "LIMA1 (EPLIN)": "n=2, NO MLL-AF4 value, neg 0|0 - LUZP1's named direct partner, and the ONLY named direct partner of any protein in this tranche that is present in the network",
    "FLNA": "n=1, no MLL-AF4 value, neg 0|1",
    "ACTR2 / ACTR3 / ARPC2 (ARP2/3)": "n=1-2, no MLL-AF4 values, clean controls",
    "ACTB": "n=7 - in this same tranche"
  },
  "absent_from_the_960": [
    "LUZP2",
    "MYO5A",
    "WASL",
    "SALL1",
    "ACTL6A",
    "CFL1",
    "PFN1",
    "GSN",
    "CORO1A"
  ],
  "reading": "THE ONLY ONE OF THE NINE WITH ITS NAMED PARTNER PRESENT - and the corroboration is thin: EPLIN at n = 2 with no index-fusion value. The ARP2/3 subunits at n = 1-2 point the same weak way. No cytoskeletal module was tested in analyses/mll-fusion-interactome-complexes/, so none of this has been tested against a background and it is an observation, not an enrichment claim (rule 84)."
}
cell types and states
[
  "Jurkat (human T-ALL) - the AP-MS host, nuclear lysate, tagged single-copy transgene, ASYNCHRONOUS culture",
  "MOLM-13 (human MLL-AF9 AML) - shRNA screen host, six shRNAs, per-gene score unpublished",
  "human ciliogenesis-competent cultured cells - the LUZP1/EPLIN cilia work",
  "in vitro reconstitution and tissue culture overexpression - the fimbacin biochemistry",
  "no B-lineage cell, no infant cell, and no KMT2A::AFF1 cell of any kind"
]
functionally screened in the source paper
{
  "screened": true,
  "shrnas_for_this_gene": 6,
  "design": "Supplementary Table 6 / MOESM5 is the shRNA library for the negative-selection screen: 768 data rows, 128 unique gene symbols, EXACTLY 6 shRNAs each - counted with openpyxl by this beat on 2026-09-21. Host is MLL-AF9-expressing MOLM-13, a human myeloid line.",
  "set_identity_measured_by_this_beat": "The 128 symbols in the shRNA library are the SAME SET as the 128 rows of MOESM4 with n_fusions >= 5, checked by set difference on 2026-09-21: the only four mismatches are alias spellings (JADE2/PHF15, JADE3/PHF16, KMT2A/MLL, NIFK/MKI67IP). This matters for the contamination question. The paper says 'Seven proteins were manually removed as these were either frequently observed contaminants or were not detected in human hematopoietic cell lines. The final set was comprised of 128 proteins.' Because the table's >=5 set is already exactly 128, those seven are NOT recoverable from Supplementary Table 5 - and every protein in this tranche is in the post-removal 128 and was carried into the functional screen.",
  "what_this_does_NOT_establish": "A per-gene result. Scores are presented only as heatmaps (Fig. 2c/2d); no per-gene depletion value is tabulated anywhere in the paper or its supplementary files, so for any individual gene the outcome is measured-not-reported. It is also MLL-AF9 MOLM-13, a myeloid line, not the index fusion and not B-lineage.",
  "the_filter_is_leaky_and_here_is_the_proof": "'Survived the authors' manual contaminant removal' is weaker than it sounds. CCT3 is also in the 128 and was also screened, and the CCT/TRiC chaperonin is the canonical AP-MS contaminant - the companion analysis analyses/mll-fusion-interactome-complexes/ uses it as its NEGATIVE control and it is still significant against a nuclear background (q = 2.7e-05, 8 of 9 subunits in the MLL-AF4 column). The authors' own named essentiality controls were RFC1, SF3A3 and CCT3. So the manual removal did not remove a canonical contaminant complex, and membership in the 128 is not the authors certifying a protein as a real partner.",
  "absence_class_for_the_per_gene_score": "measured-not-reported",
  "library_symbol": "LUZP1"
}
bounded literature
{
  "query": "LUZP1[tiab] AND (KMT2A[tiab] OR MLL[tiab] OR \"MLL-AF4\"[tiab] OR \"MLL-AF9\"[tiab] OR \"t(4;11)\"[tiab])",
  "querytranslation": "\"LUZP1\"[Title/Abstract] AND (\"KMT2A\"[Title/Abstract] OR \"MLL\"[Title/Abstract] OR \"MLL-AF4\"[Title/Abstract] OR \"MLL-AF9\"[Title/Abstract] OR \"t 4 11\"[Title/Abstract])",
  "count": 0,
  "date": "2026-09-21",
  "tool": "NCBI esearch db=pubmed",
  "names_tried": [
    "LUZP1",
    "fimbacin (not run against the KMT2A clause - a 2019 coinage with a handful of records, a residual gap)"
  ],
  "bare_operand_control": "LUZP1[tiab] alone returns 29 records, so the gene clause can return ones.",
  "positive_control": "MEN1[tiab] AND the identical five-term KMT2A clause returns 85.",
  "bound": "Titles and abstracts only; supporting figures not searched (rule 80). Cytogenetic term quoted, querytranslation read back with no injected [UID] term (rule 95). One tag per term (rule 94)."
}
what would settle it
[
  "Ask what fraction of the Jurkat cultures were mitotic. LUZP1 is at the inner centromere and the spindle in metaphase; in an asynchronous nuclear preparation that is a direct route for a cytoskeletal protein into a 'nuclear' lysate, and it applies to MAP7D1 and MAPRE1 too. The paper does not report it.",
  "Retrieve the CRAPome frequency for Q86V48. Free, and it is the external background control the source paper did not run.",
  "Why does MLL-ENL give 69 spectra and MLL-AF4 give 6 for the same prey? MLL-ENL is also the deepest bait for ACTB, VIM and MAP7D1 - the whole cytoskeletal group peaks on one bait. That is a per-bait question the public spectra can answer and nobody has asked."
]
How this could bite us back
  • LUZP1 must not reach a target list. Actin cross-linking and ciliogenesis control have no selective window, LUZP1 loss causes a developmental syndrome, and the interaction is probably not real.
  • The seductive number here is 2.63e-10. It is real and it is against the wrong bait - MLL-ENL, not the index fusion - and this graph's disease is KMT2A::AFF1. An entry that led with that p-value would be quoting the strongest number in the row rather than the relevant one.
  • If the cytoskeletal group does turn out to be mitotic carryover, the same argument removes MAP7D1, MAPRE1 and part of ACTB at once, and it is a single question to the authors rather than an experiment.
Still open
  1. Why do ACTB, VIM, MAP7D1 and LUZP1 all peak on MLL-ENL? Four cytoskeletal preys reaching their maximum spectral depth on the same bait is a pattern about that purification, and the per-bait numbers are all in the published table.
  2. What fraction of the asynchronous Jurkat cultures was mitotic? LUZP1 is an inner-centromere and spindle protein in metaphase; mitotic cells have no nuclear envelope, and this is the most concrete carryover mechanism available for the cytoskeletal half of this tranche. Nobody has asked it of this dataset.
  3. Does LUZP1 have any nuclear pool in a human cell? The nuclear annotation is an ECO:0000250 inference from mouse and has never been tested in human cells.
  4. EPLIN/LIMA1 is in the 960 at n = 2 and is a tumour suppressor. It is not written in this graph. Is it worth an entry, or is it the same artefact as LUZP1 one step removed?
Every source behind this entry (3)
  1. E1weak confidence 2 of 5: Preliminary, small, indirect, or not yet peer reviewed.paper

    LUZP1 co-purified with all seven Strep-HA-tagged MLL fusions from nuclear lysates of isogenic human Jurkat T-ALL cells; for MLL-AF4 (= KMT2A::AFF1) the combined p-value is 0.127 - above the conventional 0.05 line and rank 39 of the 42 pan-fusion proteins - with spectral counts 4|2 and a negative control of 0|0, while for MLL-ENL the same protein gives p = 2.63e-10 with 38|31; it is in the paper's final post-filter set of 128 that entered the MOLM-13 shRNA screen.

    MLL-fusion-driven leukemia requires SETD2 to safeguard genomic integrity. · Skucha A, Ebner J, Schmoellerl J, Roth M, Eder T, Cesar-Razquin A, Stukalov A, Vittori S, Muhar M, Lu B, Aichinger M, Jude J, Mueller AC, Gyorffy B, Vakoc CR, Valent P, Bennett KL, Zuber J, Superti-Furga G, Grebien F · Nature Communications 2018
    What this evidence cannot show

    SYSTEM: the AP-MS host is JURKAT, a human T-ALL line, while KMT2A::AFF1 disease is B-lineage infant leukaemia; a partner requiring a B-cell or infant proteome cannot appear here and a T-lineage partner can appear spuriously. The bait is a Strep-HA-tagged, SINGLE-COPY, doxycycline-induced transgene at an FRT/Flp cassette, not the endogenous fusion. Prey came from bulk nuclear lysate after a single STREP-Tactin step, so co-purification is NOT evidence of a direct contact and is not evidence that the two proteins are ever in the same complex. INCLUSION RULE: the paper kept a fixed number of top-ranked interactions per bait rather than applying a p threshold. Methods, read verbatim from the PMC full text by this beat on 2026-09-21: "All the identified bait-prey pairs were ranked by the combined p-value. The 300 most significant interactions per bait were retained." Measured by this beat from the cached MOESM4 xlsx: within the MLL-AF4 column 186 of 291 listed p-values (63.9%) exceed 0.05, and that column's maximum p is 0.175. BAIT DEPTH: for all nine proteins in this tranche the MLL-AF4 spectral total is rank 7 of the seven baits - measured protein by protein - so a low MLL-AF4 count is a bait property (transgene expression, purification depth, or the GLM normalisation) and must not be read as a weaker association than the same protein's count under another bait. HOW TO READ THE NEGATIVE CONTROL, measured by this beat on 2026-09-21 over all 960 rows of MOESM4: the Spearman correlation between a protein's neg_ctrl spectral total and its maximum per-bait spectral total is +0.461, and the median maximum per-bait spectral count is 42 for the 145 proteins (15.1%) with a non-zero negative control against 8 for the 815 with 0|0. A dirty negative control in this table is therefore substantially a statement about protein ABUNDANCE, not about specificity, and a clean 0|0 is substantially a statement that two control replicates were not deep enough to see the protein at all. Two consequences. (1) PSIP1/LEDGF - the one pan-fusion partner with a solved co-crystal against the KMT2A N-terminus - carries 0|5, the second-dirtiest control of the 42, so a non-zero control cannot be used to call a protein a contaminant. (2) A 0|0 control is not purity; it is an unestimated baseline. The paper's GLM estimates each prey's baseline abundance A0,j from the control purifications, so a prey the controls never saw has its baseline set by a floor rather than by data, which is the direction that inflates apparent specificity. ABOVE THE CONVENTIONAL LINE, AND THAT IS NOT A DISQUALIFIER HERE. This protein's MLL-AF4 p-value is 0.127, above 0.05. Three things make that interpretable rather than fatal. (1) The table is RANK-SELECTED, not threshold-selected - the Methods read 'The 300 most significant interactions per bait were retained', 186 of the 291 listed MLL-AF4 p-values (63.9%) exceed 0.05 and the column's maximum is 0.175 - so 0.05 was never the inclusion criterion and applying it retrospectively imposes a cutoff the experiment did not use. (2) Measured by this beat on 2026-09-21, the three WEAKEST MLL-AF4 calls in the entire pan-fusion 42 - SMC3 0.174, NOLC1 0.134, TRIM28 0.129 - ALL already have entries in this graph, and gene-nolc1 and gene-trim28 carry confidence_overall 'weak' with those exact p-values recorded. TRIM28's 0.129 is WORSE than this protein's 0.127. (3) The index bait is the shallowest of the seven for all nine proteins in this tranche. SPECIFIC TO THIS PROTEIN, measured by this beat from the cached MOESM4 xlsx on 2026-09-21: the spread between the weakest and strongest bait for this one prey is EIGHT ORDERS OF MAGNITUDE (MLL-AF4 0.127, 6 spectra; MLL-ENL 2.63e-10, 69 spectra), the largest in this tranche, and it is the cleanest single demonstration that index-column weakness is a bait property. Four of the seven baits are below 0.005, so unlike DHX16 this is NOT weak everywhere. MODULE: LIMA1/EPLIN, LUZP1's named direct partner, IS present at n = 2 (neg 0|0, no MLL-AF4 value); FLNA n = 1; ACTR2, ACTR3, ARPC2 n = 1-2; LUZP2, MYO5A and WASL absent. LOCALISATION: UniProt Q86V48's 'Nucleus' line is ECO:0000250 by similarity to mouse Q9ESV1 - there is NO human experimental nuclear annotation, while there are eight experimental cytoplasmic/cytoskeletal ones. SELECTIVITY: not named among the paper's controls (RFC1, SF3A3, CCT3 non-selective; MEN1 selective), not known to be among the unpublished 40 re-screened. Recorded as unknown. run.py re-run 2026-09-21, both controls PASS.

    Evidence that argues against this (2)
    • The clean 0|0 control is the base rate for this set - 32 of 42 pan-fusion proteins have one - and over the 960 rows control counts track abundance at Spearman +0.461. Coiled-coil, elongated, self-associating proteins such as LUZP1 are a recognised hazard in affinity purification, and the CRAPome authors state that a study's own limited negative controls do not capture a complete background protein set. No contaminant-repository frequency for Q86V48 was retrieved by this beat and it is the cheapest external check available. IntAct has never curated this dataset. Mellacheruvu D et al. 2013
    • The eight-order-of-magnitude bait spread cuts both ways. It shows the index column's weakness is not about LUZP1 - but a prey whose recovery varies that much between baits purified in the same laboratory from the same cell line is also a prey whose recovery is dominated by something other than its affinity for the shared KMT2A N-terminus. Note that MLL-ENL, the bait with the 2.63e-10 row, is also the deepest bait for ACTB (316 spectra), VIM (73) and MAP7D1 (55) - the whole cytoskeletal group peaks on the same bait, which is a pattern about the purification and not about any one protein. The raw spectra at PXD009338 have not been reanalysed here. ProteomeXchange/PRIDE 2018
  2. E2strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    Depleting LUZP1 or its interacting protein EPLIN increases the levels of MyosinVa at the centrosome and increases primary cilium formation; LUZP1 localises to both actin filaments and the centrosome/basal body and is an actin-stabilising protein that regulates actin dynamics at least in part by mobilising ARP2 to centrosomes, and both LUZP1 and EPLIN interact with known ciliogenesis and cilia-length regulators.

    LUZP1 and the tumor suppressor EPLIN modulate actin stability to restrict primary cilia formation. · Gonçalves J, Sharma A, Coyaud É, Laurent EMN, Raught B, Pelletier L · J Cell Biol 2020
    What this evidence cannot show

    Human cultured cells (RPE-1-type ciliogenesis systems), proximity-dependent biotinylation plus depletion phenotypes; not haematopoietic, not a fusion system, and nothing in it is nuclear. It is cited to establish what LUZP1 is and where it lives, and for one cross-check: EPLIN/LIMA1, the partner named here, is present in the Skucha 960 at n = 2, which makes LUZP1 the only protein in this tranche whose named direct partner appears in the network. Read from the abstract.

    Evidence that argues against this (1)
    • EPLIN's presence is weak corroboration at best: n = 2 of 7 baits, no MLL-AF4 value at all, and the partner is itself an abundant actin-associated protein with the same background profile. A shared background source produces exactly this pattern - two members of one cytoskeletal neighbourhood, both weak, neither in the index column - and nothing here distinguishes that from a real co-recovery. Skucha A et al. 2018
  3. E3moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper

    Fimbacin, encoded by LUZP1, does not interact with canonical full-length filamin A but binds filamin A repeat 21 once its cryptic integrin-binding site is exposed; fimbacin is itself an actin cross-linking protein with an actin-binding site at residues 400-500, oligomerises as an estimated octamer through an amino-terminal predicted coiled-coil, and localises to actin stress fibres, with filamin A interaction stabilising it on the actin cytoskeleton by FRAP.

    What this evidence cannot show

    In vitro biochemistry, proteomics plus in silico motif screening, and overexpression in tissue culture cells; the octamer estimate is from size-exclusion chromatography, which reports hydrodynamic behaviour rather than stoichiometry for an elongated coiled-coil protein. Not haematopoietic, not nuclear, not a fusion system. Cited here for one specific property that bears directly on the AP-MS question - LUZP1 self-associates through an N-terminal coiled-coil and cross-links actin - which is the biophysical profile most likely to produce non-specific co-purification. Read from the abstract.

    Evidence that argues against this (1)
    • This is the most damaging citation in the entry for the interaction claim, and it is placed here deliberately: an elongated, self-oligomerising, actin-cross-linking protein is close to a worst case for affinity purification specificity. Against that, the one thing it cannot explain is the negative control - if LUZP1 were co-sedimenting non-specifically it should appear in the mock purifications, and it gives 0|0. That is weak evidence, because 32 of the 42 pan-fusion proteins are also 0|0 and the control tracks abundance, but it is not nothing. Skucha A et al. 2018
Connected to