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.
Choose a failure, let the RL safety controller observe DataHub-grounded context, then follow every decision through recovery or replay.
Replaces guessed table names with stable DataHub URNs.
search(query="domain:oncology AND LUAD progression")27 governed assets · 4 owners · 3 platforms
urn:li:dataset:(gdc,TCGA_LUAD_progression,PROD)Launch the investigation to produce a DataHub-grounded reliability finding.
Awaiting DataHub search…The Governance Steward cannot mutate DataHub or recover a blocked mission without human approval.
Single-use approval · verified replay never writesThe 3D scene reacts to DataHub agent evidence; it is one inspection surface inside the governed system.
Drag to rotate
Scroll to zoom
Click a dot to learn more
Every cluster, gene and cohort summary points back to cataloged schema and lineage evidence.
gene_expression_summary.gene STRINGmean_expression FLOAT64cluster_id STRINGpatient_key STRING✓ live contract fields alignedSynchronize the live graph, inject a research incident, observe its verified blast radius, then preview the governed counterfactual recovery without writing data.
Awaiting live graph synchronization…The 3D topology starts locally; synchronization attaches fresh MCP evidence.
Repair preview: COALESCE feature patch
Select a scenario, synchronize DataHub and inject the incident.
A failed completeness contract propagates into the deployed progression model and two downstream consumers.
Dataset steward → feature owner → model owner → application operator.
Freshness, null rate, row count, schema compatibility and expression range.
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.
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.
The Repair Engineer reads schema, lineage, owners and quality rules before producing a mergeable artifact.
✓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