Open collaboration bundle · by invitation

Oncology SDG

Shared Domain Graph

Welcome. Inside is a living map of oncology that accretes as institutions privately share attributed, privacy-floored measurements — extreme collaboration for patient health, with attribution and privacy held as one.

Architecture & method only · synthetic data · no PHI
Map controls

Shared research reporting

Dr. Lena Okafor is running her own study. In-network collaborators privately ask her to capture extra, attributed measurements in situ on specimens she already has open. Honoring one accretes the shared map — a new latent region emerges.

Your intrinsic study panel

Dr. Lena Okafor · Meridian Cancer Institute · computational pathology
  • H&E whole-slide image — sealed to coverage root
  • Somatic variant calls — derived, aggregate
  • Bulk expression profile — derived, aggregate
Sealed via Oncology.Study.SpecimenSeal@v1. This is your “transect”: the already-open specimen onto which co-measurements can be honored.

No contributions yet. Honor a request to record attributed, privacy-floored credit.

Never exchanged: raw patient identifiers, PHI, re-identifiable sequence, or patient-to-specimen linkage. Only derived, consent-bounded signal enters the commons.
Planning · GPU compute & network resources

Compute planned around the work, not the org chart.

Every analysis on the shared map runs on real infrastructure — GPUs, CPUs, storage, network. This view traces how the field's models actually run (training, inference, simulation), ties each quarter's PathwayRuns to the resources they consumed and the domains they served, and shows how projects — within and across organizations — can pool compute by shared objective rather than by bureaucracy. Because raw data never moves — only private cryptographic substrates and derived signal — patient privacy is the default, and compute can be allocated to the most valuable work wherever it lives.

01

How the models run

Three workload classes with very different resource shapes and duty cycles — each mapped to the domains it serves on the map:

Training · batch / bursty

Pan-Cancer Foundation Model

Multi-node pretraining over integrated multi-omics from hundreds of thousands of patients; B300 blocks cut months to days (seed §1).

Accelerator
512× B300
Interconnect
400 Gb/s IB
Working set
1.2 PB
Duty cycle
quarterly burst
multi-omics foundation model
Inference · steady low-latency

Spatial Pathology Stratifier

Vision-language inference over gigapixel WSIs, mapping immune cells relative to tumor to stratify trial patients (seed §2).

Accelerator
32× B300 (elastic)
Latency SLO
< 250 ms / tile
Throughput
~1.1M slides/qtr
Duty cycle
continuous
pathology spatial biology stratification
Simulation · sustained baseline

In Silico Trial Engine

Millions of parallel cellular-level simulations over RWE-grounded digital twins and synthetic control arms (seed §3).

Accelerator
256× B300
Pattern
parametric sweep
Working set
300 TB
Duty cycle
sustained
digital twins synthetic control
02

Last quarter's PathwayRuns → resources & domains

A PathwayRun is a sealed, provenance-bearing execution of a Pathway (a composable workflow recipe). Every run in 2026-Q2 carries a provenance root that binds what ran to the exact network resources it ran on, and the domains / subdomains it served:

RunPathwayDomains · subdomainsGPU (type × hrs)Storage · networkProvenance root
pr_7f21Compute.TrainFoundation@v1multi-omics · genomics / epigenomics / transcriptomics / proteomics512× B300 × 9,8001.2 PB · 400 Gb/s IB0x9c4e…
pr_3a8dStudy.SpecimenSeal@v1pathology · genomics4× B300 × 1224 TB · 25 Gb/s0x1d07…
pr_b2c5Assay.HonorInSitu@v1spatial biology · immuno-oncology8× B300 × 308 TB · 25 Gb/s0x77af…
pr_c810InSilico.SimBatch@v1digital twins · synthetic control256× B300 × 4,200300 TB · 100 Gb/s0xa1b9…
pr_5e33Map.EmergeComposite@v1stratification (immune_strat)2× B300 × 30.5 TB · 10 Gb/s0x44d2…
pr_e0f1Consortium.QuarterlyClose@v1commons · attributionCPU-only2 TB · 10 Gb/s0xf3aa…
03

