Oncofusion

start / graph / gene-cbx3

Genemoderate confidence 3 of 5: One strong study, or several smaller consistent ones.Q32-brca1-hr-licensing

CBX3 / HP1-gamma (Q13185, 183 aa) - the EUCHROMATIC HP1 paralogue, and the one CTCF actually prefers: the reader that carries BRCA1/BARD1 onto H3K9-methylated break chromatin, flat in DepMap, and a fusion partner in one KMT2A::AFDN AML patient

also called CBX3 · HP1gamma · HP1-gamma · HP1G · HECH · Q13185 · CBX3_HUMAN · Chromobox protein homolog 3 · Heterochromatin protein 1 homolog gamma · Modifier 2 protein

HP1-gamma is one of three near-identical proteins that read the silencing tag on DNA, and it is the one that sticks to active genes rather than to permanently shut-down regions. A 2026 paper shows it is the specific one that hands the DNA-repair machinery onto a break, which matters because this graph has been reasoning about its cousin HP1-alpha instead.

The same thing, for a scientist

**Identity.** Q13185, `CBX3_HUMAN`, **183 aa**, primary gene name CBX3 with **no UniProt gene synonyms**, alternative protein names *HECH*, *Heterochromatin protein 1 homolog gamma* and *Modifier 2 protein*, 8 PDB entries. Chromo domain 30-88, chromoshadow domain 121-179 [E1]. One reviewed record; `gene_primary` reads back CBX3. **A rule-65 readback failure sits on this gene and it matters for this beat.** The recommended protein name is *'Chromobox protein homolog 3'* and the entry name is `CBX3_HUMAN`. **Neither string contains 'HP1' or 'gamma'.** The gamma identity lives only in an alternative name, and CBX3 carries **no** gene synonym while its paralogue CBX5 carries `HP1A`. So a reader applying the standard defence - fetch the record and read the primary protein name back - gets something that looks like a failed lookup, exactly the DPF2/LMO2 shape already in this project's registry. **The paralogue question, which the brief asked to be kept straight, was answered by the source paper itself.** [E2] tested all three: by co-immunoprecipitation from 293T extracts, **CTCF interacts preferentially with HP1-gamma, modestly with HP1-alpha and weakly with HP1-beta**, and the authors excluded differing antibody sensitivity by repeating it with tagged constructs, where HP1-gamma bound robustly despite having the *lowest* ectopic expression of the three. So the paralogue assignment here is not an inference from which antibody was to hand. **And the compartments diverge the same way.** UniProt's uncoded note for CBX3 reads *'Associates with euchromatin and is largely excluded from constitutive heterochromatin'*, whereas CBX5/HP1-alpha is annotated Chromosome/centromere with coded evidence and is described as a component of centromeric and pericentromeric heterochromatin [E1, E3]. **The paralogue this cascade uses is the euchromatic one** - which fits a break inside an actively transcribed 89 kb gene such as *KMT2A* considerably better than HP1-alpha would, and is a reason not to import Q110's CBX5 reasoning wholesale. **Its role in the cascade.** HP1-gamma binds H3K9me2/me3 at the break through its chromo domain and anchors BRCA1/BARD1 through its chromoshadow domain contacting the PxVxL motif of BARD1 at 569-573; HP1-gamma depletion reduces the BARD1-CTCF association independently of etoposide, and concurrent ATM inhibition with HP1-gamma depletion does not worsen resection or HR beyond HP1-gamma depletion alone [E2]. **Dependency: flat.** Mean **-0.0817** over **1,258** screens, 1.1% of lines below -0.5, none below -1.0; blood mean -0.1088 [E4]. Its paralogue CBX1 is roughly four times deeper in the same call (-0.3494, 16.6% below -0.5) and CBX5 is equally flat (-0.0830). **So the paralogue that matters functionally here is the one with no fitness cost, and the paralogue with a fitness cost is the one nobody has implicated.** **One KMT2A connection exists and it is not a localisation.** In a KMT2A/AFDN-rearranged AML patient, RNA-sequencing identified a previously unknown **CCDC32(15q15.1)/CBX3(7p15.2) gene fusion** present at diagnosis and at relapse, affecting wild-type expression of both genes, and over-expressing it in MV4-11 cells promoted cell-cycle progression [E5]. That is CBX3 as a secondary fusion partner in one patient, not CBX3 at the *KMT2A* locus.

