Oncofusion

start / graph / gene-map3k14

Proteinstrong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.Q38-nfkb-signalling

MAP3K14 (NIK) — the one node in this pathway where ACTIVATION, not inhibition, is the proposed therapy, and the one that also damages normal stem cells

also called MAP3K14 · NIK · NF-kappa-B-inducing kinase · HsNIK · Q99558

NIK is a kinase that is normally destroyed as fast as it is made; when you stop that destruction it switches on the second NF-kB circuit and, in mouse MLL leukaemia, the disease gets better rather than worse. The catch is that the same manipulation also harms normal blood stem cells, so it would have to be aimed at the leukaemia specifically.

The same thing, for a scientist

MAP3K14 (UniProt Q99558, 947 aa, primary gene name read back) is NIK, the apex kinase of non-canonical NF-kB: it phosphorylates IKKa, which processes p100 to p52 and releases RelB:p52. In resting cells NIK is continuously degraded through a TRAF3/TRAF2/cIAP complex, so **its level, not its activity, is the switch**. The disease result was obtained by removing the degron: `NIK-deltaT3`, a non-degradable mutant lacking the TRAF3-binding domain, expressed from a floxed-STOP allele crossed to Vav-Cre (caNIK) or Rosa-CreER-T2 (NIKERT2) [E1]. **In MLL-AF9 AML, stabilising NIK delayed leukaemia onset, delayed LSC repopulation, reduced LSC self-renewal on re-transplantation with no homing defect (0.099 +/- 0.032 versus 0.121 +/- 0.037, n=4, p=0.403), and reduced colony number and size** [E1]. The molecular signature was clean: NIK protein up about two-fold, phospho-IKKa up, RelB up, p100-to-p52 processing on, nuclear RelB and p52 up, RelA down, Nfkbia and Tnfaip3 up [E1]. **The obstacle the authors name themselves:** NIK also impairs the self-renewal of normal HSPCs, so a therapy would need leukaemia-restricted stabilisation, delivered via an LSC-restricted surface receptor such as TIM3 or CD93 — a method they describe as currently unavailable [E1]. Their workaround was a Connectivity Map query that returned **verteporfin**, which suppressed leukaemic growth, transiently upregulated non-canonical components, downregulated RelA protein, and lost most of its effect when RelB was knocked down [E1].

What it looks like
loading AF-Q99558-F1…
AlphaFold AF-Q99558-F1 ↗
colourshape

This is a prediction, not a measurement. No one has seen this protein in this shape. The colours say how much the software trusts itself, and that is worth reading before anything else — the orange stretches are places the model is effectively saying this part has no fixed shape.

very high (90+)confident (70–90)low (50–70)very low (<50)
I have never read one of these pictures before

A protein is one long chain of amino acids that folds up. The ribbon traces that chain from one end to the other; it is not a wire, it is a simplification of where the backbone runs. Drag to rotate, scroll to zoom.

Domains are the stretches of chain that do a particular job, and they are what the coloured blocks above the picture mark out. Click one and the view flies to it. In this project the important question about any domain is usually whether the fusion still has it — the labels say lost where it does not.

Anything in yellow sticks is a bound small molecule, which is usually the drug.

Go deeper
Why this entry is an activation entry

Every other therapeutic proposition in this folder is 'block something'. This one is 'stabilise something', and that changes the bite-back analysis completely: the risk is not immunosuppression but chronic non-canonical signalling, which in other systems drives lymphoid malignancy. The authors note the contrast directly — NIK is tumour-promoting in B-cell neoplasms and their result 'differs from' that, matching instead NIK's inhibitory role in anaplastic large-cell lymphoma 1.

A 2026 paper reinforces the risk side from the other direction: synonymous MAP3K14 variants drive altered splicing to activate NF-kB in mature B-cell malignancies 2. That is a human genetic argument that constitutive NIK activity is oncogenic in the B lineage — and the index disease of this graph is a B-lineage leukaemia.

Verteporfin is not a NIK stabiliser and should not be described as one

Verteporfin arrived from a Connectivity Map query on the NIK-stabilised LSC signature — that is, it was selected for producing a similar transcriptional state, not for acting on NIK 1. It is an FDA-approved photosensitiser for macular degeneration that raises cellular reactive oxygen species, and it is widely used as a YAP/TEAD inhibitor. Its effect here was largely attenuated by RelB knockdown and had no additive effect on NIK-stabilised cells, which argues the route runs through the same arm — but 'acts through non-canonical NF-kB' is not 'stabilises NIK'. Any entry that calls verteporfin a NIK-targeted agent would be wrong.