GPU-hour footprint by domain

How the quarter's 16,000 GPU-hours were actually spent — one bar, split by share of the total, so the shape of the work is legible at a glance:

Multi-omics training9,800 h61.3%
In-silico simulation4,200 h26.3%
Spatial pathology inference1,280 h8.0%
Drug-design / docking480 h3.0%
Federated / secure-agg overhead240 h1.5%
04

Pooling compute by shared objective

The three workload classes have complementary duty cycles. Scheduled against one another, a shared allocation runs far hotter than any single project's private cluster — and the savings fund more science:

  1. Training is bursty and batch-tolerant → it backfills nights, weekends, and inter-quarter gaps.
  2. Inference is steady and latency-bound → it holds a reserved low-latency floor.
  3. Simulation is a sustained, preemptible baseline → it soaks up whatever is left.
  4. Interleaved, utilization rises from a typical ~45% siloed to ~85%+ pooled, at predictable cost.

Across organizations, allocation follows the shared goal and objective space — compute goes to the work most likely to move patient outcomes, not to whichever org has seniority. Each party keeps single-tenant sovereignty; only derived signal and cryptographic substrates cross the boundary, so pooling never implies data pooling.

ModeSiloedPooled by objective
Utilization~45%~85%+
Allocation basisorg budget / seniorityoutcome value of the work
What crosses the boundary(nothing — capacity stranded)derived signal + crypto substrate
Privacy postureisolated but idleisolated and busy
05

Datacenter map — compute by collaboration

Where each collaboration's workloads actually run. Pick a collaboration to see the institutions, their places, and the datacenter regions involved. Links carry derived signal over private cryptographic substrates — raw data stays local to each site.

06

Provenance bound to network resources

Because each analysis's provenance chains down to the CPU / GPU / storage / network it ran on, the whole pipeline is auditable and, crucially, plannable: you can price any future analysis from the measured cost of the ones that produced today's map.

Provenance layerBound resourcePlanning signal
PathwayRunGPU type × hours, node countaccelerator demand curve
Coverage root / sealstorage class × volumehot / warm / cold tiering
Cross-party contributionnetwork egress + crypto computeinterconnect & secure-agg budget
Attribution ledger entrywho ran it, on whose capacitychargeback & fair-share pooling
07

Forward capacity plan

Rolling the measured footprint forward, against the roadmap of models to train and studies to run — the basis for a structured, multi-year offtake (predictable CapEx vs. volatile OpEx, seed §4):

PeriodHeadline workloadGPU-hoursPeak nodesNote
2026-Q2 (actual)foundation v1 + sims16,000512baseline measured here
2026-Q3 (plan)+ immune-strat inference scale-out21,500640pooled off-peak with partner org
2027 FY (plan)pan-cancer v2 pretrain88,0001,0243-yr dedicated block, single-tenant
Custom inference and training architectures follow from this: the allocation attends to the actual work being performed and the outcomes being sought — not arbitrary organizational dynamics. GPU compute planning sidecar
08

Privacy by construction

Pooling and planning use resource telemetry and derived signal only. Raw patient data never leaves its sovereign boundary; parties collaborate through private cryptographic substrates — federated learning, secure aggregation, and proofs of computation — so the default is privacy, and shared compute never means shared records.

federated learning secure aggregation differential privacy proof-of-computation single-tenant isolation
Illustrative figures. Run IDs, GPU-hours, roots, and projections here are synthetic and for demonstration only — no real workloads, telemetry, or patient data.
Latent-space report · a guided tour

How a field builds its own map.

This report is a way to discover the idea behind the visualization — from the problem in oncology, through the category-theoretic machinery, to the collaboration mechanism that makes the map draw itself. Read top to bottom, or jump to a section. Two kinds of links appear throughout.

