A medicine has a shape before it has a target: an antibody carrying a poison, a peptide carrying an isotope, a T cell carrying a receptor. These 12 hubs read the corpus by shape. Each one gathers what OnCo already records about a format, 810 medicines in all with 350 approved and 1,848 trials recruiting, and every section names the records it came from; where the corpus has nothing, the section says so rather than filling in.
93 medicines in the corpus · 14 technology records
An antibody-drug conjugate is an antibody that homes to a protein on the tumour cell, is swallowed, and releases a chemotherapy payload inside it. That widens chemotherapy's safe dose window about a hundredfold, which is why payloads too toxic to give alone can be used, though lung inflammation, neutropenia and eye toxicity from the payload still occur. from Antibody-drug conjugate (ADC)
A patient's T cells are removed, given a synthetic receptor that recognises the cancer, multiplied, and put back as a living drug. from CAR-T cell therapy
A bispecific antibody is one antibody with two different grabbing arms, so it can block two targets at once or pull an immune cell onto a cancer cell. from Bispecific antibodies
374 medicines in the corpus · 20 technology records
Pills that block the specific enzyme a cancer relies on. Imatinib in 2001 proved a cancer could be switched off by design. from Small-molecule kinase inhibitors
Cytokine therapy gives immune-signalling proteins as drugs. High-dose interleukin-2 was the first immunotherapy to cure some melanomas, at great toxicity. from Cytokines & engineered cytokines
Viruses engineered to infect and burst cancer cells while leaving normal cells alone, and to alert the immune system in the process. from Oncolytic viruses
Most of OnCo is organised by disease, target or record kind. The modality lens turns the corpus ninety degrees and reads it by the shape of the medicine, the way a drug designer, a manufacturer or a regulator thinks about it: everything the site knows about antibody-drug conjugates in one place, then everything about radioligands, and so on for the twelve formats the open drug engine defines.
Nothing on a hub is written for the hub. The plain-English explanation is the technology record's own TL;DR and principle; the approved medicines are the drug records with approval rows; the trials are the trial records that name those medicines; the side-effect profile is the glossary terms and label events those records carry; the resistance routes are the atlas entries whose exemplars are medicines of the format. Every section says which records it came from, and a section with nothing behind it is left empty.
How a hub is built
The medicines of a format are the ones the open drug engine files under it, placed on its grid or listed as unresolved; the technology records of a format are listed by hand in src/lib/modular-formats.ts and each carries a pill back to its hub. From those two sets the rest follows the graph's links: companies from the medicine records and the companies that list them, papers and ideas from their references, roadmap steps from the records they cite, manufacturing from the site and supply chain records.
Each hub has a JSON companion at the same address (data.json) with the same sections and the record ids behind each, so agents can read the lens the way a reader does. The pages are open data (CC BY-NC 4.0). Nothing here is medical advice.