Facts and figures
uniprotQ99558
length AA947
alphafold IDAF-Q99558-F1
resolution notegene_exact:MAP3K14 AND organism_id:9606 AND reviewed:true returned 1 reviewed row; gene_primary read back as MAP3K14; length 947 aa.
pathway armnon-canonical (apex)
regulationconstitutive degradation via a TRAF3/TRAF2/cIAP complex; level rather than activity is the switch
direction in diseasestabilisation SUPPRESSES MLL-AF9 mouse AML
tool usedNIK-deltaT3 non-degradable mutant (TRAF3-binding domain deleted), Vav-Cre or Rosa-CreER-T2
chemical matternone; verteporfin was signature-matched, not NIK-targeted
subnuclear localizationNO NUCLEAR POOL ANNOTATED, AND THE CYTOPLASMIC CALL ITSELF IS UNSOURCED - so this is a bounded absence rather than a NOT APPLICABLE. UniProt Q99558's single 'Cytoplasm' value has an empty evidence list [E_q89_map3k14_loc1]. Bounded 2026-09-21: MAP3K14[tiab] AND ("nuclear localization" OR nucleus OR "nuclear translocation" OR cytoplasm OR localization)[tiab] returns 11 records against an operand control of 146 for MAP3K14[tiab] alone - a live query returning a small, specific set, none of which this beat found to be a NIK compartment study at title level. THE SEARCH MUST BE RUN ON MAP3K14 AND NOT ON 'NIK': see data.symbol_collision_nik.
localization shown for fusionNO - nobody has localised NIK in any KMT2A fusion, in any lineage. The bounded query (MAP3K14[tiab] OR "NF-kappaB-inducing kinase"[tiab]) AND (MLL[tiab] OR KMT2A[tiab]) returns 2 records on 2026-09-21: PMID 29320732, this entry's E1 and a genetic-model paper with no localisation, and PMID 32598477, a mantle-cell-lymphoma mutation meta-analysis that is off topic at title level. So ONE on-topic record in the whole fusion-context literature for this gene, and it contains no compartment measurement.
localization
{
  "subcellular": "CYTOPLASM - AND UNIPROT ATTACHES NO EVIDENCE TO IT WHATSOEVER. Q99558 fetched 2026-09-21 carries exactly one SUBCELLULAR LOCATION value, 'Cytoplasm', with an EMPTY evidence list: no ECO:0000269, no ECO:0000250, no PROSITE or HAMAP rule, and no note. That is the weakest annotation class this tranche encountered, weaker than AFF3's uncoded nuclear call because AFF3 at least has an independent imaging paper behind it [E_q89_map3k14_loc1].",
  "why_the_compartment_is_nevertheless_the_mechanism": "This entry's own central point is that NIK's LEVEL, not its activity, is the switch - in resting cells NIK is continuously degraded through a TRAF3/TRAF2/cIAP complex, and the disease result was obtained with NIK-deltaT3, a non-degradable mutant lacking the TRAF3-binding domain. That degradation machinery is cytosolic, so the cytoplasmic call is mechanistically coherent even though it is unsourced. What NIK does next is move somebody ELSE: it phosphorylates IKKa, which processes p100 to p52 and releases RelB:p52 to enter the nucleus. THE NUCLEAR TRANSLOCATION IN THIS PATHWAY BELONGS TO RelB:p52, NOT TO NIK, and the entry says so explicitly so that a reader does not file the pathway's nuclear step under this gene.",
  "subnuclear": "NOT APPLICABLE AS FAR AS THE RECORD GOES, BUT RECORDED AS A BOUNDED ABSENCE RATHER THAN A NOT APPLICABLE, and the distinction is deliberate. NIK is annotated cytoplasmic with no nuclear pool, which would ordinarily justify NOT APPLICABLE as it does for CD33 and ELOVL1 in this tranche - but those two are excluded by TOPOLOGY (a single-pass surface receptor, a seven-pass ER enzyme), which is a structural bar, whereas NIK is a soluble kinase with nothing structural preventing nuclear entry and an annotation that carries no evidence at all. A soluble cytoplasmic kinase with an unsourced compartment call is an open question, not a closed one."
}
symbol collision nik
{
  "finding": "NEW COLLISION, NOT IN data/symbol-collisions.json - grepped before searching per rule 88, and RE-GREPPED at hand-back because the registry grew from 93 to 97 rows during this beat (the coordinator added SIP1, NEXT, NOP2 and WDR5-versus-WDR50 on 2026-09-21). At 97 rows there is still NO row for NIK, MAP3K14 or MAP4K4. Stated with both counts because an inventory read once during a concurrent cycle is stale by the time it is quoted.",
  "the_collision": "'NIK' is a gene synonym of BOTH MAP3K14 (Q99558, 947 aa, NF-kappa-B-inducing kinase) AND MAP4K4 (O95819, 1,239 aa, whose synonyms are HGK, KIAA0687 and NIK, for NCK-INTERACTING KINASE). Verified live 2026-09-21 by fetching both UniProt records [E_q89_map3k14_loc1][E_q89_map3k14_loc2].",
  "why_it_bites_on_this_dimension_specifically": "BOTH PROTEINS ARE ANNOTATED CYTOPLASMIC - MAP4K4 'Cytoplasm' on ECO:0000269 PubMed:14966141. So a localisation search on 'NIK' returns two cytoplasmic kinases and the WRONG ANSWER LOOKS RIGHT: a reader would find cytoplasmic records, conclude the compartment is confirmed, and never notice the records were about a different kinase. This is rule 65's shape (the protein-name defence fails) with the added twist that the FACT BEING SOUGHT is identical for both, so no sanity check on the content can separate them.",
  "measured": {
    "query": "NIK[tiab] AND (\"MAP4K4\"[tiab] OR \"Nck-interacting kinase\"[tiab])",
    "querytranslation": "\"NIK\"[Title/Abstract] AND (\"MAP4K4\"[Title/Abstract] OR \"Nck-interacting kinase\"[Title/Abstract])",
    "records": 25,
    "date": "2026-09-21",
    "tool": "NCBI esearch db=pubmed"
  },
  "defence_that_works": "LENGTH. 947 against 1,239 aa - a 292-residue gap, far outside the sixteen-residue SMC1A/SMC3 limit rule 66 names as the discriminator's edge. Assert uniprot plus length_aa, which this entry already does, and verify-accessions.py will catch a swap.",
  "defence_that_does_not_work": "Searching 'NIK'. Use MAP3K14, or NIK paired with an NF-kB term, and title-check.",
  "proposed_registry_row": "token 'NIK', class 'alias_is_shared_by_two_kinases_with_the_same_annotated_compartment', candidates MAP3K14/Q99558/947 and MAP4K4/O95819/1239, length_defence_usable true, block_autogeneration true. Proposed to the coordinator rather than written, because data/symbol-collisions.json is not this beat's file."
}
cell type
{
  "normal": "WEAKLY EXPRESSED AND BROADLY - UniProt Q99558 tissue specificity reads 'Weakly expressed in testis, small intestine, spleen, thymus, peripheral blood leukocytes, prostate, ovary and colon' [E_q89_map3k14_loc1]. PERIPHERAL BLOOD LEUKOCYTES, SPLEEN AND THYMUS ARE ALL NAMED, so unlike BICRA in this tranche the haematopoietic compartment is at least in the list - and the qualifier is 'weakly', which is consistent with this entry's own mechanism, since a protein held at near-zero by constitutive degradation should look weakly expressed in any steady-state assay.",
  "in_this_disease": "MURINE MLL-AF9 AML, AND NORMAL MOUSE HAEMATOPOIETIC STEM CELLS - the second is the bite-back. This entry's existing E1 records that stabilising NIK with the non-degradable NIK-deltaT3 allele, driven from a floxed-STOP allele crossed to Vav-Cre or Rosa-CreER-T2, suppressed MLL-AF9-induced AML - delayed onset, delayed LSC repopulation, reduced LSC self-renewal on re-transplantation with no homing defect - while the same manipulation also harms normal blood stem cells. NAMING THE FUSION: MLL-AF9 is KMT2A::MLLT3, MOUSE, MYELOID; nothing in KMT2A::AFF1 and nothing B-lineage.",
  "grade": "The cell-type record is a genetic-model record. No NIK protein measurement, let alone a localisation, exists in any human leukaemic cell."
}
cell state
{
  "state": "DEGRADATION STATE, WHICH IS THIS GENE'S ENTIRE STORY AND IS A STABILITY STATE RATHER THAN A DIFFERENTIATION STATE. In resting cells NIK is continuously destroyed by the TRAF3/TRAF2/cIAP complex; receptor engagement or loss of that complex lets it accumulate, and accumulation is activation. So the meaningful 'state' variable for NIK is how much of it exists, not what the cell is differentiating into.",
  "why_that_matters_for_localisation": "A protein whose steady-state level is held near zero is a hard subject for any imaging experiment, which is a plausible practical reason - beyond simple neglect - that NIK has no sourced compartment annotation after three decades. Endogenous NIK immunofluorescence in an untreated cell would be close to a negative-control experiment.",
  "bounded": "No NIK cell-state or localisation measurement exists in any leukaemic cell."
}
localization bounded absence
{
  "date": "2026-09-21",
  "tool": "NCBI esearch db=pubmed",
  "queries": [
    {
      "query": "MAP3K14[tiab] AND (\"nuclear localization\"[tiab] OR nucleus[tiab] OR \"nuclear translocation\"[tiab] OR cytoplasm[tiab] OR localization[tiab])",
      "querytranslation": "\"MAP3K14\"[Title/Abstract] AND (\"nuclear localization\"[Title/Abstract] OR \"nucleus\"[Title/Abstract] OR \"nuclear translocation\"[Title/Abstract] OR \"cytoplasm\"[Title/Abstract] OR \"localization\"[Title/Abstract])",
      "count": 11
    },
    {
      "query": "MAP3K14[tiab]",
      "querytranslation": "\"MAP3K14\"[Title/Abstract]",
      "count": 146,
      "role": "OPERAND CONTROL - the 11 is a real subset of a 146-record literature, not a dead query"
    },
    {
      "query": "(MAP3K14[tiab] OR \"NF-kappaB-inducing kinase\"[tiab]) AND (MLL[tiab] OR KMT2A[tiab])",
      "querytranslation": "(\"MAP3K14\"[Title/Abstract] OR \"NF-kappaB-inducing kinase\"[Title/Abstract]) AND (\"MLL\"[Title/Abstract] OR \"KMT2A\"[Title/Abstract])",
      "count": 2,
      "on_topic": 1
    }
  ],
  "name_list_note": "Run on MAP3K14 and on the spelled-out kinase name, NOT on 'NIK', because NIK is shared with MAP4K4 and both proteins are annotated cytoplasmic - see data.symbol_collision_nik. The bare NIK form was run once as a diagnostic and returned 135 records for the same localisation clause, i.e. a twelvefold inflation over the clean symbol, which is the contamination made visible.",
  "absence_class": "never-measured"
}
How this could bite us back
  • NIK stabilisation impairs normal haematopoietic stem and progenitor self-renewal. The authors identify this as the central obstacle and propose a delivery solution they say does not exist.
  • Constitutive non-canonical NF-kB activity is oncogenic in the B lineage - NIK is tumour-promoting in B-cell neoplasms and MAP3K14 variants activate NF-kB in mature B-cell malignancies. Proposing chronic NIK activation in an infant B-ALL would be proposing a known B-cell oncogenic signal as a therapy.
  • NIK stabilisation represses canonical NF-kB, so it carries the infection risk of the canonical-blocking proposals in this folder as well as its own.
  • The non-canonical arm builds secondary lymphoid organs and medullary thymic epithelium. Chronic activation in a developing child has developmental consequences no leukaemia experiment measures.
  • TIFAB and HOXA9 each reverse the protective effect by downregulating RelB, so a resistance route to a NIK-based therapy already has two named genes and both are upregulated in this disease.
