Oncofusion

start / graph / gene-rest

Proteinmoderate confidence 3 of 5: One strong study, or several smaller consistent ones.Q101-writers-and-readers

REST / NRSF - the transcription factor that delivers G9a to chromatin through MED19 and MED26, is a paediatric cancer gene, and is the worst search token in this corpus

also called REST · NRSF · RE1-silencing transcription factor · neural-restrictive silencer factor · XBR

REST is a switch that keeps nerve-cell genes turned off in every cell that is not a nerve cell, and it does it by hiring silencing enzymes - including the H3K9 methyltransferase G9a, which it reaches through two Mediator subunits this project has already written about. It is also a Wilms tumour gene, and its name is an ordinary English word, which makes it almost impossible to search for.

The same thing, for a scientist

REST (Q13127, 1,097 aa, HGNC:9966) is a nine-zinc-finger repressor that binds the RE1/NRSE element and silences neuronal genes in non-neuronal cells by recruiting the corepressors SIN3A, SIN3B and RCOR1/CoREST [E1]. It is in this graph for three reasons, and none of them is neuronal biology. **(1) It is the transcription factor in this graph's own G9a finding**: `gene-med19` reports that MED19 and MED26 are the two Mediator subunits REST uses to deliver G9a-dependent H3K9me2 silencing, and MED19 is one of only eighteen proteins curated against a KMT2A fusion construct. UniProt adds the condition that entry lacks - **REST interacts with EHMT1 and EHMT2 ONLY in the presence of CDYL**, within a complex of CDYL, REST, WIZ, SETDB1, EHMT1 and EHMT2 [E2]. **(2) It is a paediatric cancer gene**: UniProt lists REST as causative in **Wilms tumor 6**, and REST is expressed at higher levels in the lymphocytic compartment - spleen, thymus and peripheral blood lymphocytes [E1]. **(3) It is a measured retrieval hazard, and this entry exists partly to record it.** Re-measured by this beat rather than quoted from a brief: a case-sensitive word-boundary match for the token reaches 359 of 1,990 node files (2026-09-22), and the token immediately preceding it is UniProt 250 times, IntAct 165, Ensembl 91, PMC 72 and HGNC 37 - API references in our own prose. In PubMed it is worse than the registry says: **`REST[gene]` expands to `"rest"[All Fields]` and returns 216,469 records - MORE than the 196,013 of the bare `REST[tiab]`** [E3]. Only `NRSF[tiab]` (501) and `"RE1-silencing transcription factor"[tiab]` (289) are usable, they overlap by just 81 records, and through both of them **REST's leukaemia and haematopoietic literature is empty on title-check** [E4].

What it looks like
REST1,097 aa
C2H2-type zinc finger 1 · residues 159–181C2H2-type zinc finger 5 (required for nuclear localization) · residues 304–326C2H2-type zinc finger 9 · residues 1060–1082Interaction with SIN3AInteraction with SIN3A · residues 32–122NRSE-binding region · residues 201–212Interaction with RCOR1Interaction with RCOR1 · residues 1009–108702004006008001,000
loading AF-Q13127-F1…
AlphaFold AF-Q13127-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
The one route into this project's biology, and the cofactor requirement the graph did not have

gene-med19 was written because MED19 is curated in IntAct against an engineered MLL-AFF4 chimera - one of only eighteen proteins in the whole curated record whose partner is a KMT2A fusion rather than KMT2A or the 3-prime partner. Its epigenetics field then records the thing that makes MED19 an epigenetic node at all: MED19 and MED26 are the two Mediator subunits identified as direct physical and synergistic functional targets of REST in G9a/EHMT2-dependent H3K9me2 silencing of neuronal genes in non-neuronal cells (PMID 19049968). Its own reopening condition is H3K9me2 and G9a occupancy at KMT2A::AFF1 target loci under MED19 depletion.

What this entry adds is the step that route requires and nobody here had written: CDYL. UniProt records that REST interacts with EHMT1 and EHMT2 only in the presence of CDYL, and that a complex exists containing at least CDYL, REST, WIZ, SETDB1, EHMT1 and EHMT2; REST's own FUNCTION comment states that transcriptional repression by REST-CDYL via the recruitment of histone methyltransferase EHMT2 may be important in transformation suppression 2. So the chain gene-med19 half-describes is REST → (CDYL required) → EHMT1/EHMT2 → H3K9me2, with Mediator as the adaptor - and CDYL has no entry in this graph, is not a DepMap dependency (mean -0.0911, rank 4,136 in this project's own scan), and has never been measured in a KMT2A-rearranged cell.

Note the direction, because it is not the obvious one. UniProt's own words put the REST-CDYL-EHMT2 route on the side of transformation SUPPRESSION. Combined with mark-h3k9me3's position that H3K9 methylation restrains the MLL-fusion programme, the honest prediction is that this axis is protective and that interfering with it is the wrong direction - which is the same sign warning this beat records for PRMT6 and for the H3K9 marks generally.

