⌬
OncoTwin 3DV10.0 · SEVEN DATAHUB-NATIVE CANCER CONTEXT TWINS
◉ DataHub connecting
BUILD WITH DATAHUBAGENTS THAT DO REAL WORK+PRODUCTION ML AGENTS+METADATA-AWARE CODE GEN
JUDGE MODE · RL DIGITAL TWIN + INTERACTIVE AGENT THEATRE

Watch context become safe action.

Choose a failure, let the RL safety controller observe DataHub-grounded context, then follow every decision through recovery or replay.

◉ ACTIVE INCIDENTLUADRNA-seq freshness breachluad_progression_v3
RL DIGITAL TWIN MISSIONS · RESEARCH-ONLY SAFETY SIMULATION
RL POLICYQ-LEARNING
STATE RISK—
ACTIONAWAITING
REWARD—
DATA TRUST—
Mission events will appear here as GCP + DataHub work is replayed.
◉   LIVE CONTEXT GRAPH◎ Auto-following
▱DataHub18% context
Ready · six agents awaiting incident00:00
AGENT INSPECTOR · 01◎ READ

Context Scout

Replaces guessed table names with stable DataHub URNs.

DATAHUB CAPABILITYMCP · searchsearch(query="domain:oncology AND LUAD progression")
CONTEXT RETURNED

27 governed assets · 4 owners · 3 platforms

urn:li:dataset:(gdc,TCGA_LUAD_progression,PROD)
GROUNDED FINDING—/5

Launch the investigation to produce a DataHub-grounded reliability finding.

Awaiting DataHub search…
GOVERNED WRITEBACKLOCKED

The Governance Steward cannot mutate DataHub or recover a blocked mission without human approval.

Single-use approval · verified replay never writes
CANCER TWIN · SYNTHETIC RESEARCH SPACE

See progression. Interrogate provenance.

The 3D scene reacts to DataHub agent evidence; it is one inspection surface inside the governed system.

3D SPECIMEN · CLICK A DOT TO EXPLORE

Pulmones

LUADSYN-NSCLC-A17LUNG
○ LOCAL ENGINE
✣ INFERRED STATEStage III

Drag to rotate
Scroll to zoom
Click a dot to learn more

00
Baseline
01
Stage I
02
Stage II
03
Stage III
04
Stage IV
03 · STAGE IIISynthetic regional progression state
TISSUE CELLS14,382
ACTIVE SIGNALS1
CONTEXT LINKS34
MODEL RISKHIGH
SINGLE-CELL CONTEXT

Cell states with governed meaning.

Every cluster, gene and cohort summary points back to cataloged schema and lineage evidence.

INTERACTIVE UMAP · 14,382 CELLS◎ brush + hover
GENE PROGRAMMKI67
DATAHUB CATALOG SCHEMAgene_expression_summary.gene STRINGmean_expression FLOAT64cluster_id STRINGpatient_key STRING✓ live contract fields aligned
DATAHUB CAUSAL OBSERVATORY · LIVE EVIDENCE / SIMULATED CONSEQUENCE

Watch metadata become a safety force field.

Synchronize the live graph, inject a research incident, observe its verified blast radius, then preview the governed counterfactual recovery without writing data.

SPATIAL ML LINEAGE ORGANISM○ starting causal engine
FOCUSED ASSETprogression_featurescataloged feature tableAwaiting live graph synchronization…
LIVE DATAHUB EVIDENCESIMULATED BIOLOGYSEVEN CATALOGED DATA PRODUCTSHUMAN POLICY MEMBRANE
CAUSAL CONTROL DECKUNSYNCED
GRAPH PROVENANCENo live evidence attached

The 3D topology starts locally; synchronization attaches fresh MCP evidence.

SELECTED COUNTERFACTUALBLOCK MODEL

Repair preview: COALESCE feature patch

Select a scenario, synchronize DataHub and inject the incident.

0/6LIVE MCP READS0AFFECTED NODES0WRITES
END-TO-END ML LINEAGE · 3 HOPS◎ live MCP get_lineage
→ → → →
BLAST RADIUS1 model · 2 APIs · 1 dashboard

A failed completeness contract propagates into the deployed progression model and two downstream consumers.

OWNERSHIP CHAINThoracic ML

Dataset steward → feature owner → model owner → application operator.

QUALITY ASSERTIONS8 passing · 1 warning

Freshness, null rate, row count, schema compatibility and expression range.

JUDGE PROOF MODE · SEVEN DATAHUB-NATIVE CONDITIONS

Enter the Cancer Context Universe.

Each 3D world maps to its own cataloged BigQuery data product. Capture identity, schema, contract, ownership, query and bidirectional-lineage proof from the self-hosted DataHub MCP server.

INTERACTIVE 3D MISSION MULTIVERSE○ starting local engine
SELECTED WORLDBiomarker Completeness CrisisProduction ML Agents
DataHub context beamRL safety stateGoverned recovery
LIVE DATAHUB EVIDENCE LEDGERNOT CAPTURED
VERIFIABLE CLAIMRun a live proof capture

No cached screenshots. Every proof is generated on demand.

Awaiting canonical DataHub URN…

MCP search, schema and bidirectional lineage calls will appear here with their measured latency.

0/6MCP READS—ACTIVE INCIDENTS0WRITES DURING PROOF
METADATA-AWARE CODE GENERATION

Generate the fix from real context.

The Repair Engineer reads schema, lineage, owners and quality rules before producing a mergeable artifact.

GENERATED ARTIFACT
MERGE READINESS92 / 100

✓Schema groundedFields verified through DataHub MCP

✓Lineage-awareProtects downstream model and API

✓Owner assignedThoracic ML

✓Quality thresholdMatches cataloged completeness rule

!Human approvalRequired before PR/writeback