What it looks like
Chromobox protein homolog 3183 aa
ChromoChromo · residues 30–88ChromoshadowChromoshadow · residues 121–1790100

No three-dimensional model is available for this protein, so the map above is the whole picture. That is itself informative: AlphaFold does not model chains this long, and the parts that have been crystallised are held under the entries for the individual domains.

Go deeper
Why the paralogue matters more here than it usually does

This graph already holds gene-cbx5 (HP1-alpha) and an absence entry bounding the reader question for it. Importing that reasoning to HP1-gamma would be wrong in three specific ways, all measured:

CBX3 / HP1-gammaCBX5 / HP1-alpha
compartmenteuchromatin, largely excluded from constitutive heterochromatin (uncoded note)centromeric and pericentromeric heterochromatin (coded, three citations)
CTCF interaction at a DSBpreferential 2modest 2
coded subcellular citations18
ENCODE ChIP-seq4 (GM12878, HCT116, K562)4 (GM12878, H1, HepG2, K562)
DepMap mean-0.082-0.083

The compartment row is the one that changes an argument. KMT2A is a long, actively transcribed gene and its breakpoint cluster region sits in accessible, CTCF- and cohesin-bound chromatin. An HP1 paralogue that is excluded from constitutive heterochromatin and associates with euchromatin is the one that could plausibly be there; the pericentromeric paralogue is the one this graph happened to have written first.

And the third paralogue is the trap. CBX1/HP1-beta is four times deeper in DepMap than either of the others (-0.349 against -0.082 and -0.083, same call, same data version), and it is the paralogue with no role in this cascade. A reader who conflates the family will attribute CBX1's fitness cost to the protein doing the repair work.

What CBX3 is NOT shown to do
  • Not placed at the KMT2A locus in any cell type. CBX3[tiab] AND KMT2A[tiab] returns 1 record (the CCDC32/CBX3 fusion paper), CBX3[tiab] AND MLL[tiab] returns the same 1, HP1gamma[tiab] AND MLL[tiab] returns 0 with a non-empty querytranslation and 'No items found.', and CBX3[tiab] AND leukemia[tiab] returns 3.
  • Not shown in a haematopoietic cell in the cascade. 2 is U2OS and HEK-293T throughout.
  • Not separable from its paralogues by the PEELI reagent, which removes binding to all three chromoshadow domains.
  • Not implicated in KMT2A::AFF1. The one KMT2A-rearranged patient observation is in a KMT2A::AFDN case, and the functional validation used MV4-11, which is KMT2A::AFF1 - so even within that single paper the fusion context of the patient and of the model differ.