★ The token, measured - and the dispatch brief's recommended operand is the worst of the three

This is a rediscovery of registry row 13 inside the corpus and a genuinely new finding in PubMed, and the two halves should be read separately.

Inside this corpus (rediscovery, and the row is now partly stale). Row 13 records REST as acronym_is_ordinary_technical_vocabulary_not_this_gene, named_in_entries: 217, block_autogeneration: true, with the note every occurrence checked was the web API, and the sentence "REST is a real neuronal transcription factor and could in principle be relevant, but nothing in this graph is currently about it". That last clause is no longer true: gene-med19, written in cycle 54, carries the RE1-silencing transcription factor as load-bearing evidence for its epigenetics field, and disambiguates it explicitly in its own body text. The trap itself is live and larger: re-measured by this beat, a case-sensitive word-boundary match reaches 359 of 1,990 node files (2026-09-22) against named_in_entries: 217 when the row was written - though part of that growth is this beat itself, which names REST in seven new entries, so the figure shows the trap persisting rather than spreading.

In PubMed (new, and it contradicts the dispatch brief that sent this beat). The brief instructed: use RE1-silencing transcription factor, NRSF, or REST[gene]. Measured 2026-09-22 with every querytranslation read back 3:

operandrecordsquerytranslation
REST[tiab]196,013"REST"[Title/Abstract]
REST[gene]216,469"rest protein human"[Supplementary Concept] OR "rest protein human"[All Fields] OR **"rest"[All Fields]** OR "rest"[MeSH Terms]
NRSF[tiab]501"NRSF"[Title/Abstract]
"RE1-silencing transcription factor"[tiab]289the phrase

REST[gene] is worse than REST[tiab]. The [gene] tag does not restrict to the gene; it expands into a disjunction that includes "rest"[All Fields], the ordinary English word, and so returns twenty thousand records more than the untagged form. Every scoped count built on it is noise: REST[gene] AND leukemia[tiab] = 676, REST[gene] AND hematopoi*[tiab] = 393, REST[gene] AND MLL[tiab] = 23, REST[gene] AND KMT2A[tiab] = 5.

And there is a second, disease-specific collision that makes this maximally dangerous. UniProt lists REST as causative in Wilms tumor 6 - and in the Wilms-tumour literature a "nephrogenic rest" is a standard pathological entity, so REST[gene] AND "Wilms tumor"[tiab] = 74 in the one disease where a real REST result would be expected. The collision word and the gene's own disease are the same word in the same papers.

Both aliases are required, not either. Id sets rather than counts, as registry row 122 demands: NRSF[tiab] returns 501, the full name returns 289, their intersection is 81 and their union is 709 - so 59.2% of the reachable literature is NRSF-only and 29.3% is full-name-only, and no single safe operand reaches even three-quarters of it.

What is there, once the token is safe: nothing in this disease

Through both safe operands, with every count's translation read back and every zero run twice 4:

queryrecordson title-check
NRSF[tiab] AND leukemia[tiab]10 - PMID 33828122 is An order independent algorithm for inferring gene regulatory network using quantile value for conditional independence tests
NRSF[tiab] AND hematopoi*[tiab]10 - PMID 37833991 is Mitogen-Activated Protein Kinase and Exploratory Nuclear Receptor Crosstalk in Cancer Immunotherapy
NRSF[tiab] AND MLL[tiab]0-

So REST has no leukaemia literature and no haematopoietic literature at all, and the two records that look like they might are a network-inference methods paper and a review. The brief's instruction to title-check caught both, and without it this entry would have reported 1 and 1 rather than 0 and 0.

That absence sits oddly beside the expression data, which is the reason to keep the question open rather than close it: UniProt records REST as expressed at higher levels in the tissues of the lymphocytic compartment, including spleen, thymus, peripheral blood lymphocytes and ovary 1. A transcription factor that is lymphocyte-enriched, is a paediatric cancer gene, and delivers a repressive histone methyltransferase through two Mediator subunits - one of which is curated against a KMT2A fusion - has never been studied in a blood cancer.

The most likely reason is the token. A field whose gene symbol is a high-frequency English word is under-searched by construction, and this graph's own experience is the demonstration: REST sat at the top of the named-but-unwritten queue for cycles, ahead of every genuine gap, purely because of API references in our own prose.

Localization, cell type, and the degradation control

Subcellular: NUCLEUS AND CYTOPLASM, both experimental and both repeatedly cited - the best-evidenced localisation record in this beat. UniProt Q13127 carries multiple location comments, and across them Nucleus is coded ECO:0000269 to PubMed:16442230, 21258371, 24670762, 27531581 and 30684677, and Cytoplasm to PubMed:24670762, 27531581, 30684677 and 16442230 1. Subnuclear: NO COMPARTMENT ASSIGNED, recorded as an absence - although the tissue-specificity comment does record a pathological compartment: in Parkinson disease and dementia with Lewy bodies, localization to Lewy bodies and pale bodies was detected, with decreased nuclear levels in dopaminergic and cortical neurons. That is a disease-state relocalisation, not a normal subnuclear address, and it is recorded as such.