▸ interactiveacts on the live map (filters a category, reveals latent nodes, opens the collaboration panel). ↗ documentopens the underlying bundle artifact (registry YAML, technique spec, pathway template, sidecar) in a new tab.
01

The problem worth solving

Modern oncology's frontier — pan-cancer multi-omics foundation models, spatial-biology patient stratification, in silico trials with synthetic control arms — is gated less by compute than by cooperation. The signal that would move patient outcomes sits in silos held by institutions that compete, and that are bound by strict privacy law. Compute is necessary but not sufficient.

This model is grounded in domain-expert context on the field's challenges and opportunities. seed.txt · Executive summary
02

The core idea

Represent the oncology Shared Domain Graph (SDG) not as a fixed taxonomy but as a living latent space: a hypergraph whose most valuable regions are hidden until collaboration brings them into being. The organizing claim is a single equation — a pullback that lets two things usually traded against each other be held at once:

Sovereign Attribution = Privacy ×collaboration Attribution

Full credit, zero identity leakage. When credit is guaranteed and re-identification is impossible, the rational move for a competitive institution flips from hoard to contribute.

03

Reading the map

The map holds 34 conceptual domains in 9 categories, joined by morphisms and grouped into hyperedge regions. Tap a category to ▸ highlight it live (tap again to clear):

Every domain on the map is oriented toward Patient Outcomes — survival, response, quality of life. Hover any node on the map for its description and its grounding in the seed context.

04

The category Onc

Formally, Onc is a category. Its objects are the domains; its morphisms are structure-preserving maps (a practice area projects into Law-like bases, an entity grounds a domain, a temporal constraint binds a process); its hyperedges capture irreducibly multi-way relations rendered as regions.

05

Emergent pullbacks

The interesting domains are pullbacks (fiber products) D₁ ×B D₂: a composite that exists only once both of its legs do. These are hidden by default and crystallize in situ when a co-measurement supplies the missing leg. Tap go to see where each lives:

Immune Stratification = Spatial Biology ×clin Immunogo ▸
Spatial Multi-omics = Multi-omics ×omics Spatial Biologygo ▸
In Silico Control Arm = Digital Twin ×clin Synthetic Controlgo ▸
Pan-Cancer Model Card = Foundation Model ×omics Multi-omicsgo ▸
Response Prediction = Trials ×patient Responsego ▸
Hiding composites until both legs exist keeps the map an honest snapshot of what the network can actually do right now — watching it fill in is watching the field cooperate. composite-domains.yaml · emergence sidecar
06

The two focal points

The pullback of §2 works because attribution and privacy operate on different layers and never contend for the same object:

LayerObjectGuarantee
DataRaw records / sequenceNever leaves the sovereign boundary
DerivedCalls, panels, aggregates, model cardsConsent-bounded, privacy-classed
LedgerContribution + creditFully attributed; references only the derived layer
07

The water-reporting analogy

The shape is borrowed from field “water reporting” and rebuilt for oncology as shared assay reporting. None of the prior work's code or assets are used.

Water reportingShared assay reporting
Transect walkA lab's own study on a specimen / cohort
Bounded sample pointThe already-open specimen
Private request for extra readingsPrivate request for an extra derived assay
Honor on the same walkHonor in situ on the same specimen
Shared water mapShared oncology SDG map
Cross-project opportunityAn emergent composite domain
08

How the map grows

Each turn of the loop adds an attributed contribution to the commons, under the privacy floor, and may emerge a new composite — five pathway templates encode it:

  1. Seal your intrinsic study panel to a coverage root.
  2. Receive private, in-network co-measurement requests.
  3. Honor one in situ — near-zero marginal cost, high network value.
  4. A new edge is emitted; a composite domain emerges.
  5. The attribution ledger credits who made it possible.
  6. Quarter close snapshots the emergent map.
09

Falsifiable claims