Facts and figures
uniprotQ13185
uniprot entry nameCBX3_HUMAN
gene symbolCBX3
gene primary readbackCBX3
protein nameChromobox protein homolog 3
length AA183
n PDB entries8
how the accession was resolvedgene_exact:CBX3 AND organism_id:9606 AND reviewed:true, fetched live 2026-09-22, returned EXACTLY ONE reviewed human record; gene_primary reads back CBX3 and length is asserted at 183 aa. Rule 88 registry read run first over d['collisions'] (177 rows, case-sensitive): CBX3, CBX1, CBX5 and HP1 all return zero rows, so no prior trap was logged for this family.
localizationNucleus, and this is the ONLY coded location on the record - a single ECO:0000269 from PubMed:28977666. For comparison CBX5 carries coded Nucleus (three citations), Chromosome (two) and Chromosome/centromere (three). So CBX3's database localisation rests on one experimental citation while its paralogue's rests on eight.
subnuclear localizationUniProt's UNCODED note is the discriminating statement and rule 91 says to read it: CBX3 'associates with EUCHROMATIN and is largely EXCLUDED from constitutive heterochromatin. May be associated with microtubules and mitotic poles during mitosis (Potential)'. That is the opposite compartment from CBX5/HP1-alpha, annotated as a component of centromeric and pericentromeric heterochromatin. CBX1/HP1-beta's note says only that it is unassociated with chromosomes during mitosis. The compartment relevant to this beat - H3K9-methylated chromatin transiently formed AT A BREAK - is in none of the three notes and comes only from [E2]. Nothing places CBX3 at the KMT2A locus in any cell type.
localization shown for fusionfalse
cell typeU2OS and HEK-293T for the cascade [E2]. ENCODE has 4 released CBX3 ChIP-seq experiments, in GM12878, HCT116 and K562 - two of them blood-lineage - so an occupancy question CAN be asked of the archive for this protein [E6]. The one KMT2A-rearranged human observation is a single AML patient carrying a CCDC32/CBX3 fusion, with functional work in MV4-11 (a KMT2A::AFF1 line) [E5]. No infant material, no B-lineage progenitor, no CBX3 measurement in KMT2A::AFF1 primary cells.
cell stateThree states change what this reader does. **DNA DAMAGE** - HP1-gamma is described in [E2] as 'rapidly and transiently recruited to DSBs in a CTCF-reliant manner', so its occupancy anywhere is a function of damage state and is transient by design. **MITOSIS** - UniProt flags possible microtubule and mitotic-pole association as Potential, and the three paralogues behave differently through mitosis, so a paralogue-blind reagent reports a mixture. **TRANSCRIPTION** - the euchromatic association means CBX3 occupancy tracks active genes, which is the state the KMT2A locus is in.
epigenetic readoutREADER of H3K9me2/me3 through the chromo domain (30-88), and a PROTEIN-PROTEIN ADAPTOR through the chromoshadow domain (121-179), which binds the PxVxL motif of BARD1 at 569-573. It writes nothing and erases nothing. In this cascade it is the node that converts a histone mark into a repair-factor recruitment, which is precisely why an H3K9 methyltransferase inhibitor can block BRCA1/BARD1 loading without touching BRCA1 itself.
mark readH3K9me2, H3K9me3
reader of that markmark-h3k9me3
shown for fusionPARTIAL and not as a localisation: in KMT2A::AFDN AML, as a SECONDARY FUSION PARTNER. A CCDC32(15q15.1)/CBX3(7p15.2) fusion was found by RNA-seq in one KMT2A/AFDN-rearranged patient at diagnosis and relapse, altered wild-type CCDC32 and CBX3 expression, and promoted cell-cycle progression when over-expressed in MV4-11 [E5]. Nothing in KMT2A::AFF1, nothing in infant material, and NO measurement of CBX3 occupancy at the KMT2A locus in any cell type.
archive bound 2026 09 22ENCODE released TF ChIP-seq: CBX3 4 experiments (GM12878, HCT116, K562). So CBX3 occupancy at the KMT2A locus is answerable from public data in two blood-lineage cells with compute and no wet work.
absence classmeasured-not-analysed
absence class reasoningFour ENCODE CBX3 ChIP-seq experiments exist, two in blood-lineage cells, and none has been read at the KMT2A locus. The literature is separately bounded: CBX3[tiab] AND KMT2A[tiab] returns 1 record and it is the CCDC32/CBX3 fusion paper [E5], not a localisation.
gene synonyms in uniprot
[]
identifier trap found here
{
  "trap_1_readback_failure": "Neither the entry name CBX3_HUMAN nor the recommended protein name 'Chromobox protein homolog 3' contains 'HP1' or 'gamma'. The gamma identity is only in an ALTERNATIVE name. A reader applying rule 65 concludes the lookup failed. Same class as DPF2 returning REQU_HUMAN / 'Zinc finger protein ubi-d4', and LMO2 returning RBTN2_HUMAN / 'Rhombotin-2'.",
  "trap_2_asymmetric_synonyms": "CBX5 carries the gene synonym HP1A. CBX3 carries NO gene synonym at all and CBX1 carries only 'CBX'. So a gene_exact query on HP1G or HP1GAMMA cannot reach CBX3 while the equivalent query for alpha can reach CBX5 - the family is unevenly indexed and the unevenness runs against the paralogue this beat needs.",
  "trap_3_the_p25_collision_already_noted_by_Q110": "CBX5's alternative name is 'Antigen p25' and CBX1's is 'Heterochromatin protein p25' and 'p25beta'. Two different paralogues both answer to p25 in the older literature.",
  "trap_4_length_defence_is_weak": "CBX3 183 aa, CBX1 185 aa, CBX5 191 aa - all three within 8 residues, verified live 2026-09-22. verify-accessions.py asserts accession plus length_aa and can catch a CBX3/CBX5 swap only by 8 residues; a CBX3/CBX1 swap is 2 residues, inside the LMO2 row's limit and far inside rule 66's 16. Only gene_primary and the accession discriminate.",
  "registry_status": "NOT in data/symbol-collisions.json as of 2026-09-22 (checked case-sensitively over d['collisions'], 177 rows, zero matches for CBX1, CBX3, CBX5 or HP1). Reported for a row in the hand-back."
}
domains
[
  {
    "name": "Chromo",
    "start": 30,
    "end": 88
  },
  {
    "name": "Chromoshadow",
    "start": 121,
    "end": 179
  }
]
paralogue discrimination
{
  "question": "Which HP1 does this cascade use, and does this graph's existing HP1-alpha reasoning transfer?",
  "answer_from_the_source_paper": "HP1-gamma. [E2] co-immunoprecipitated CTCF against all three endogenous subtypes and found preferential interaction with HP1-gamma, modest with HP1-alpha, weak with HP1-beta; it then repeated the comparison with tagged constructs to exclude antibody-sensitivity differences and HP1-gamma still bound robustly at the lowest expression level of the three.",
  "but_the_BARD1_side_is_NOT_selective": "The BARD1 PEELI mutant 'largely lacks the ability to bind the CSD of ALL HP1 subtypes' [E2]. So selectivity in this cascade is on the CTCF-HP1 arm, not on the HP1-BARD1 arm, and a PEELI experiment cannot attribute anything to gamma specifically.",
  "the_three_accessions_and_lengths": "CBX3/HP1-gamma Q13185 183 aa; CBX1/HP1-beta P83916 185 aa; CBX5/HP1-alpha P45973 191 aa. Verified live 2026-09-22.",
  "compartments": "CBX3 euchromatin, largely excluded from constitutive heterochromatin (uncoded note). CBX5 centromeric and pericentromeric heterochromatin (coded). CBX1 no compartment note beyond mitotic behaviour.",
  "dependency": "CBX3 -0.0817, CBX5 -0.0830, CBX1 -0.3494 across 1,257-1,258 screens - CBX1 roughly four times deeper than either of the others, and CBX1 is the paralogue with no role in this cascade.",
  "what_this_graph_had_instead": "gene-cbx5 (HP1-alpha), written by Q110, and `absence-no-h3k9-writer-or-reader-localised-at-the-kmt2a-locus` bounds the reader question for CBX5. That absence is correct and is about a DIFFERENT paralogue from the one the DSB literature names here. This entry does not contradict it; it adds the paralogue the cascade actually uses."
}
depmap
{
  "n_screens_with_gene_effect": 1258,
  "mean_gene_effect": -0.0817,
  "median_gene_effect": -0.0749,
  "min_gene_effect": -0.6843,
  "max_gene_effect": 0.6011,
  "frac_below_minus_0_5": 0.0111,
  "frac_below_minus_1_0": 0,
  "n_blood_screens": 147,
  "blood_tissue_blocks": [
    "lymphoid tissue",
    "hematopoietic tissue"
  ],
  "blood_mean_gene_effect": -0.1088,
  "blood_frac_below_minus_0_5": 0.0204,
  "n_tissue_blocks_flattened": 29,
  "paralogue_comparison_same_call": {
    "CBX1": -0.3494,
    "CBX5": -0.083,
    "CBX3": -0.0817
  },
  "open_targets_data_version": {
    "year": "26",
    "month": "06",
    "iteration": null
  },
  "depmap_release": null,
  "rule_83": "no DepMap release identifier is present in the payload; the Open Targets data version is recorded and is not a substitute. CBX1's screen count is 1,257 and CBX3's and CBX5's are 1,258 - a one-line difference, which is the gene-specific variation rule 83 describes and not a release difference.",
  "rule_84": "no median-split proportion is reported, and no claim is made that any of these genes falls in any half of any ranking.",
  "live_zero_screen_control": "POLR2A in the same call returned 0 tissue blocks and 0 screens with a passing approvedSymbol readback.",
  "reading": "flat. A flat score in an unstressed screen is the expected result for a redundant reader with two close paralogues, and it cannot discriminate between 'dispensable' and 'buffered by CBX1 and CBX5'. Do not read it as evidence against the cascade."
}
How this could bite us back
  • CBX3 is flat in DepMap (-0.082, 1.1% of 1,258 lines below -0.5) and has two close paralogues, so an HP1-gamma-directed intervention would be both hard to make selective and likely to be buffered - and the paralogue that DOES carry a fitness cost, CBX1 at -0.349, is the one with no role in this cascade. A pan-HP1 reagent would therefore pay CBX1's toxicity to get CBX3's effect.
  • Any experiment in this graph that uses the BARD1 PEELI mutant is pan-HP1 by construction and cannot support an HP1-gamma-specific conclusion. Reporting a PEELI result as an HP1-gamma result would be the same category error as reading a W6/32 signal as an HLA-A signal.
  • This entry does not license reusing this graph's HP1-alpha findings for HP1-gamma or the reverse. `absence-no-h3k9-writer-or-reader-localised-at-the-kmt2a-locus` bounds CBX5 and remains correct for CBX5; it says nothing about CBX3, and CBX3 is the paralogue the DSB literature names.