The C2H2 zinc finger 5 (304-326) is required for nuclear localization 1 - one of nine zinc fingers, so the DNA-binding array and the import signal are interleaved, and a zinc-finger mutation can be a localisation mutation.

Cell type and state. Neuronal by function and by most of its expression record, but explicitly lymphocyte-enriched as well (spleen, thymus, peripheral blood lymphocytes). DepMap: not essential, mean gene effect -0.2147 over 1,258 lines, 5.2% of lines depleted, lymphoid tissue -0.1385 over 97 lines 5; in this project's own KMT2A scan the difference is +0.0385 Chronos units at rank 13,754 of 17,728, which ranks noise between two near-zero arms.

Two control layers worth recording because they are drug-adjacent. REST protein is a substrate of the SCF ubiquitin-ligase F-box proteins FBXW11 and BTRC and is deubiquitinated by USP7 1 - so REST abundance is proteasomally controlled, and this graph already holds a USP layer (target-usp1-in-kmt2a-rearranged-leukaemia, gene-usp2-adjacent entries) and a degron layer. Separately, SRRM4-dependent alternative splicing converts REST to isoform 3, which binds the NRSE more weakly and can act against full-length REST 1 - so REST activity has a splicing switch, in a graph that holds hyp-splicing-landscape-kmt2a-r.