The concept is stated as pre-registered, falsifiable hypotheses — the ones this demo exercises:

H-ONC1Honoring a request materializes a new pullback with no top-down edit.

H-ONC2Attribution and privacy hold simultaneously (sovereign attribution).

H-ONC5An already-open specimen: near-zero marginal cost, high network value.

10

Read the bundle

Everything on the map is a view onto a signed-off collaboration bundle. Start anywhere:

Honest boundaries. Architecture and method only. No patient data, no PHI, no re-identifiable sequence — every party, cohort, DID, and reading here is synthetic and illustrative. The category-theoretic framing is a modeling stance, not a clinical claim.
Overview · start here

A shared map for oncology, built by extreme collaboration.

Oncology's hardest problems — pan-cancer multi-omics models, spatial-biology patient stratification, in silico trials — require compute at serious scale.

They also need it run with efficiency, transparency, and governance — reliability built through redundancy across collaborative dimensions, not siloed isolation.

The signal that would move patient outcomes is scattered across institutions that cannot safely combine it.

This is an interactive model of a different arrangement: a living map of the oncology SDG that accretes in situ as competitors privately share attributed, privacy-floored measurements — and new regions of knowledge emerge that no one directly authored.

And yet “no one directly authored” is not the same as unauthored. Every collaborator authors the context from which a new region crystallizes — the questions asked, the panels run, the annotations left, the objectives held in common.

Large language models compress that distributed human context into dense representations, and honoring a co-measurement hardens that compression into a durable, verifiable substrate — the way sustained pressure turns loose carbon into diamond.

So each emergent region carries the fingerprints of everyone whose context made it possible, even when no single hand drew it.

Pathways & PathwayRuns. The mechanics under the map are Pathways — licensable, composable workflow recipes — and PathwayRuns — their sealed, provenance-bearing executions. Every run records who contributed what, on which resources (see the Planning tab), so the emergent structure stays fully attributed while raw data never moves — only derived signal over private cryptographic substrates.

Focal point · Attribution

Every observation, panel, and model card carries provenance and a credit split. Contributing is on the record.

Focal point · Privacy

Single-tenant sovereignty, consent scope, federated computation. Nothing re-identifiable is ever exchanged.

The pullback that unlocks both

Sovereign Attribution = Privacy × Attribution. Full credit with zero identity leakage, held at once.

What you're looking at

A hypergraph of 34 conceptual domains of oncology — molecular, imaging, clinical, therapeutic, patient, compute, governance, and the collaboration fabric — all organized around patient outcomes (survival, response, quality of life). The most valuable domains are latent pullbacks, hidden until collaboration brings them into being.

Who it's for

Computational pathologyGenomics labsImmuno-oncology Pharma R&DClinical research orgsPatient trusts Compute providers

Grounded in domain-expert context from the field — the challenges and opportunities around pan-cancer models, spatial pathology, and data sovereignty.

Try it in three steps

  1. Open Collaboration to see private, in-network co-measurement requests on an already-open specimen.
  2. Honor a request — near-zero marginal cost, high network value.
  3. Watch a new composite domain emerge on the map, with an attribution-ledger entry and the privacy floor intact.

The latent-space report

Want the full picture? The Latent-space report is a guided, ten-section tour that makes the whole concept discoverable — from the problem in oncology, through the category-theoretic machinery (objects, morphisms, pullbacks), to the collaboration mechanism that makes the map draw itself. It carries two kinds of links: ▸ interactive ones that act on the live map (filter a category, reveal latent nodes, emerge a specific pullback), and ↗ document ones that open the underlying bundle artifacts — registry YAML, technique specs, pathway templates, sidecars, hypotheses — in a new tab.

How to read the map

Tap a category to highlight it live on the map (tap again to clear):

Honest boundaries. Architecture and method only. All parties, cohorts, DIDs, and readings are synthetic — no patient data, no PHI. Use the Index button or bottom navigation to move between sections.