Oncofusion

start / graph / gene-aff1-as1

Genemoderate confidence 3 of 5: One strong study, or several smaller consistent ones.Q155-can-an-aff1-promoter-measurement-be-attributed

AFF1-AS1 - the antisense RNA 151 bp from the index fusion partner's TSS, which Ensembl does not recognise and this project's promoter table cannot see

also called AFF1 antisense RNA 1 · LOC100506746 · AFF1 antisense · ENSG00000284968 (Ensembl's unnamed 'Novel transcript, antisense to AFF1')

Right next to AFF1 - the gene that gives this project's index fusion its business end - another gene starts 151 letters away and points the other way. It has never been studied by anyone, and this project's measurement table has no row for it, so every measurement of AFF1's on-switch has silently been a measurement of both.

The same thing, for a scientist

AFF1-AS1 is **NCBI GeneID 100506746**, **HGNC:53447**, approved 2017-04-19, locus type *RNA, long non-coding*, 4q21.3 [E1]. Its only RefSeq transcript is **NR_038841**, three exons, `chr4:86,924,893-86,934,850` on the **minus** strand, 1,946 nt of exon [E2]. Its TSS lies **151 bp** from AFF1's (`chr4:86,935,001`, plus strand, NM_001166693), head to head, so the 2 kb promoter window this project scores for AFF1 (`chr4:86,934,001-86,936,001`) shares **1,849 of 2,000 bp = 92.45%** with an equivalent AFF1-AS1 window [E2]. **That figure, and the GeneID, were carried into this beat as explicitly unverified premises and both are confirmed** - re-derived from NCBI esearch+esummary, HGNC REST and the UCSC refGene track fetched independently this cycle. **But the pair is far less stable than a single number suggests, and that is the substance of this entry.** Ensembl **does not carry the symbol AFF1-AS1 at all** (`xrefs/symbol/homo_sapiens/AFF1-AS1` returns `[]` at HTTP 200 while the same call resolves `AFF1` and `IRX2-DT`), and HGNC's own record for AFF1-AS1 carries **no `ensembl_gene_id` field** [E1][E3]. What Ensembl has at the locus is **ENSG00000284968**, an **unnamed** lncRNA described only as *"Novel transcript, antisense to AFF1"*, spanning `chr4:86,924,630-86,936,202` on the minus strand - **1,352 bp longer at the 5' end than RefSeq's model, which puts its gene-level TSS 1,999 bp DOWNSTREAM of Ensembl's AFF1 TSS, inside AFF1 rather than divergent from it** [E3]. Under RefSeq the two promoter windows overlap **92.45%**; under Ensembl's gene-level spans, **0.05%**. **The same statistic takes essentially the whole range of its possible values depending on which annotation you ask.** Nothing is published about this RNA under any name this beat could construct: `"AFF1-AS1"[tiab]` and `AFF1-AS1[All Fields]` both return **0** in PubMed, Europe PMC's full-text index returns **hitCount 0** for `"AFF1-AS1"` against 651 for `"HOXA-AS2"` and 2,129 for `"AFF1"`, and a 2026 review devoted to non-coding RNAs in KMT2A-rearranged ALL names **seven** lncRNA symbols and not this one, while naming AFF1 twenty-five times [E4][E5].

Go deeper
Identifiers, every one fetched this cycle
fieldvalueroute
NCBI GeneID100506746esearch db=gene, AFF1-AS1[sym] AND human[orgn], querytranslation AFF1-AS1[sym] AND "Homo sapiens"[Organism], count 1
HGNC idHGNC:53447rest.genenames.org/fetch/symbol/AFF1-AS1, numFound 1
approved nameAFF1 antisense RNA 1HGNC
locus typeRNA, long non-codingHGNC locus_type
approved2017-04-19HGNC date_approved_reserved
cytoband4q21.3NCBI maplocation
RefSeqNR_038841 (the only one)HGNC refseq_accession; UCSC refGene and ncbiRefSeq both return exactly one transcript
Ensemblabsent - HGNC record has no ensembl_gene_id key at allHGNC
UniProtnone, correctly - a gene:AFF1-AS1 AND organism_id:9606 search returns a header and zero rowsUniProt REST

The brief that dispatched this beat flagged the GeneID as not independently verified. It is correct. A note worth keeping from Q153: a guessed id, 100874058, returns a well-formed record for COX10-DT, an unrelated gene. The resolution above went through esearch on the symbol, and the querytranslation is recorded so a reader can see which search ran.

Structure: three exons, and no coding potential in either annotation

UCSC hg38 refGene, fetched 2026-09-24 over chr4:86,800,000-87,200,000:

AFF1-AS1  NR_038841  chr4:86,924,893-86,934,850  -  3 exons  cdsStart == cdsEnd (non-coding)

Exons, minus strand, 5' first: 86,934,486-86,934,850 (365 bp), 86,933,394-86,933,542 (149 bp), 86,924,893-86,926,326 (1,434 bp) - 1,948 bp of exon across a 9,957 bp locus.

ncbiRefSeq (the current NCBI release, which carries predicted XM_/XR_ models as well) returns the same single transcript, so NCBI has not extended this gene since the 2020 refGene snapshot the project's table is built from.

Ensembl's model of the locus, ENSG00000284968, has four transcripts, and they do not agree with each other either:

transcriptspan (1-based)TSS (minus strand)distance from AFF1's refGene TSS
ENST0000050828086,924,630-86,936,20286,936,202+1,201 bp, inside AFF1
ENST0000050648486,925,867-86,936,17986,936,179+1,178 bp, inside AFF1
ENST0000050315986,935,451-86,936,20286,936,202+1,201 bp, inside AFF1
ENST0000050926286,933,165-86,934,54286,934,542-459 bp, inside the project's window

So Ensembl places one of its four antisense transcripts in the divergent position RefSeq describes, and three starting on the far side of AFF1's TSS. This is not a coordinate rounding difference; it is a different model of what the gene is.

What is known about its biology: nothing, bounded five ways

Every count below was run this cycle. PubMed counts come through scripts/pubmed_safe.py, which raises rather than returning a zero it cannot explain, and the querytranslation is recorded beside each one.

instrumentquerycounttranslation / note
PubMed"AFF1-AS1"[tiab]0"AFF1-AS1"[tiab]
PubMedAFF1-AS1[All Fields]0AFF1-AS1[All Fields]
PubMed"AFF1 antisense"[tiab]0
PubMed"AFF1 antisense RNA 1"[All Fields]0
PubMedLOC100506746[All Fields]1PMID 22470424, an ALS GWAS - the symbol appears as a locus label, not a subject
PubMed"AF4 antisense"[All Fields]0
PubMedAFF1[tiab] AND antisense[tiab]1PMID 16703585, panhandle PCR breakpoint cloning - off topic
PubMedAFF1[tiab] AND lncRNA[tiab]1PMID 36595475, a leukaemia transcriptome resource - off topic
Europe PMC (full text)"AFF1-AS1"hitCount 0controls through the identical shape: "HOXA-AS2" 651, "IRX2-DT" 4, "AFF1" 2,129
GEO (db=gds)"AFF1-AS1"0quotedphrasesnotfound: ["AFF1-AS1"] - the phrase is not in the index at all; control "HOXA-AS2" returns 24

And the reagent test that matters more than any count. A PubMed zero is bounded by abstracts, so before recording an absence the rule is to open the papers most likely to contain the thing as a supporting panel. The best available one is PMID 41358901, "The hidden regulators: Non-coding RNAs in KMT2A-rearranged acute lymphoblastic leukemia" (Int J Cancer 2026), a review whose entire subject is ncRNAs in this disease. Its full text was fetched from Europe PMC (PMC12922646, 56,262 characters after tag-stripping, with the unicode hyphens normalised to ASCII before searching - the document uses U+2010 and a naive search misses every hyphenated symbol). It names AFF1 twenty-five times and AFF1-AS1 zero times. The lncRNA symbols it does name are HOXA10-AS, LAMP5-AS1, LINC00226, LINC00511, LINC00958, LINC01221 and LINC01226 - seven, and not this one 5.

So the absence is not "we searched and found nothing". It is: the review of exactly this topic, written this year, does not know this transcript exists.

What this project has measured at the locus, and what it means

AFF1-AS1 has no row in this project's 19,404-symbol promoter table, because the table carries one NM_-derived row per gene symbol and AFF1-AS1 has only an NR_ transcript. So it cannot be scored, cannot appear as a comparator, and cannot be counted by any within-table audit.

It can be measured directly, and this beat did (no bigWig was downloaded; pybigtools reads GSE252378's files over HTTP range requests):

intervalwidthKMT2A-N occupancy call
AFF1's 2 kb promoter window (92.45% shared with AFF1-AS1's)2,00020 / 27 samples
the 151 bp an AFF1 window has and an AFF1-AS1 window does not15115 / 27
the 151 bp an AFF1-AS1 window has and an AFF1 window does not1511 / 27
AFF1-AS1's whole gene body9,9570 / 27
a width-matched first 9,957 bp of AFF1's body9,9574 / 27

AFF1-AS1's gene body carries no fusion occupancy in any of the 27 samples, and the width-matched AFF1-body-over-AFF1AS1-body ratio has a median of 2.247 and exceeds 1.0 in 25 of 27 6.

That reads as evidence that the promoter signal belongs to AFF1 - and this beat's own base-resolution profile then showed that reading is wrong, because the signal at this locus is bimodal and neither mode is on AFF1's TSS. See ana-q155-the-kmt2a-n-signal-at-the-aff1-locus-is-bimodal-and-neither-mode-is-centred-on-aff1s-tss. The honest statement is the narrow one: nothing measurable is happening in AFF1-AS1's body; where the promoter signal belongs is a separate question and the answer is not AFF1 either.

Facts and figures
ncbi gene ID100506746
hgnc IDHGNC:53447
gene primaryAFF1-AS1
descriptionAFF1 antisense RNA 1
locus typeRNA, long non-coding
hgnc date approved2017-04-19
cytoband4q21.3
uniprot noteNo UniProt record exists and none should: a REST search gene:AFF1-AS1 AND organism_id:9606 returns a header row and zero records, fetched 2026-09-24. Recorded absent, not guessed.
divergent pair withgene-aff1
tss separation from aff1 bp151
tss separation from aff1 bp ncbi gene level161
promoter window overlap with aff1 PCT refgene92.45
promoter window overlap with aff1 PCT ncbi gene level91.95
promoter window overlap with aff1 PCT ensembl gene level0.05
in project promoter tablefalse
why absent from project tablethe 19,404-row table carries one NM_-derived row per gene symbol; AFF1-AS1 has only NR_038841
absence classmeasured-not-analysed
epigenetic readoutnone published. The only measurement of any kind at this locus is this beat's KMT2A CUT&RUN scoring in GSE252378: 0 of 27 samples occupied over the gene body.
shown for fusionmeasured in KMT2A::AFF1, ::MLLT1, ::MLLT3, ::MLLT10, ::AFDN and ::EPS15 in GSE252378 and NOT occupied over its gene body in any of the 27 samples; nobody anywhere has measured its expression in any fusion
measurements
n_pubmed_records0.000n_pubmed_records: 0n_europepmc_fulltext_reco…0.000n_europepmc_fulltext_records: 0n_samples_occupied0.000n_samples_occupied: 0promoter_window_overlap_p…92.5promoter_window_overlap_pct: 92.45tss_separation151.0tss_separation: 151
hg38
{
  "refgene_transcript": "NR_038841",
  "refgene_span_0based": "chr4:86924893-86934850",
  "strand": "-",
  "tss_0based": 86934850,
  "exons_0based": [
    [
      86924893,
      86926326
    ],
    [
      86933394,
      86933542
    ],
    [
      86934486,
      86934850
    ]
  ],
  "exonic_bp": 1948,
  "n_transcripts_refseq": 1,
  "n_transcripts_ncbirefseq_current": 1
}
ensembl
{
  "symbol_resolves": false,
  "xrefs_symbol_response": "[] at HTTP 200; controls AFF1 -> ENSG00000172493 and IRX2-DT -> ENSG00000186493 resolved in the same session",
  "locus_gene_id": "ENSG00000284968",
  "locus_gene_name": null,
  "locus_description": "Novel transcript, antisense to AFF1",
  "biotype": "lncRNA",
  "span_1based": "chr4:86924630-86936202",
  "strand": -1,
  "transcript_tss_1based": [
    86936202,
    86936179,
    86936202,
    86934542
  ],
  "hgnc_carries_ensembl_gene_id": false
}
measurements — the numbers behind the chart
[
  {
    "quantity": "tss_separation",
    "subject": "AFF1-AS1 TSS to AFF1 TSS, head to head, opposite strands",
    "value": 151,
    "units": "bp",
    "n": 2,
    "universe": "hg38 refGene NR_038841 txEnd 86,934,850 against NM_001166693 txStart 86,935,001, 0-based",
    "null": null,
    "note": "161 bp from NCBI Gene-level spans; Ensembl's gene-level model puts the antisense TSS 1,999 bp the OTHER side of AFF1's TSS"
  },
  {
    "quantity": "promoter_window_overlap_pct",
    "subject": "AFF1's 2 kb project window against an equivalent AFF1-AS1 window, under three annotations",
    "value": 92.45,
    "units": "percent of a 2,000 bp window",
    "n": 3,
    "universe": "refGene 92.45%, NCBI Gene-level 91.95%, Ensembl gene-level 0.05%; project window chr4:86,934,001-86,936,001",
    "null": 21.6,
    "note": "the null is the share of all 19,404 project windows containing another gene's TSS (Q153). The three-annotation spread is the point: the statistic is not annotation-invariant."
  },
  {
    "quantity": "n_pubmed_records",
    "subject": "AFF1-AS1 under seven names, PubMed",
    "value": 0,
    "units": "records",
    "n": 7,
    "universe": "PubMed via pubmed_safe esearch, 2026-09-24; names AFF1-AS1, AFF1-AS, 'AFF1 antisense', 'AFF1 antisense RNA 1', LOC100506746 (1 off-topic hit), 'AF4 antisense', 'MLLT2 antisense'",
    "null": 99,
    "note": "null is \"HOXA-AS2\"[tiab] = 99, a comparable haematopoietic antisense RNA, through the identical query shape"
  },
  {
    "quantity": "n_europepmc_fulltext_records",
    "subject": "the quoted phrase \"AFF1-AS1\" in Europe PMC, which indexes open-access full text",
    "value": 0,
    "units": "records",
    "n": 1,
    "universe": "Europe PMC REST search, 2026-09-24; controls \"HOXA-AS2\" 651, \"IRX2-DT\" 4, \"AFF1\" 2129",
    "null": 651,
    "note": "a full-text zero is much stronger than an abstract zero; this is the tightest bound in the entry"
  },
  {
    "quantity": "n_samples_occupied",
    "subject": "AFF1-AS1 gene body (chr4:86,924,893-86,934,850, 9,957 bp), KMT2A-N1+N2, GSE252378",
    "value": 0,
    "units": "samples",
    "n": 27,
    "universe": "27 KMT2A-fusion samples; rule >= 2.0x in both KMT2A-N antibodies AND above the per-library max of eight width-matched tissue-restricted loci",
    "null": null,
    "note": "AFF1's width-matched first 9,957 bp scores 4 of 27 under the same rule"
  }
]
How this could bite us back
  • Any promoter-directed intervention at AFF1 - a CRISPRi tile, a steric-blocking oligonucleotide, an enhancer deletion - necessarily engages AFF1-AS1's promoter too, because 92.45% of the sequence is shared. A selective AFF1 promoter perturbation does not exist at the DNA level, and a phenotype from one cannot be attributed to AFF1.
  • The converse is a real mechanism rather than a caveat: if the KMT2A fusion drives AFF1-AS1 rather than AFF1, a programme built on 'the fusion autoregulates its own partner' would be chasing the wrong transcript, and no 2 kb readout could tell the difference. This beat's data cannot exclude it - AFF1-AS1's body is empty, but so is AFF1's at this threshold.
  • Because nothing is published about this RNA, the off-target arm of any AFF1-promoter experiment has no literature to predict it from. That is a reason to measure AFF1-AS1 first, not a reason to ignore it.
Still open
  1. Is AFF1-AS1 transcribed at all in KMT2A::AFF1 leukaemia? No stranded RNA-seq in any deposit this project uses has been queried for it, and a single strand-aware coverage lookup over chr4:86,924,893-86,934,850 in an existing infant KMT2A-r RNA-seq deposit would answer it with no wet work. This is the cheapest open question in the entry.
  2. Are RefSeq's NR_038841 and Ensembl's ENSG00000284968 the same transcription unit? They share the locus and the strand and differ by 1,352 bp at the 5' end, which is the difference between a divergent antisense RNA and an internal antisense RNA - two different mechanisms. Nobody has adjudicated it and CAGE data would.
  3. Does AFF1-AS1 have a promoter of its own, or does it share AFF1's? The 151 bp separation is below the resolution of any occupancy assay in this project, and only a nascent-transcription assay (PRO-seq, GRO-cap) could place the two initiation sites independently.
Every source behind this entry (6)
  1. E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    AFF1-AS1 is NCBI GeneID 100506746 and HGNC:53447, approved 2017-04-19, with HGNC locus_type 'RNA, long non-coding', location 4q21.3, entrez_id 100506746 and refseq_accession NR_038841; the HGNC record carries no ensembl_gene_id field.

    HGNC record for AFF1-AS1 (HGNC:53447), fetched via the HGNC REST service · HUGO Gene Nomenclature Committee, rest.genenames.org · HGNC 2026
    What this evidence cannot show

    A database record fetched 2026-09-24, not a paper. The absence of ensembl_gene_id is an assertion about THIS record as returned on this date; HGNC adds Ensembl mappings over time and this one may acquire it. The GeneID was resolved by esearch on AFF1-AS1[sym] AND human[orgn] (querytranslation read back as 'AFF1-AS1[sym] AND "Homo sapiens"[Organism]', count 1), not typed from memory or copied from a sibling entry.

    Evidence that argues against this (1)
    • An HGNC approval is a nomenclature decision, not a demonstration that a transcript is made, is stable, or does anything. HGNC approves antisense symbols on annotation evidence alone. So 'AFF1-AS1 is a gene' is a statement about a naming committee, and the biology behind it is exactly what E4 and E5 show is absent. NCBI Gene 2026
  2. E2established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    In hg38 refGene, AFF1-AS1 is the single transcript NR_038841 on the minus strand at chr4:86,924,893-86,934,850 with three exons and cdsStart equal to cdsEnd (non-coding), so its TSS is 151 bp from AFF1's (NM_001166693, plus strand, txStart 86,935,001) and the project's 2 kb AFF1 window chr4:86,934,001-86,936,001 shares 1,849 of 2,000 bp (92.45%) with an equivalent AFF1-AS1 window; NCBI Gene's gene-level spans give 161 bp and 91.95%.

    UCSC Genome Browser hg38 refGene and ncbiRefSeq tracks, chr4:86,800,000-87,200,000, with NCBI Gene esummary for GeneIDs 100506746 and 4299 · UCSC Genome Browser, api.genome.ucsc.edu; NCBI Gene E-utilities · UCSC Genome Browser / NCBI Gene 2026
    What this evidence cannot show

    UCSC txStart/chromStart are 0-based half-open and txEnd is the 1-based end, so the minus-strand TSS is txEnd and the plus-strand TSS is txStart; the 151 bp is the 0-based difference and the TSS-to-TSS distance counted in 1-based coordinates is 152. The 92.45% is a property of this project's 2 kb window convention as much as of the genome: a 500 bp window would share 69.8% and a 5 kb window 97.0%. refGene here is the same snapshot the project's promoter table is built from (dataTime 2020-08-17 per Q153), which is why it is the right annotation for describing what the project actually measures and the wrong one for describing the genome today.

    Evidence that argues against this (1)
    • Divergent promoter pairs are ordinary: bidirectional promoters separated by under 1 kb were estimated at more than 10% of human genes, so this geometry is not special to AFF1 and does not by itself imply shared regulation. What it implies is a measurement limit, which is the only claim made here. Trinklein ND et al. 2004
  3. E3established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    Ensembl does not carry the symbol AFF1-AS1: xrefs/symbol/homo_sapiens/AFF1-AS1 returns an empty array at HTTP 200 while the identical call resolves AFF1 to ENSG00000172493 and IRX2-DT to ENSG00000186493; what Ensembl has at the locus is the unnamed lncRNA ENSG00000284968, described as 'Novel transcript, antisense to AFF1', spanning chr4:86,924,630-86,936,202 on the minus strand with four transcripts whose TSSs are 86,936,202, 86,936,179, 86,936,202 and 86,934,542.

    What this evidence cannot show

    Ensembl REST returned HTTP 500 and HTTP 503 on four attempts during this beat before serving these records, and a failed fetch is an instrument failure rather than an absence, so every statement here rests on a response that was actually received and saved (q155_ens_region.json, q155_ens_tx.json). The empty xrefs result is NOT treated as an instrument failure because the identical call on two control symbols returned records in the same session. Whether ENSG00000284968 and AFF1-AS1 are 'the same gene' is a curation question nobody has adjudicated; they share the locus and the antisense orientation and differ by 1,352 bp at the 5' end.

    Evidence that argues against this (1)
    • The directional claim - that Ensembl puts the antisense TSS inside AFF1 rather than divergent from it - is true of three of Ensembl's four transcripts and FALSE of the fourth, ENST00000509262, whose TSS at 86,934,542 sits 459 bp inside the project's AFF1 window on the divergent side. So the two annotations are not simply in opposition; Ensembl contains RefSeq's reading as a minority model. Quoting only the 0.05% gene-level overlap would overstate the disagreement. UCSC Genome Browser et al. 2026
  4. E4strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.dataset

    A PubMed search returns zero records for AFF1-AS1 under every name this beat could construct, and Europe PMC's full-text index returns hitCount 0 for the quoted phrase, against 651 for HOXA-AS2, 4 for IRX2-DT and 2,129 for AFF1 through the identical query shape.

    What this evidence cannot show

    This is a bound on a NAME LIST, not on the biology. The names tried were AFF1-AS1, AFF1-AS, 'AFF1 antisense', 'AFF1 antisense RNA 1', LOC100506746, 'AF4 antisense', 'MLLT2 antisense'; a paper describing an uncharacterised antisense transcript by coordinate, or calling it something else entirely, would be invisible to all of them. Two of the queries this script labelled 'controls' - "IRX2-DT"[tiab] and IRX2[tiab] AND antisense[tiab] - returned zero; they were mislabelled by me and are comparators, not controls, and the genuine positive controls (AFF1 226, AF4 1219, MLLT2 6, HOTAIR+antisense 633, "HOXA-AS2" 99, KMT2A+lncRNA 9) all returned large values through the same shapes, which is why the zeros above are recorded as real. The GEO query is the archive check rule 47 requires and it returned quotedphrasesnotfound rather than a bare zero, which is the stronger form of negative.

    Evidence that argues against this (1)
    • A zero in PubMed and Europe PMC bounds what has been REPORTED, not what has been measured. Any RNA-seq of a KMT2A::AFF1 sample contains reads over this locus; the absence is measured-not-reported at worst and measured-not-analysed at best, not never-measured. The cheap closing move is a stranded RNA-seq lookup in an existing deposit, not a new experiment. NCBI GEO DataSets / E-utilities 2026
  5. E5strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.review

    A 2026 review devoted to non-coding RNAs in KMT2A-rearranged acute lymphoblastic leukemia names AFF1 twenty-five times in its full text and AFF1-AS1 zero times, and the seven lncRNA symbols it does name are HOXA10-AS, LAMP5-AS1, LINC00226, LINC00511, LINC00958, LINC01221 and LINC01226.

    The hidden regulators: Non-coding RNAs in KMT2A-rearranged acute lymphoblastic leukemia. · Poersch MA, Rodrigues AC, Stricker PEF, Azevedo ALK, Bruschi DP, de Oliveira JC · Int J Cancer 2026
    What this evidence cannot show

    A review is a map, not a primary source, and this one is cited here PRECISELY for what it does not contain, which is the weakest kind of citation unless the instrument is stated. The instrument: Europe PMC fullTextXML for PMC12922646, HTTP 200, 176,836 bytes, <body> present, 56,262 characters after stripping tags first and unescaping entities second, and EVERY unicode dash (U+2010, U+2011, U+2012, U+2013, U+2014, U+2212) normalised to ASCII hyphen before searching - the document uses U+2010 and an ASCII-hyphen search for 'AFF1-AS1' would have returned a meaningless zero for a different reason. A review can omit something that is published; this bounds the field's attention, not the literature.

    Evidence that argues against this (1)
    • The review does not name C4orf36 either, and C4orf36 IS a protein-coding gene with a current-RefSeq TSS 269 bp from AFF1's. So the review's silence is about the whole neighbourhood rather than specifically about an antisense RNA, which weakens any inference that AFF1-AS1 in particular has been considered and dismissed. UCSC Genome Browser et al. 2026
  6. E6moderate confidence 3 of 5: One strong study, or several smaller consistent ones.dataset

    In GSE252378, AFF1-AS1's 9,957 bp gene body is occupied in 0 of 27 KMT2A-fusion samples under the project's two-antibody rule with a width-matched floor, the 151 bp unique to an AFF1-AS1 promoter window is occupied in 1 of 27, and the width-matched AFF1-body-over-AFF1AS1-body ratio has a median of 2.247 and exceeds 1.0 in 25 of 27 samples.

    Q155 interval deconvolution over all 133 GSE252378 libraries, read remotely without downloading any bigWig · Iqbal Lab oncofusion knowledge graph, beat Q155 · this project 2026
    What this evidence cannot show

    There is no spike-in in this deposit, so every value is a within-sample share and cannot separate low target abundance from a shallow library. The run is complete - 133 of 133 libraries, zero failures, asserted before any verdict was computed - but the floor is the maximum over eight tissue-restricted loci at the same width, which is a conservative floor and not a null distribution. A ratio of body means over a 9,957 bp interval says nothing about where inside the interval the signal is; the base-resolution profile in the sibling entry does, and it does not support the directional reading this ratio suggests.

    Evidence that argues against this (1)
    • A zero in AFF1-AS1's gene body is weak evidence that the promoter signal is AFF1's, because the assay is unstranded protein occupancy on DNA, not transcription. A divergent promoter is ONE piece of DNA, and an occupancy measurement at it has no gene to belong to. The gene-body asymmetry tests whether an elongation complex travels into one transcription unit, which is a different and narrower question. Core LJ et al. 2008
Connected to