Facts and figures
uniprotQ13127
uniprot IDREST_HUMAN
gene symbolREST
length AA1097
hgnc IDHGNC:9966
ensembl gene IDENSG00000084093
alphafold IDAF-Q13127-F1
accession assertionQ13127 asserted explicitly. gene_exact:REST AND organism_id:9606 AND reviewed:true returns exactly ONE reviewed human record (2026-09-22), 1,097 aa, with NRSF and XBR as gene synonyms - so the UNIPROT lookup is clean and it is only the LITERATURE and FREE-TEXT searches that are poisoned. That asymmetry is worth stating: a token can be perfectly safe in a structured identifier lookup and catastrophic in an index search.
PDB count rcsb3
PDB noteThree entries by RCSB accession-index query on Q13127 (2026-09-22), the full list; UniProt cross-references the same three. For a 1,097-residue nine-zinc-finger transcription factor that is near-total structural darkness - the structures cover fragments, and no full-length or corepressor-complex structure exists.
domain architecture noteNine C2H2-type zinc fingers, eight clustered at 159-412 and a ninth isolated at 1060-1082, with the two corepressor-interaction regions at opposite ends - SIN3A at 32-122 (SIN3B at 43-57) at the N-terminus and RCOR1/CoREST at 1009-1087 overlapping the ninth zinc finger. The region required for NRSE binding is 201-212. ZINC FINGER 5 (304-326) IS REQUIRED FOR NUCLEAR LOCALIZATION, so the DNA-binding array and the import determinant are interleaved and a zinc-finger mutation can be a localisation mutation rather than a binding mutation. Extensive disorder at 452-642, 774-837, 853-938 and 961-1049. The `domains` list gives the first, fifth and ninth zinc fingers plus the three functional regions rather than all nine, so the span is visible without inventing a merged boundary.
enzyme classNOT AN ENZYME. REST is a zinc-finger DNA-binding repressor that recruits catalytic corepressors - SIN3A/SIN3B with histone deacetylases, RCOR1/CoREST, the BHC complex, and EHMT1/EHMT2 via CDYL.
localizationNUCLEUS AND CYTOPLASM, both experimental and both multiply cited - the best-evidenced localisation record in this beat. UniProt Q13127 fetched 2026-09-22 carries several SUBCELLULAR LOCATION comment blocks (some scoped to isoform 3), across which Nucleus is coded ECO:0000269 to PubMed:16442230, 21258371, 24670762, 27531581 and 30684677 and Cytoplasm to PubMed:24670762, 27531581, 30684677 and 16442230. C2H2-type zinc finger 5 is required for nuclear localization. This entry does not attribute a compartment to a specific isoform, because the record does not cleanly support that.
localization evidence codeECO:0000269 throughout, with five citations for Nucleus and four for Cytoplasm and no by-similarity values. None of the cited papers was read for this entry, so rule 91 still applies as to which is the founding observation.
subnuclear localizationNO NORMAL COMPARTMENT ASSIGNED, recorded as an absence. The record does however carry a PATHOLOGICAL relocalisation, which is recorded separately and not as a subnuclear address: in Parkinson disease and dementia with Lewy bodies, decreased nuclear REST was observed in dopaminergic and cortical neurons with localization to LEWY BODIES and PALE BODIES (PubMed:30684677), and in Alzheimer disease, frontotemporal dementia and dementia with Lewy bodies decreased nuclear levels were observed in prefrontal cortex and hippocampus but not dentate gyrus or cerebellum (PubMed:24670762). REOPENING CONDITION: REST immunofluorescence or fractionation in a t(4;11) line - no REST imaging in any haematopoietic cell was found.
localization shown for fusionNO - nobody has looked in any fusion, and nobody has looked in any blood cell. There is no REST experiment of any kind in a haematopoietic system: through safe operands, NRSF[tiab] AND hematopoi*[tiab] = 1 and that record is a review.
epigenetic readoutNOT A WRITER, ERASER OR READER - AND NOT NOT-APPLICABLE, for the same reason MED19 is not. REST has no catalytic and no reader module: nine C2H2 zinc fingers, two corepressor-interaction regions and extensive disorder. What it does is DELIVER catalytic corepressors to a defined DNA element, so its epigenetic readout is other enzymes' marks. (1) HISTONE DEACETYLATION, via SIN3A/SIN3B and RCOR1/CoREST, and via the BHC complex which deacetylates and demethylates specific histone sites at RE1/NRSE. (2) H3K9 METHYLATION, via EHMT1/EHMT2 - and this is the route that reaches this project, because MED19 and MED26 are the two Mediator subunits REST uses for G9a-dependent H3K9me2 silencing (PMID 19049968), MED19 being one of only eighteen proteins curated against a KMT2A fusion construct. UniProt adds the requirement that gene-med19 lacks: the REST-EHMT1/EHMT2 interaction occurs ONLY in the presence of CDYL, within a CDYL/REST/WIZ/SETDB1/EHMT1/EHMT2 complex, and REST-CDYL recruitment of EHMT2 is described as potentially important in TRANSFORMATION SUPPRESSION - so the predicted sign of this axis is protective. BOUNDED, and the bounding is only possible through safe operands: NRSF[tiab] AND leukemia[tiab] = 1 (title-checked, off topic), NRSF[tiab] AND hematopoi*[tiab] = 1 (title-checked, off topic), NRSF[tiab] AND MLL[tiab] = 0; the approved symbol CANNOT be used as an operand at all - REST[gene] = 216,469 and REST[tiab] = 196,013. No H3K9me2, CDYL or REST measurement exists in any KMT2A-rearranged cell.
epigenetic mark namedH3K9me1/me2 - deposited by EHMT1/EHMT2, which REST delivers via CDYL and, per this graph's own finding, via MED19 and MED26. Plus histone deacetylation at RE1/NRSE sites via SIN3A, SIN3B, RCOR1 and the BHC complex. REST catalyses neither.
cell typeNeuronal by function and by most of the record - neurons of prefrontal cortex, hippocampal pyramidal neurons, dentate granule neurons, cerebellar Purkinje and granule neurons, substantia nigra dopaminergic neurons, and neural progenitor cells, all at protein level. BUT ALSO LYMPHOCYTE-ENRICHED: UniProt records higher expression in the tissues of the lymphocytic compartment - spleen, thymus, peripheral blood lymphocytes and ovary - on one 1996 citation. DepMap: 1,258 lines mean -0.2147, 5.2% depleted; lymphoid tissue n = 97 mean -0.1385. NO measurement in an infant t(4;11) sample, none in fetal liver, LMPP or pro-B, and no REST experiment in any haematopoietic cell at all.
cell stateDIFFERENTIATION and DISEASE STATE are the two documented ones and both are neural. REST maintains repression of neuronal genes in neural stem cells and dissociates from RE1/NRSE sites to permit transcription and neuronal differentiation; and in Alzheimer disease, frontotemporal dementia, Parkinson disease and dementia with Lewy bodies nuclear REST falls in specific neuronal populations. A third is post-transcriptional: SRRM4-dependent alternative splicing inactivates REST by producing isoform 3, required in inner-ear mechanosensory hair cells for derepression of neuronal genes and hearing. NO haematopoietic differentiation, quiescence, persister or niche state has been examined - and this matters for a graph with a lineage-switch layer, because REST is the canonical enforcer of lineage-inappropriate gene silencing and lineage switch is this disease's signature infidelity.
shown for fusionNO - nobody has looked in any fusion, and nobody has looked in any blood cell. Named per rule 86. The nearest connection is indirect and runs through this graph's own work: MED19, which REST uses to deliver G9a, is curated in IntAct against an engineered MLL-AFF4 chimera - but that co-IP contains no REST, no G9a and no H3K9me2 measurement.
absence classliterature-absence-bounded
absence class noteMIGRATED 2026-09-23, mechanically and not by judgement: the class string itself begins 'literature'. The field previously held the whole verdict as free text and that string is preserved here verbatim because it says more than the token can: 'literature - bounded through SAFE operands only, with counts, querytranslations, id-set comparison, controls and a title-check of every hit; the approved symbol cannot be used as an operand at all, and the absence is stated as an absence within a partial net.'
domains
Interaction with SIN3A32.0Interaction with SIN3A: 32C2H2-type zinc finger 1159.0C2H2-type zinc finger 1: 159NRSE-binding region201.0NRSE-binding region: 201C2H2-type zinc finger 5 (…304.0C2H2-type zinc finger 5 (required for nuclear localization): 304Interaction with RCOR11,009Interaction with RCOR1: 1009C2H2-type zinc finger 91,060C2H2-type zinc finger 9: 1060
PDB IDS
[
  "2CZY",
  "6DU2",
  "6DU3"
]
domains — the numbers behind the chart
[
  {
    "name": "C2H2-type zinc finger 1",
    "start": 159,
    "end": 181,
    "pfam": null
  },
  {
    "name": "C2H2-type zinc finger 5 (required for nuclear localization)",
    "start": 304,
    "end": 326,
    "pfam": null
  },
  {
    "name": "C2H2-type zinc finger 9",
    "start": 1060,
    "end": 1082,
    "pfam": null
  },
  {
    "name": "Interaction with SIN3A",
    "start": 32,
    "end": 122,
    "pfam": null
  },
  {
    "name": "NRSE-binding region",
    "start": 201,
    "end": 212,
    "pfam": null
  },
  {
    "name": "Interaction with RCOR1",
    "start": 1009,
    "end": 1087,
    "pfam": null
  }
]
complex membership
{
  "corepressors": "SIN3A (via 32-122), SIN3B (via 43-57), RCOR1/CoREST (via 1009-1087); the BHC complex at RE1/NRSE sites",
  "g9a_route": "CDYL + REST + WIZ + SETDB1 + EHMT1 + EHMT2 - and the REST-EHMT1/EHMT2 interaction occurs ONLY in the presence of CDYL (PMID 19061646)",
  "mediator_adaptor": "MED19 and MED26 are the two Mediator subunits identified as direct physical and synergistic functional targets of REST in G9a-dependent H3K9me2 silencing (PMID 19049968, carried in gene-med19); the same laboratory has also placed the route on MED12",
  "degradation_and_other": "substrate of FBXW11 and BTRC (SCF F-box proteins); interacts with USP7; interacts with ZFP90 (which inhibits REST repressor activity) and with PRICKLE1 via zinc finger 5",
  "note": "No REST-containing complex has been reported to include KMT2A, a KMT2A fusion or menin."
}
depmap
{
  "source": "DepMap CRISPR (Chronos) via Open Targets Platform GraphQL, fetched 2026-09-22",
  "release": "NOT STATED BY THE API - unverified (rule 83)",
  "is_essential": false,
  "n_screens": 1258,
  "mean_gene_effect": -0.2147,
  "fraction_lines_depleted_below_minus_0_5": 0.052,
  "lymphoid_tissue": {
    "n_lines": 97,
    "mean_gene_effect": -0.1385
  }
}
depmap kmt2a selectivity
{
  "chronos_mean_kmt2a_rearranged": -0.1785,
  "chronos_mean_other_leukaemia": -0.217,
  "difference": 0.0385,
  "pan_essentiality_all_lines": -0.2161,
  "selectivity_rank": 13754,
  "rank_denominator": 17728,
  "percentile": 77.583,
  "direction": "NOT A DEPENDENCY IN EITHER ARM. A 0.0385-unit difference between two near-zero arms; the 78th percentile ranks noise and must never be quoted. A dropout screen would also be expected to MISS a transformation-suppressing repressor entirely, since its loss should if anything improve growth.",
  "cofactor_control": "CDYL, required for the REST-EHMT1/EHMT2 interaction: mean -0.0911 all lines, KMT2A-rearranged -0.1333 against -0.0911, rank 4,136 - also not a dependency.",
  "provenance": "Joined 2026-09-22 from analyses/depmap-kmt2a-selective-scan-full (generated 2026-09-19T10:12:06Z), 11 KMT2A-rearranged and 43 other leukaemia lines; the scan records NO DepMap release (rule 83)."
}
identifier trap
{
  "status": "REGISTRY ROW 13 EXISTS AND IS PARTLY STALE; the PubMed half of this is NEW and contradicts the dispatch brief.",
  "corpus_side": "RE-MEASURED BY THIS BEAT, not quoted from a brief: a case-sensitive word-boundary match for the token reaches 359 of 1,990 node files (2026-09-22), against named_in_entries 217 when row 13 was written. Counting the token immediately preceding each match gives UniProt 250, IntAct 165, Ensembl 91, PMC 72 and HGNC 37 - API references in our own prose. Part of the growth since the row was written is this beat itself, which names the token in seven new entries, so the figure shows the trap persisting and still dominated by API references rather than spreading through the corpus. The gene is invisible to an internal grep.",
  "row_13_clause_now_false": "Row 13's note says 'nothing in this graph is currently about it'. gene-med19, written cycle 54, carries the RE1-silencing transcription factor as load-bearing evidence for its epigenetics field and disambiguates it in its own body text. The row should be updated rather than removed - the trap is live and larger, and only that one clause is stale.",
  "pubmed_side_measured_2026_09_22": {
    "REST[tiab]": 196013,
    "REST[gene]": 216469,
    "REST[gene]_querytranslation": "\"rest protein human\"[Supplementary Concept] OR \"rest protein human\"[All Fields] OR \"rest\"[All Fields] OR \"rest\"[MeSH Terms]",
    "NRSF[tiab]": 501,
    "RE1_silencing_transcription_factor_tiab": 289,
    "finding": "REST[gene] returns MORE than REST[tiab] because the [gene] tag EXPANDS into a disjunction containing the ordinary English word. A field tag does not rescue a symbol that collides with common vocabulary - it makes it worse.",
    "id_set_comparison": "NRSF 501 ids, full name 289 ids, INTERSECTION 81, UNION 709 - 59.2% NRSF-only, 29.3% full-name-only. Both aliases are required; neither alone reaches three-quarters of the reachable literature.",
    "disease_specific_second_collision": "REST[gene] AND \"Wilms tumor\"[tiab] = 74. UniProt lists REST as causative in WILMS TUMOR 6, and a NEPHROGENIC REST is a standard pathological entity in that same literature - so the collision word and the gene's own disease occupy the same papers.",
    "noise_examples": "REST[gene] AND leukemia[tiab] = 676, REST[gene] AND hematopoi*[tiab] = 393, REST[gene] AND MLL[tiab] = 23, REST[gene] AND KMT2A[tiab] = 5 - all unusable.",
    "asymmetry_worth_recording": "gene_exact:REST at UniProt returns exactly ONE reviewed human record. The token is perfectly safe in a structured identifier lookup and catastrophic in a free-text index."
  },
  "safe_practice": "Use NRSF[tiab] AND the quoted full name, take the UNION, and TITLE-CHECK every hit. Title-checking was not optional here: both apparent haematopoietic hits were false positives."
}
disease associations
{
  "wilms_tumor_6": "UniProt DISEASE annotation, database strength only, no primary genetic paper retrieved for this entry. A PAEDIATRIC malignancy - which is the one category of REST association that would matter most to this project and the one whose literature is least reachable, because 'nephrogenic rest' collides with the gene symbol in exactly those papers.",
  "others": "Gingival fibromatosis 5 (GINGF5, autosomal dominant); autosomal dominant deafness 27 (DFNA27), consistent with the SRRM4 splicing-inactivation requirement in inner-ear hair cells."
}
reached for by
[
  "gene-med19 - MED19 and MED26 are the two Mediator subunits REST uses to deliver G9a-dependent H3K9me2 silencing (PMID 19049968); that entry names REST explicitly as the RE1-silencing transcription factor and disambiguates it from the web API",
  "mark-h3k9me3 - the H3K9 mark family and the direction argument",
  "data/symbol-collisions.json row 13 - the token block, which this entry updates rather than rediscovers"
]
How this could bite us back
  • There is no REST-directed intervention and this entry does not propose one; the relevant intervention is on the enzyme REST delivers, and there the direction is against us. UniProt's own wording puts REST-CDYL recruitment of EHMT2 on the side of transformation SUPPRESSION, and mark-h3k9me3 argues H3K9 methylation restrains the MLL-fusion programme - so interfering with this axis is predicted to help the leukaemia.
  • A G9a inhibitor given for the reasons in gene-ehmt2 would also disable this route, and nobody has measured whether the protective arm or the HoxA9-supporting arm dominates in a KMT2A-rearranged cell. That is a live, unmeasured trade-off inside one drug.
  • The searchability problem is itself a risk to any claim made here, including the negative ones: this entry's central absence - no leukaemia, no haematopoietic literature - is bounded through two aliases that overlap by 11% of their union, so the net is demonstrably partial and the bound is correspondingly weak. It is stated as such, and any future beat quoting it must carry that sentence.
  • The paediatric-cancer association is the least verifiable and most important thing in the record: Wilms tumor 6 is a UniProt DISEASE annotation with no primary paper retrieved here, and the literature that would confirm it is the single worst-colliding sub-literature for this symbol, because a nephrogenic REST is a pathological entity in those same papers.
  • Compensation and control layers are dense: REST activity is set by proteasomal degradation (FBXW11, BTRC, USP7), by an inhibitory partner (ZFP90) and by an SRRM4-dependent splice switch that produces a competing isoform. A perturbation of REST protein level is not a perturbation of REST function, and three separate mechanisms can buffer it.
Still open
  1. Is REST expressed and active in a KMT2A-rearranged blast? UniProt says the lymphocytic compartment expresses it at higher levels, on a single 1996 citation, and there is no REST measurement in any haematopoietic cell. One western blot and one RNA-seq lookup would settle whether this entry has a subject in this disease.
  2. Does REST restrain lineage infidelity in this disease? REST is the canonical enforcer of lineage-inappropriate gene silencing and this disease's signature is lineage switch. That pairing has never been tested, and the graph's entire lineage-switch layer contains no REST measurement.
  3. Is CDYL present in a t(4;11) line, and does the REST-CDYL-EHMT2 complex form there? The G9a route this graph half-describes through MED19 requires CDYL, CDYL has no entry here, and neither protein has been measured in a leukaemic cell.
  4. Which Mediator subunit actually carries the route - MED19/MED26 or MED12? The same laboratory has published both, gene-med19 records the contest, and adding the CDYL requirement means the route has three open positions rather than one.
  5. Is the REST-EHMT2 axis transformation-suppressing in leukaemia as UniProt's wording suggests for transformation generally? If so it is a protective axis and the therapeutic implication is negative - which matters because G9a inhibitors exist and this beat's EHMT2 entry records the opposite direction downstream.
  6. How much REST literature is unreachable? NRSF and the full protein name overlap by only 81 of 709 records, so the union is demonstrably incomplete and the approved symbol cannot be counted at all. Any absence recorded for this gene - including this entry's - is an absence within a partial net, and nobody knows how partial.
Every source behind this entry (5)
  1. E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    REST (Q13127, 1,097 aa) is a transcriptional repressor that binds the neuron-restrictive silencer element and represses neuronal gene transcription in non-neuronal cells, restricting neuronal gene expression by associating with the corepressors SIN3A and RCOR1 which recruit histone deacetylase; it carries nine C2H2-type zinc fingers with zinc finger 5 required for nuclear localization, interaction regions for SIN3A at 32-122, SIN3B at 43-57 and RCOR1 at 1009-1087, and an NRSE-binding region at 201-212; it is located in both Nucleus and Cytoplasm with multiple experimental citations for each; it is expressed in neurons and neural progenitors and ALSO at higher levels in the tissues of the lymphocytic compartment including spleen, thymus and peripheral blood lymphocytes; it is a substrate of FBXW11 and BTRC and interacts with USP7; SRRM4-dependent alternative splicing produces isoform 3, which binds NRSE with lower affinity and can oppose isoform 1; and it is listed as causative in Wilms tumor 6, gingival fibromatosis 5 and autosomal dominant deafness 27.

    What this evidence cannot show

    A database record, not a measurement, and an unusually large one whose comments are split across isoforms - REST has multiple SUBCELLULAR LOCATION comment blocks, some scoped to isoform 3, and this entry collapses them into 'Nucleus and Cytoplasm with multiple citations for each' rather than attributing a compartment to an isoform, which the record does not cleanly support. None of the cited localisation papers was read, so rule 91 applies throughout. The Wilms tumor 6 disease association is a UniProt DISEASE annotation and no primary genetic paper for it was retrieved for this entry - it is recorded at database strength only and is flagged in the open questions rather than built on.

    Evidence that argues against this (1)
    • The lymphocytic-compartment expression statement, which is the single most on-topic line in this record for a leukaemia graph, rests on ONE citation (PubMed:8568247) from 1996 in a comment that also says simply 'Ubiquitous', and every other tissue statement in the record is neuronal and carries protein-level evidence. So 'REST is lymphocyte-enriched' is a thirty-year-old mRNA-era assertion sitting inside a record whose weight is entirely neural, and it should not on its own motivate a haematopoietic hypothesis. That is also consistent with the literature: through safe search tokens, REST has no haematopoietic literature at all. UniProt Consortium 2026
  2. E2moderate confidence 3 of 5: One strong study, or several smaller consistent ones.database

    The REST route to the H3K9 methyltransferases requires a cofactor this graph had not recorded: REST interacts with EHMT1 and EHMT2 ONLY in the presence of CDYL, a complex exists containing at least CDYL, REST, WIZ, SETDB1, EHMT1 and EHMT2, and transcriptional repression by REST-CDYL via recruitment of EHMT2 is described as potentially important in transformation SUPPRESSION.

    What this evidence cannot show

    Database-strength only: this is a UniProt curation of a single paper, PMID 19061646, which was NOT retrieved for this entry, so the CDYL requirement should be read from the primary paper before it is built on. The record spells the fifth complex member 'SETB1', which is almost certainly SETDB1; that reading is an inference from context, not a database value. The underlying system is neuronal-gene silencing in non-neuronal cells, and 'may be important in transformation suppression' is a hedged statement about a general mechanism, not a result in any leukaemia.

    Evidence that argues against this (1)
    • Which adaptor carries the G9a route is contested, and this graph already records the contest from the Mediator side: gene-med19 notes that Mediator's contribution to REST silencing has ALSO been placed on MED12 rather than on MED19/MED26, in work from the same laboratory. Adding a CDYL requirement gives the route three disputed or undocumented components - which Mediator subunit, whether CDYL is present in the relevant cell, and whether SETDB1 or EHMT1/2 is the operative methyltransferase - and none of the three has been measured in a KMT2A-rearranged cell. A route with that many open positions is a hypothesis, not a pathway. Oncofusion Knowledge Graph 2026
  3. E3established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    REST[gene] is a WORSE PubMed operand than the untagged form, not a better one: REST[gene] returns 216,469 records and its querytranslation expands to a disjunction including "rest"[All Fields] - the ordinary English word - against 196,013 for REST[tiab], while the only usable operands are NRSF[tiab] at 501 and "RE1-silencing transcription factor"[tiab] at 289; and a second disease-specific collision compounds it, because REST[gene] AND "Wilms tumor"[tiab] returns 74 records in the very disease UniProt lists REST as causing, where a nephrogenic REST is a standard pathological entity.

    What this evidence cannot show

    This measures operand behaviour on one date and does not audit the 216,469 records - the claim is about the translation string, which is verbatim from the API, and about the arithmetic that [gene] returns MORE than [tiab]. It also directly contradicts the dispatch brief that commissioned this entry, which recommended REST[gene] as one of three safe operands; the literature and the API win over the brief, per standing instruction. No claim is made that [gene] behaves this way for other symbols - it almost certainly does not, and the pathology here is that 'rest' is an indexed English word and a MeSH term in its own right.

    Evidence that argues against this (1)
    • The opposite reading is that REST[gene] is behaving correctly and the expectation was wrong: PubMed's [gene] tag is documented to search a gene-symbol field AND to fall back through All Fields, so a symbol that is an English word will always explode. Which makes the useful statement narrower and sharper than 'the tag is broken': for a symbol that collides with ordinary vocabulary, NO field tag rescues it, because the tag expands rather than restricts. The only remedy is a synonym that is not a word - here NRSF - or the full protein name as a quoted phrase, and both must be used because neither reaches most of the literature alone. NCBI PubMed 2026
  4. E4strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database

    Through both safe operands and after title-checking every hit, REST has NO leukaemia literature and NO haematopoietic literature: NRSF[tiab] AND leukemia[tiab] = 1 and that record is a gene-regulatory-network inference algorithm paper; NRSF[tiab] AND hematopoi*[tiab] = 1 and that record is a review of MAPK and nuclear-receptor crosstalk in cancer immunotherapy; NRSF[tiab] AND MLL[tiab] = 0.

    What this evidence cannot show

    Titles and abstracts only; rule 80 applies and a REST measurement inside a supporting figure of a leukaemia paper is not bounded by this. The absence is also bounded by the SAFE operands only - NRSF and the full name - and those two reach a union of 709 records against an unknown true total, because the approved symbol cannot be counted at all. So this is an absence within a partial net, and it is stated that way. The two hits were resolved to titles rather than merely counted, because a control count is a list nobody opens; both turned out to be false positives, which is why the count and the title-check are both recorded.

    Evidence that argues against this (1)
    • A zero in a partially reachable literature is weaker than a zero in a fully reachable one, and the expression data is the reason to keep the question open: UniProt records REST as expressed at higher levels in spleen, thymus and peripheral blood lymphocytes, it is listed as causative in a PAEDIATRIC malignancy, and its documented G9a-delivery route runs through two Mediator subunits one of which is curated against a KMT2A fusion construct. Every one of those is a reason a REST result in leukaemia could exist and be invisible - and the token pathology means it would also be invisible to anyone looking for it. UniProt Consortium 2026
  5. E5strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database

    REST is not a DepMap dependency: mean gene effect -0.2147 across 1,258 screened cell lines with 5.2% of lines depleted below -0.5, and a lymphoid-tissue mean of -0.1385 over 97 lines; CDYL, which its EHMT1/EHMT2 interaction requires, is likewise not a dependency (mean -0.0911, rank 4,136 in this project's KMT2A scan).

    What this evidence cannot show

    Rule 83: the API does not state the DepMap release; 1,258 is REST's own screen count. In this project's KMT2A scan REST is at -0.1785 in KMT2A-rearranged lines against -0.217 in other leukaemia lines - a +0.0385 difference at rank 13,754 of 17,728, ranking noise between two near-zero arms, recorded only so the percentile is never quoted. Critically, the approvedSymbol readback matters more here than anywhere else in this beat: a symbol that is an English word is exactly the case where a resolver could silently return something else, and the readback confirmed REST.

    Evidence that argues against this (1)
    • A viability screen is the wrong assay for a repressor whose documented role is lineage-inappropriate gene silencing, and the direction it would be expected to matter in is the opposite of a dependency. If REST-CDYL-EHMT2 repression is transformation-SUPPRESSING as UniProt's own wording suggests, then REST loss should make cells grow better, not worse - which a dropout screen registers as no effect. The relevant readout would be inappropriate neuronal-gene expression or lineage infidelity, and this graph has an entire lineage-switch layer in which REST has never been measured. UniProt Consortium 2026
Connected to