Still open
  1. Does NIK stabilisation suppress or accelerate KMT2A-rearranged B-ALL? NIK is tumour-promoting in B-cell neoplasms and the only leukaemia data are myeloid, so the sign in the index disease is genuinely unknown rather than merely untested.
  2. Is there any chemical matter that stabilises NIK? The proposal rests on an agent that does not exist; the cIAP-degrading SMAC mimetics stabilise NIK as a side effect and were not tested here.
  3. Would NIK stabilisation combine with or cancel a menin inhibitor? Menin binds NFKB2, the non-canonical precursor, so a menin inhibitor may itself perturb the arm this proposal wants to activate.
  4. Does verteporfin's effect survive a YAP/TEAD-independent control? Its RelB dependence is suggestive but its known pharmacology was not excluded.
  5. Where does NIK-deltaT3 protein go once it is allowed to accumulate? The disease experiment in this entry is a stabilisation experiment, endogenous NIK is normally held near zero, and nobody has imaged the stabilised protein - so the compartment of the species that actually does the work in the published model is unknown.
  6. UniProt's cytoplasmic call for NIK carries no evidence at all after three decades of NF-kB work. Is there a primary imaging paper for endogenous human NIK anywhere, and if not, is that neglect or is it that a protein held at near-zero abundance is effectively unimageable?
  7. Should data/symbol-collisions.json carry a NIK row? Proposed to the coordinator with the measurement attached; the registry currently has none, and both candidate proteins share the same annotated compartment, which defeats content-based disambiguation.