Still open
  1. ANSWERED IN CYCLE 63, AND THE ANSWER IS NO. All 13 released ENCODE BRCA1, CBX3 and CBX1 ChIP-seq tracks were read at seven KMT2A intervals: ZERO called IDR peaks in 13 of 13, from peak sets holding 280-26,789 peaks genome-wide, and the BCR core reads 0.566-1.235 fold over the genome-wide median of same-width tiles. The exon-11 element looked enriched in two BRCA1 tracks (2.05x, top 3.5% in HeLa-S3) and fell to 0.34-1.25x against 6,000 CTCF anchors of the same cell type, below the anchor median in 10 of 13. A conservative-IDR CTCF peak IS on the element in all six biosamples, so the anchor is there and the resection factors are not. See ana-q35-brca1-cbx3-and-cbx1-are-not-at-the-kmt2a-breakpoint-cluster-in-any-encode-cell. Resting state only - the damage state remains unmeasured in any cell type. Original text: AND THIS QUESTION WAS ALREADY PARTLY FALSE WHEN WRITTEN: gene-cbx5, written in cycle 60, records zero called peaks for CBX3 in K562 and GM12878 in its own open_questions. Two entries contradicted each other for two cycles and neither cited the other. Original text: Is CBX3 enriched at the KMT2A exon-11 CTCF element (GRCh38 chr11:118,488,159-118,489,206) in undamaged K562 or GM12878? Four ENCODE datasets exist, two in blood lines, and nobody has looked - this is a compute-only question.
  2. Does HP1-gamma's euchromatic preference mean the cascade behaves differently at a transcribed locus such as KMT2A than at the pericentromeric heterochromatin where HP1-alpha and SUV39H1 normally work? The source paper's reporters are integrated transgenes and do not address it.
  3. Is the CTCF preference for HP1-gamma over HP1-alpha absolute or quantitative? If quantitative, the paralogue used may be whichever is most abundant in the cell, and abundance in a fetal haematopoietic progenitor is unmeasured.
  4. Is the CCDC32/CBX3 fusion recurrent? One patient in one 16-patient series is the entire evidence base, and a second case anywhere would change whether CBX3 belongs in this graph as a partner as well as a reader.
