HDAC1 and HDAC2 belong to at least five different corepressor complexes, so an HDAC1/2 observation names no complex - and this graph carried both enzymes without the scaffolds that would tell them apart
also called NuRD versus Sin3/HDAC · the shared HDAC1/2 core · why an HDAC readout is ambiguous
HDAC1 and HDAC2 are the erasers that rub acetyl marks off histones, and several completely different machines use the same two erasers. So finding HDAC1 somewhere tells you an eraser is present - it does not tell you which machine brought it, and the machines silence different genes and respond differently to drugs.
The same thing, for a scientist
The NuRD and Sin3 histone-deacetylase complexes share a four-protein core - HDAC1, HDAC2, RBBP4 (RbAp48) and RBBP7 (RbAp46) - whose deacetylase activity in isolation is severely compromised; what makes each complex what it is, and what restores activity, is the scaffold around that core [E1]. Later chemoproteomic profiling of sixteen HDAC inhibitors against intact megadalton complexes rather than purified catalytic subunits found HDAC1/2 in **NuRD, Sin3, NCoR, CoREST and a then-novel mitotic deacetylase complex (MiDAC)**, all scaffolded by ELM-SANT-domain subunits, and showed the complexes are **pharmacologically distinguishable** - aminobenzamides bind the HDAC-NCoR complex more strongly than the HDAC-Sin3 complex - concluding that HDAC-inhibitor selectivity must be evaluated in the context of complexes and not catalytic subunits [E2]. This graph's exposure to that ambiguity was structural rather than accidental: it carried `gene-hdac1`, `gene-hdac2`, `gene-rbbp4` and `gene-rbbp7` - all four shared subunits - plus `gene-chd4` described as "the NuRD ATPase", and **none** of the subunits that distinguish the complexes: no MTA, no MBD, no GATAD2, no SIN3A. HDAC1 is named in 60 node files. The distinguishing measurement this beat ran makes the point concretely: in the pan-MLL-fusion AP-MS network the shared HDAC1/2 + RBBP4/7 core is **0 of 4** while Sin3-specific subunits score 4 of 17 and NuRD remodelling-module subunits 5 of 7 [E3] - so in that dataset the scaffolds are informative and the shared enzymes carry no information at all.
The concrete difference: two complexes, one core
| NuRD | Sin3/HDAC | |
|---|---|---|
| scaffold | MTA1/MTA2/MTA3 — BAH + ELM2 + SANT | SIN3A or SIN3B — PAH1-3 + HID |
| remodelling ATPase | CHD3/CHD4/CHD5 | none |
| deacetylase | HDAC1, HDAC2 | HDAC1, HDAC2 |
| histone chaperone | RBBP4, RBBP7 | RBBP4, RBBP7 |
| DNA-modification reader | MBD2 (5mC); MBD3, which does not read 5mC | none |
| adaptors | GATAD2A/GATAD2B (p66-alpha/beta), CDK2AP1 | SAP18, SAP30, SUDS3/SDS3, ARID4A/ARID4B, ING1/ING2 |
| how it is delivered to DNA | methyl-CpG reading and nucleosome remodelling | sequence-specific repressors docking the PAH domains |
The operational rule. An observation of HDAC1 or HDAC2 - a co-IP band, a mass-spectrometry row, a ChIP peak, an inhibitor response - is consistent with at least five complexes. To name one you need a scaffold: an MTA or a GATAD2 or an MBD for NuRD; SIN3A or SIN3B or SUDS3 or SAP30 for Sin3. The same holds for RBBP4 and RBBP7, which are in PRC2 and CAF-1 as well, and which this graph already carries in a PRC2 folder.
Why a shared core is a trap specifically for this project
This graph's recurring failure mode is the inference that complex membership transfers a property. An existing entry records it in its own bite_back: adopting "complex membership transfers a chromatin readout to the scaffold" as an annotation standard "would credit large parts of the corpus on the epigenetics dimension without any new measurement."
A shared core makes that inference worse in both directions.
- Forward: from "HDAC1 is here" to "NuRD is here" is a leap across a four-way ambiguity. HDAC1 is named in 60 node files in this corpus.
- Backward: from "NuRD is here" to "deacetylation is happening here" fails too, because the isolated shared core has severely compromised activity 1 and because the two NuRD sub-modules are separable and independently active - so a NuRD subunit can be present with no deacetylase module attached 4.
And the measurement this beat ran shows both failures would have fired on real data: in the pan-MLL-fusion network the scaffolds are present and the shared enzymes are not 3.
What follows for a therapeutic argument
Do not treat an HDAC inhibitor as a complex-directed agent unless the proposal says how complex selectivity would be achieved and demonstrated. The chemoproteomic evidence that complexes can be discriminated is a demonstration in cell extracts against an immobilised ligand 2; no clinical HDAC inhibitor is marketed on complex selectivity, and no HDAC inhibitor trial in this graph is designed around one. The destructive half of that paper - that subunit-level selectivity claims are meaningless - is the part safe to rely on.
The constructive corollary is where a real opportunity sits: the scaffolds are what differ, so the scaffolds are where selectivity would have to come from - and they are precisely the proteins with no chemical matter. MTA2 has zero PDB entries, SIN3A has zero PDB entries, and the only published molecule anywhere in this beat is a peptide that disrupts the p66-alpha-MBD2 coiled coil in an erythroid system.
| the operational rule | To name a complex from an HDAC1/2 observation you must have observed a SCAFFOLD: an MTA, an MBD or a GATAD2 for NuRD; SIN3A, SIN3B, SUDS3, SAP30 or an ARID4 for Sin3. RBBP4 and RBBP7 do not count - they are in PRC2 and CAF-1 as well. CHD3/CHD4 do not fully count either, because a CHD3/CHD4-family ATPase has documented NuRD-independent activity. |
|---|---|
| relationship to existing entries | NEW, and it is the entry the beat's dispatch asked for. It does not restate gene-hdac1 or gene-hdac2, which own their own biology; it states what those entries cannot, namely that their subject is shared. It is the concept counterpart of protein-nurd-complex and gene-sin3a, which carry the two complexes as objects. It generalises the caution already recorded in mechanism-q181's bite_back - that complex membership must not transfer a chromatin readout to a scaffold - into the specific case where the SHARED subunit is the one being observed. |
shared subunits
[ "HDAC1", "HDAC2", "RBBP4", "RBBP7" ]
complexes containing hdac1 2
[ "NuRD", "Sin3/HDAC", "NCoR/SMRT", "CoREST", "MiDAC" ]
distinguishing subunits
{
"NuRD": [
"MTA1",
"MTA2",
"MTA3",
"MBD2",
"MBD3",
"GATAD2A",
"GATAD2B",
"CHD3",
"CHD4",
"CHD5",
"CDK2AP1"
],
"Sin3/HDAC": [
"SIN3A",
"SIN3B",
"SUDS3",
"SAP30",
"SAP18",
"ARID4A",
"ARID4B",
"ING1",
"ING2",
"BRMS1",
"BRMS1L",
"PHF12",
"MORF4L1"
]
}corpus exposure before this beat
{
"shared_subunits_with_entries": "ALL FOUR - gene-hdac1, gene-hdac2, gene-rbbp4, gene-rbbp7",
"nurd_distinguishing_subunits_with_entries": "NONE. gene-chd4 existed and is the ATPase, which is NuRD-family but has documented NuRD-INDEPENDENT activity in Drosophila.",
"sin3_distinguishing_subunits_with_entries": "NONE. gene-ing2 existed but was written as a PHD-finger reader in a writers-and-readers beat, not as a Sin3 subunit.",
"word_boundary_naming_counts_2026_09_24": "HDAC1 named in 60 node files, HDAC2 in 22, RBBP4 in 17, RBBP7 in 14, CHD4 in 38 - against MTA2 in 1, MBD3 in 1, GATAD2A in 4, SIN3A in 7, all of them incidental. Counted with scripts/beat-inventory.py.",
"why_this_matters": "Every one of those 60 HDAC1 mentions is, on its own, consistent with five complexes. The graph had maximal exposure to the ambiguity and zero means of resolving it."
}measurements
[
{
"quantity": "subunits_present",
"subject": "the four subunits shared by NuRD and Sin3/HDAC (HDAC1, HDAC2, RBBP4, RBBP7) in the Skucha pan-MLL-fusion network",
"value": 0,
"units": "subunits",
"n": 4,
"universe": "960-protein network, union over seven MLL-fusion baits, top ~291-293 preys per bait",
"null": 0.19,
"note": "null is 4 x 960 / 20431 against the proteome background; complex-specific scaffolds in the same dataset score 5 of 7 (NuRD remodelling) and 4 of 13 (Sin3-specific)"
},
{
"quantity": "node_files_naming_the_symbol",
"subject": "HDAC1 versus the NuRD- and Sin3-distinguishing scaffolds in this corpus before this beat",
"value": 60,
"units": "node files (word-boundary matched)",
"n": 3086,
"universe": "all node files in data/graph/nodes as of 2026-09-24, counted with scripts/beat-inventory.py",
"null": null,
"note": "against MTA2 in 1, MBD3 in 1, GATAD2A in 4 and SIN3A in 7 - all incidental. HDAC2 22, RBBP4 17, RBBP7 14, CHD4 38."
}
]- Every HDAC-inhibitor proposal in this graph inherits this ambiguity: the drug hits a catalytic subunit shared by at least five corepressor complexes in every cell in the body, so 'targeting NuRD with an HDAC inhibitor' is not a mechanism, it is a hope.
- The subunits that WOULD give selectivity - MTA2, SIN3A, the MBDs, the GATAD2s - have no chemical matter and, for MTA2 and SIN3A, no experimental structures at all. Selectivity and tractability point in opposite directions here.
- Reading an HDAC1 signal as NuRD would let this graph credit itself on the epigenetics dimension without any new measurement - the exact error an existing entry's bite_back warns against. This concept exists to make that error visible, and it will only work if entries that mention HDAC1 are actually checked against it.
- How many of this corpus's 60 HDAC1 mentions actually name a complex? A pass over them asking 'is a scaffold subunit named in the same entry?' would turn this concept into a measurement, and would produce a list of entries that need qualifying.
- Which HDAC1/2 complex, if any, is engaged at KMT2A::AFF1 target genes? No experiment in this graph distinguishes them at any locus in any KMT2A-rearranged cell, and a scaffold-directed ChIP - an MTA and a SIN3A in the same t(4;11) line - would be the first.
- Does complex-selective HDAC inhibition do anything in this disease? The chemoproteomic work says complexes are pharmacologically distinguishable and nobody has used that in a KMT2A-rearranged system; an aminobenzamide-versus-hydroxamate comparison in a t(4;11) line is a cheap first look.
- Is MiDAC relevant here? It was novel when discovered and is the least-characterised of the five; this graph has no entry for it and no beat has asked whether it appears in any MLL-fusion dataset.
HDAC1 belongs to at least five corepressor complexes; an HDAC1 observation names none of them
same shared-membership ambiguity as HDAC1
RBBP4 is in NuRD, Sin3/HDAC, PRC2 and CAF-1, so it does not name a complex either
the NuRD side of the distinction
the Sin3/HDAC side of the distinction
- part of →Plain-English: chromatin and epigenetics — the sticky notes on the DNA, and which ones matter here
a reading rule for every acetylation claim in the graph