All findings

RBM10 + CDKN1B

RBM10 and CDKN1B co-occurrence in bladder cancer (MSK-IMPACT 50K)

Novel lead: held up under a stratified controlCo-occurrence · Evidence: pattern across patients, not yet tested within subtypes

DataMSK-IMPACT 50K (2026) · Bladder cancer · 1,917 tumours · both altered in 9 (1.4 expected if independent)

Engine's conclusion

Novel lead. Significant, with a real effect in a consistent direction, and it still holds when tumours are compared only within the same tumour type (and within the same molecular subtype, wherever this cancer's subtypes are known in the data). No artifact check failed.

On the map: An early signal. Neither its statistical strength nor its expected value is high enough yet to count as a discovery.

Called novel: a PubTator3 search finds no title or abstract naming both RBM10 and CDKN1B in bladder cancer. A relationship reported only in a paper's full text would not appear in this search. See the PubTator3 search.

Signal (x) is the corrected significance on the map's scale, discounted from 7% to 3% because the cohort-composition confound is not yet controlled. Efficacy (y) is credibility times actionability.

Structure & site3D structure: AlphaFold

These genes are altered together more often than chance would predict.

Primary site

Bladder

This finding's tumour type arises in the highlighted organ.

No structure profile is curated for this gene.

RBM10Gene

A human gene in this finding. Not in the curated driver set, so no structured profile is shown.

RBM10 mutations in bladder cancer →RBM10 co-mutations by tumour type →Other findings with RBM10 →

No structure profile is curated for this gene.

CDKN1BGene

A human gene in this finding. Not in the curated driver set, so no structured profile is shown.

Other findings with CDKN1B →

Anatomical figure from the EBI Expression Atlas anatomogram, and predicted structures from the AlphaFold Protein Structure Database (both CC-BY-4.0). A model shows the protein's healthy fold; a highlighted residue marks a recurrent cancer position, not a prediction of a specific mutation's effect.

Statistical evidence
Contingency table: the source of the q1,917 tumours

The raw 2×2 the FDR q and log₂ odds ratio above were computed from. It is the immutable evidence the score re-derives from: every number on this page traces back to these four counts.

Gene stateRBM10 alteredRBM10 wild-type
CDKN1B altered914
CDKN1B wild-type1111,783

both 9 (expected 1.4 if independent) · CDKN1B-only 14 · RBM10-only 111 · neither 1,783

Sources

Weak evidence. Below the α=0.05 reject threshold (e≥20). Unlike a single-look p, this stays valid under the engine's continuous re-testing.

Why it sits here on the map

Molecular-subtype certification is unresolved. Recorded lineage only. Within-lineage molecular subtype remains unresolved. The association remains visible, but does not qualify as a subtype-controlled discovery.

The two axes are variables: signal (x) and efficacy (y = credibility × actionability). A point high on both lands in the frontier (top-right). A strong signal with low credibility sits low and to the right: statistically strong, not worth pursuing.

HypothesisModel-generated hypothesis (not evidence)
Written by gpt-6-luna

A language model wrote this from the evidence listed below. It is annotation: the engine's verdict above comes only from the measured statistics, never from this text.

The RBM10–CDKN1B co-occurrence across bladder-cancer patients is most likely driven by residual molecular-subtype composition: a subtype enriched for alterations in both genes could produce the population-level association even after lineage and overall alteration burden are accounted for, without implying that the alterations cooperate within the same tumour.

Argument strength (model self-report)16%
After adversarial review16%
The argument
  1. 1The association is a substantial but not definitive population-level signal: the within-stratum log2 odds ratio is 3.4 (95% CI 2.1–4.6), with 9 double-altered tumours, and it survives FDR correction at q=0.039. Burden-aware testing reduces concern that it merely reflects generally mutation-heavy tumours.E1E19
  2. 2Residual molecular-subtype composition is the leading explanation because lineage was recorded, but molecular subtype remains unresolved; the within-lineage analysis does not rule out subtype confounding. The Cybergenic corpus directly converges with this interpretation for the same pair and cancer (E16). Its other findings provide only contextual, not pair-specific, support: E15 and E18 also favor subtype composition for different RBM10 pairs, while E17 concerns a different cancer and depletion pattern.E2E16E15E18E17
  3. 3Ranked explanations: (1) residual molecular-subtype composition; (2) a cohort-specific signal or winner's-curse/data artifact; (3) a shared upstream driver; (4) deterministic co-amplification; (5) genuine within-tumour cooperation. The lack of replication across independent patient sources materially elevates the artifact explanation. The evidence supplies no specific shared driver or amplicon evidence, and co-occurrence across patients does not establish within-tumour cooperation.E2E3E1
  4. 4The provided paper abstracts do not establish a relationship between RBM10 and CDKN1B: the bladder-cancer abstract concerns FGFR3 and a urothelial carcinoma variant, while the other highlighted abstract concerns GNAQ/GNA11 in metastatic solid tumours. They therefore do not support a pair-specific mechanism; the absence of a curated network link is consistent with this being an under-explored candidate.E9E10E11E4
What would confirm or refute it

Test the leading subtype-composition hypothesis in an independent bladder-cancer cohort with molecular-subtype annotations: estimate the RBM10–CDKN1B association within subtypes and in a subtype-adjusted model, and check whether the association attenuates. To earn a within-tumour cooperation claim, separately use clonal or single-cell DNA profiling to establish co-alteration in the same tumour cells, followed by a functional co-dependency test.

Strongest competing explanation (model)

This is a conservative, testable explanation rather than a finding. The strongest deflating explanation is cohort specificity or winner's curse: significance occurs in only one independent patient source, despite surviving FDR correction. Subtype composition is unresolved, not demonstrated. No cited Europe PMC paper actually studies the RBM10–CDKN1B pair, so a within-tumour mechanism is unearned; that lack of pair-specific evidence strengthens the under-explored interpretation but lowers confidence.

Adversarial review (second model pass)

Weakest link: Residual molecular-subtype confounding is only a plausible, untested explanation: subtype was not measured or adjusted for, and the association rests on nine double-altered tumors in one non-replicated cohort.

Cross-cohort agreement (intra-snapshot)single source

Significant (after FDR correction) in one independent source of this tumour type so far. The engine records where a pattern is significant, not every source that could test it, so this calls for caution: a pattern selected from many tests tends to overstate its effect. It does not count against the pattern.

Evidence the argument cites

Model-written annotation, not a finding. The statistics it cites are real and are shown above; the argument connecting them is a hypothesis that needs wet-lab or clinical validation before it means anything.

Cite this finding
Permalink
https://cybergenic.im/findings/662b34e3-f982-4160-beaa-396311e7aff2
First seen
29 Sep 2026
Prediction registry
Locked 29 Sep 2026, row hash 684ffae6cff318bc08b70c2b76820bdc (not testable out of sample). How the registry works
BibTeX
@misc{cybergenic_662b34e3,
  author       = {{Cybergenic}},
  title        = {{RBM10 and CDKN1B co-occurrence in bladder cancer (MSK-IMPACT 50K)}},
  year         = {2026},
  howpublished = {\url{https://cybergenic.im/findings/662b34e3-f982-4160-beaa-396311e7aff2}},
  note         = {Research engine finding, first seen 2026-09-29; prediction locked 2026-09-29, registry row hash 684ffae6cff318bc08b70c2b76820bdc},
  month        = sep
}

Frontier alerts