Every source behind this entry (5)
  1. E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.paper

    Stabilisation of NIK using a non-degradable NIK-deltaT3 allele suppresses MLL-AF9-induced AML: it reduced colony formation and cell numbers in vitro, significantly delayed AML onset in vivo, delayed LSC repopulation, and inhibited LSC self-renewal on re-transplantation with no homing defect. Mechanistically NIK protein rose about two-fold with increased IKKa phosphorylation, RelB upregulation, p100-to-p52 processing, increased nuclear RelB and p52, reduced RelA expression and nuclear localisation, and upregulation of the canonical inhibitors Nfkbia and Tnfaip3. NIK also impairs the self-renewal of normal HSPCs, which the authors identify as the key obstacle, proposing LSC-restricted delivery via receptors such as TIM3 or CD93 as a currently unavailable solution. A Connectivity Map query on the NIK-stabilised LSC signature identified verteporfin, which dose-dependently suppressed leukaemic growth and colony formation, delayed AML in vivo, transiently upregulated non-canonical components, downregulated RelA protein, and was largely attenuated by RelB knockdown.

    Stabilization of NF-κB-Inducing Kinase Suppresses MLL-AF9-Induced Acute Myeloid Leukemia. · Xiu Y, Dong Q, Li Q, Li F, Borcherding N, Zhang W, Boyce B, Xue HH, Zhao C · Cell Reports 2018
    What this evidence cannot show

    Genetic stabilisation of a mutant protein in mice, not a drug acting on endogenous NIK; there is no NIK stabiliser in existence. One fusion (MLL-AF9), one species, one laboratory. The human relevance claim rests on a supplementary figure. Verteporfin's selection is transcriptional-signature matching, and verteporfin has well-known YAP/TEAD and ROS activities that this design cannot exclude as the operative mechanism. Full text read this session via Europe PMC fullTextXML (PMC5810947), 44,387 characters.

    Evidence that argues against this (1)
    • NIK is tumour-promoting in B-cell neoplasms, which the authors state as the contrast that made their result unexpected. Since the index disease of this graph is infant B-ALL, the direction that holds in myeloid AML cannot be assumed to hold in the disease this graph exists for. Li EW et al. 2026
  2. E2strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database

    Counted absence and enumeration. (KMT2A OR MLL OR "mixed-lineage leukemia") AND (MAP3K14 OR "NF-kappaB-inducing kinase"[tiab] OR "NF-kB-inducing kinase"[tiab]) returns 3 PubMed records: the MLL-AF9 NIK paper, a mantle cell lymphoma mutation meta-analysis, and a 2026 paper reporting that MAP3K14 synonymous variants drive altered splicing to activate NF-kB in mature B-cell malignancies. There is exactly one KMT2A-relevant NIK study in the literature.

    What this evidence cannot show

    querytranslation was read. The short alias NIK was deliberately NOT searched as a bare token: it is a three-letter string that matches unrelated fields and would inflate the count, exactly the alias-precision failure the brief records for RD/NELFE. The 2026 Blood paper's abstract was fetched and read: two recurrent synonymous MAP3K14 variants introduce splice donor sites that remove the TRAF3-binding motif, and prime-edited cell lines show NF-kB activation with enhanced proliferation and survival across CLL, LPL/Waldenstroem, myeloma and mantle cell lymphoma. Those are MATURE B-cell malignancies, not precursor B-ALL, so the read-across to infant KMT2A-rearranged disease is an argument about the lineage's tolerance of non-canonical activation, not a result in it.

    Evidence that argues against this (1)
    • A zero at the symbol level is not a zero at the pathway level, and on this beat that is demonstrable rather than hypothetical: PMID 29320732 studies the non-canonical arm directly in MLL-AF9 leukaemia and is unreachable from any of these subunit symbol queries, because it names the kinase and the pathway rather than the subunit. The count is honest about what was searched and should not be read as evidence that the biology is unstudied - only that it is not indexed under this symbol. Xiu Y et al. 2018
  3. E3established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    UniProt reviewed human record Q99558 (M3K14_HUMAN) has primary gene name MAP3K14 and length 947 aa; gene_exact:MAP3K14 AND organism_id:9606 AND reviewed:true returned exactly one row and gene_primary read back as MAP3K14.

    What this evidence cannot show

    Resolved 2026-09-20 with gene_primary requested and all rows read. MAP3K7 (TAK1, O43318, 606 aa) was resolved the same way and returns zero relevant records in this disease; it is recorded as a bounded absence rather than given an entry.

    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
  4. E_q89_map3k14_loc1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    UniProt Q99558 (M3K14_HUMAN, primary gene MAP3K14, synonym NIK, 947 aa, read back 2026-09-21) carries exactly ONE subcellular location value, 'Cytoplasm', WITH AN EMPTY EVIDENCE LIST - no experimental, by-similarity or rule-based attribution of any kind - and no location note. Its TISSUE SPECIFICITY comment reads: 'Weakly expressed in testis, small intestine, spleen, thymus, peripheral blood leukocytes, prostate, ovary and colon.'

    What this evidence cannot show

    Established as a statement about the record, and the record is close to empty on this dimension. An unevidenced location comment tells you what a curator believes, not what was measured, and this beat found no primary imaging paper for endogenous human NIK in eleven records of a live 146-record literature. The tissue comment is likewise uncoded, bulk-tissue and undated.

    Evidence that argues against this (1)
    • The counter-case for the cytoplasmic call is strong on mechanism even though it is absent from the record, and the entry should not treat 'unsourced' as 'doubtful'. NIK's regulation is degradative and its destruction machinery - TRAF3, TRAF2, cIAP1/2 - is cytosolic; its substrate IKKa is cytosolic; and the whole non-canonical pathway is organised around keeping NIK out of existence until a receptor signal arrives. A protein consumed by a cytosolic complex is cytosolic. What the missing evidence costs is not confidence in the resting compartment but the ability to detect anything else: there is no baseline against which a NUCLEAR pool could be recognised if one appeared under stabilisation, and the disease-relevant experiment in this entry is precisely a stabilisation experiment. Nobody has asked where NIK-deltaT3 protein goes once it is allowed to accumulate, and that is a different question from where NIK sits when it barely exists. UniProt Consortium 2026
  5. E_q89_map3k14_loc2established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    'NIK' NAMES TWO DIFFERENT HUMAN KINASES AND BOTH ARE ANNOTATED CYTOPLASMIC. UniProt O95819 (M4K4_HUMAN, primary gene MAP4K4, 1,239 aa, read back 2026-09-21) lists gene synonyms HGK, KIAA0687 and NIK - for NCK-interacting kinase - and carries the subcellular location 'Cytoplasm' on ECO:0000269 PubMed:14966141. MAP3K14 (Q99558, 947 aa) carries the synonym NIK for NF-kappa-B-inducing kinase and the subcellular location 'Cytoplasm'. On 2026-09-21 the query NIK[tiab] AND ("MAP4K4"[tiab] OR "Nck-interacting kinase"[tiab]) returns 25 records. data/symbol-collisions.json was grepped before searching (93 rows at that moment) and re-grepped at hand-back after the coordinator grew it to 97 rows the same day; at both readings it contains no entry for NIK, MAP3K14 or MAP4K4.

    What this evidence cannot show

    Verified live against both UniProt records this session. The 25-record co-occurrence query measures how often the two names appear together, which is a lower bound on contamination - papers using 'NIK' for MAP4K4 without ever writing MAP4K4 are not counted, and those are the dangerous ones. The registry absence was checked twice by grepping the file this session, at 93 rows and again at 97 rows after the coordinator committed four new rows mid-beat, and is stated as of 2026-09-21.

    Evidence that argues against this (1)
    • One might argue the collision is harmless because context disambiguates - an NF-kB paper means MAP3K14 and a cytoskeletal or metabolic paper means MAP4K4 - and for most questions that is true. It is specifically NOT true for the question this beat was sent to answer. Context disambiguation works when the two proteins have different properties; here the property being looked up is IDENTICAL (both cytoplasmic), so a localisation search on 'NIK' returns confirmatory-looking records for either protein and the error is undetectable from the answer. The diagnostic run makes the size visible: the same localisation clause returns 11 records against MAP3K14 and 135 against NIK, a twelvefold inflation, and a beat that took the larger number as this gene's literature would have been reading mostly about a different kinase. That is the failure mode rule 65 describes for HDAC7/HDAC9, arriving through a shared alias rather than a shared protein name. UniProt Consortium 2026
Connected to