Every source behind this entry (6)
  1. E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    CBX3 is UniProt Q13185, entry name CBX3_HUMAN, 183 amino acids, primary gene name CBX3 with NO gene synonyms, recommended protein name 'Chromobox protein homolog 3' and alternative names HECH, 'Heterochromatin protein 1 homolog gamma' and 'Modifier 2 protein'; the feature table annotates a Chromo domain at 30-88 and a chromoshadow-subtype Chromo domain at 121-179, and the record cross-references 8 PDB entries; its only coded subcellular location is Nucleus (one ECO:0000269, PubMed:28977666), with an uncoded note stating that it associates with euchromatin and is largely excluded from constitutive heterochromatin and may associate with microtubules and mitotic poles during mitosis.

    What this evidence cannot show

    A database record fetched 2026-09-22. The euchromatin statement is UNCODED, so it is a curator's summary and not an ECO:0000269 experimental annotation - it is quoted because rule 91 says the uncoded comments carry the condition-scoped statements, not because it has the status of a measurement. The single coded citation for nuclear localisation is a thin evidence base compared with CBX5's eight.

    Evidence that argues against this (1)
    • The euchromatin/heterochromatin split between CBX3 and CBX5 is a UniProt curator's summary of an older imaging literature, and HP1 paralogues redistribute on damage, on differentiation and through the cell cycle. A steady-state compartment assignment cannot be read as where the protein is at the moment of a double-strand break, which is the only moment this beat is about. Hwang SY et al. 2026
  2. E2strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    HP1-gamma is the HP1 paralogue in the CTCF-directed HR cascade, and the assignment was tested against the other two. In U2OS and HEK-293T cells, CTCF recruits HP1-gamma, KAP1, SUV39H1, SETDB1 and KDM5A to enable rapid BRCA1/BARD1 accumulation at DSBs. Among the three HP1 subtypes, CTCF interacts preferentially with HP1-gamma, modestly with HP1-alpha and weakly with HP1-beta by co-immunoprecipitation of endogenous proteins; repeating the comparison with ectopically expressed FLAG-tagged subtypes and HA-tagged CTCF, HP1-gamma interacted robustly despite showing the lowest ectopic expression of the three, excluding an antibody-sensitivity artefact. Endogenous HP1-gamma pulls down full-length CTCF and the ZF fragment (246-588) but not the N-terminus or C-terminus. HP1-gamma is rapidly and transiently recruited to DSBs in a CTCF-reliant manner; HP1-gamma depletion reduces the BARD1-CTCF interaction independently of etoposide; and concurrent ATM inhibition with HP1-gamma depletion does not aggravate impaired end resection or reduced HR efficiency beyond HP1-gamma depletion alone.

    CTCF primes repressive chromatin for rapid BRCA1/BARD1 recruitment to drive homologous recombination repair of DNA double-strand breaks. · Hwang SY, Choi D, Choi MJ, Jo HR, Jeong JH, Kang MA, Lee JS · Nucleic Acids Research 2026
    What this evidence cannot show

    U2OS osteosarcoma reporter lines and HEK-293T only; no haematopoietic cell, no fusion, no KMT2A locus. The paralogue comparison is by co-immunoprecipitation abundance, which is a relative-affinity readout in over-expression and in whole-cell extract, not a quantitative binding measurement - 'preferentially, modestly, weakly' is the paper's own gradation and no Kd is reported. The HP1-gamma antibodies used are Millipore 05-690 and Abcam ab217999; no clone-level cross-reactivity data against HP1-alpha or -beta is given, which for a family of three proteins within 8 residues is the standing worry (the CLONE is the identifier, not the label). DOI taken from PubmedData/ArticleIdList only.

    Evidence that argues against this (1)
    • The BARD1 side of the same cascade is explicitly NON-selective - the PEELI mutant 'largely lacks the ability to bind the CSD of all HP1 subtypes' - so the paralogue specificity rests entirely on the CTCF-HP1 co-IP gradient. If CTCF's preference is quantitative rather than absolute, HP1-alpha could substitute in a cell where it is the abundant paralogue, and the DSB literature separately names HP1-beta in other systems. Hwang SY et al. 2026
  3. E3established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    The three human HP1 paralogues are within 8 residues of each other and carry unevenly indexed synonyms: CBX3 Q13185 183 aa with no gene synonyms; CBX1 P83916 185 aa with the single gene synonym CBX and alternative protein names including 'Heterochromatin protein p25' and 'p25beta'; CBX5 P45973 191 aa with the gene synonym HP1A and the alternative protein name 'Antigen p25'. CBX5 carries coded Chromosome/centromere localisation from three citations and is described as a component of centromeric and pericentromeric heterochromatin; CBX1's note states only that it is unassociated with chromosomes during mitosis; CBX3's note states that it associates with euchromatin and is largely excluded from constitutive heterochromatin.

    What this evidence cannot show

    Database records fetched 2026-09-22; each gene_exact query returned exactly one reviewed human record with its primary gene name reading back correctly. The compartment statements for CBX3 and CBX1 are uncoded notes while CBX5's is coded, so the three are not documented to the same standard and the apparent contrast is partly a contrast in curation depth.

    Evidence that argues against this (1)
    • The 8-residue spread across the family means verify-accessions.py cannot catch a CBX1/CBX3 swap (2 residues) and barely catches a CBX3/CBX5 one (8 residues). Length is not a defence in this family, so any downstream entry must carry the accession and rely on gene_primary - the same limitation the PRKAR1A row in the registry records for a pair at zero residues apart. Oncofusion Knowledge Graph identifier registry 2026
  4. E4strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database

    CBX3 is not a CRISPR dependency and its paralogue CBX1 is: flattening every tissue block gives CBX3 1,258 screens, mean -0.0817, median -0.0749, minimum -0.6843, maximum 0.6011, with 1.11% of lines below -0.5 and none below -1.0, and a blood mean of -0.1088 over 147 screens. In the same call CBX5 gives mean -0.0830 over 1,258 screens (0.40% below -0.5) and CBX1 gives mean -0.3494 over 1,257 screens with 16.6% below -0.5 and a blood mean of -0.3187.

    Open Targets Platform GraphQL API, target.depMapEssentiality with all tissue blocks flattened, plus meta.dataVersion · Open Targets Platform; Broad Institute DepMap · Open Targets Platform 2026
    What this evidence cannot show

    Rule 83: no DepMap release identifier in the payload; Open Targets data version year 26 month 06. The 1,257-versus-1,258 difference between CBX1 and its paralogues is one screen and is gene-specific variation, not a release difference. Rule 84: no median-split proportion reported. Live zero-screen control fired - POLR2A returned 0 blocks and 0 screens in the same call. A knockout screen in unstressed culture cannot test a damage-conditional function, and three close paralogues are the textbook case where single-gene knockout underestimates pathway importance.

    Evidence that argues against this (1)
    • A flat gene-effect score for a member of a three-paralogue family is uninformative about requirement, because the redundancy is exactly what the screen cannot see. This figure must not be used to argue that HP1-gamma is dispensable for the cascade; the relevant experiment is a triple depletion or a separation-of-function allele, and neither is in DepMap. Open Targets Platform; Broad Institute DepMap 2026
  5. E5weak confidence 2 of 5: Preliminary, small, indirect, or not yet peer reviewed.paper

    CBX3 appears in KMT2A-rearranged AML as a secondary fusion partner, not as a locus-resident protein. In 16 chromosomal-rearrangement AML patients monitored across diagnosis, refractoriness and relapse, RNA-sequencing of a FISH-diagnosed KMT2A (11q23)/AFDN (6q27)-rearranged case identified a previously unknown CCDC32 (15q15.1)/CBX3 (7p15.2) gene fusion present at both diagnosis and relapse; the fusion significantly affected wild-type expression of both CCDC32 and CBX3 at relapse by quantitative PCR; the chimeric fusion persisted over diagnostic and relapse phases in a 21-year-old male with rapidly relapsed refractory AML; and over-expression of the CCDC32/CBX3 fusion in MV4-11 cells promoted cell-cycle progression, which the authors offer as functional validation of a role in treatment resistance.

    What this evidence cannot show

    ONE patient, in a series of 16, in a 21-year-old male - not an infant and not KMT2A::AFF1 but KMT2A::AFDN. Abstract read; full text not fetched. The functional validation is over-expression of the fusion in MV4-11, a KMT2A::AFF1 line, so the patient's fusion context and the model's fusion context differ within the same paper. A cell-cycle-progression readout is not a DNA-repair readout and this paper makes no claim about HR, HP1 function, or the CTCF cascade. Nothing here places CBX3 protein at the KMT2A locus.

    Evidence that argues against this (1)
    • A single recurrent-in-one-patient RNA fusion found by RNA-seq in a 16-patient series, without an independent cohort, is at high risk of being a private event or a read-through artefact; the authors report no second patient carrying CCDC32/CBX3. This entry cites it as the only CBX3-KMT2A-rearranged connection in the literature, which is a statement about the literature's thinness rather than about CBX3's importance. Xu Y et al. 2025
  6. E6strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database

    ENCODE holds 4 released TF ChIP-seq experiments for target label CBX3, in GM12878, HCT116 and K562 - two of them blood-lineage cells - so CBX3 occupancy at the KMT2A locus is answerable from public data with compute and no wet work. In the same census CBX1 has 2 (HepG2, K562), CBX5 4 (GM12878, H1, HepG2, K562), BRCA1 7, KDM5A 3 (no blood line), and BARD1, EXO1, DNA2, SUV39H1 and RBBP8 have no ENCODE target record at all.

    What this evidence cannot show

    Counted 2026-09-22 on the released TF ChIP-seq facet only; GEO individual depositions, ChIP-Atlas and ReMap were not swept. The count matches Q110's independent census of the same facet one day earlier (4 for CBX3, 2 for CBX1), which is a cross-check rather than an independent confirmation since it is the same endpoint. Crucially, all four experiments are in UNDAMAGED cultured cells, and the cascade this entry is about is damage-conditional and transient - so a re-analysis at the KMT2A locus tests only the resting state.

    Evidence that argues against this (1)
    • Re-analysing these four datasets at the KMT2A locus could return a well-powered zero that is uninformative, for exactly the reason Q108's resting-state H3K9me3 null was: the model predicts the signal appears only after a break. An absence closed this way would need to be labelled as a resting-state absence, not as an absence. Hwang SY et al. 2026
Connected to