← Research

Methods

How we read a plant

Tradition tells us which plants matter. To say why, we follow each one down to the molecules it carries, the proteins those molecules meet, and the measurements that record the meeting — in the open, every step cited.

Why a plant is never one thing

A herb is not a drug, and reading it like one misses what it is. A drug is a single molecule built to hit a single target. A plant is a community of compounds, assembled by the plant for its own reasons, each meeting the body in its own way. To understand a herb is to map that community — not to reduce it to a lone "active ingredient," but to trace the several molecules that give it its character and the several points at which they touch human biology.

That is the work of this library. For each plant we carry, we follow the same path: from the plant, to its known compounds, to the proteins those compounds are measured to engage, to the body systems those proteins govern. The result is not a claim that a herb treats a condition — we make no such claims. It is a map of mechanism: the precise, cited points where the plant meets the body.

The method, step by step

Identity, first. Every compound we name is resolved to a real chemical record in PubChem — the public chemistry database maintained by the U.S. National Library of Medicine — so that the molecule we discuss is the exact molecule, by structure, not by name alone.

Measured activity, second. For the proteins each compound engages, we draw on ChEMBL (the European Bioinformatics Institute's bioactivity database) and BindingDB (a public repository of measured binding affinities). Where a real, exact-match measurement exists — a Kd, a Ki, an IC50 — we report it with its source. Analog and approximate matches are excluded, so attribution stays truthful.

Structure, third. To see how a compound and its protein fit, we use AlphaFold — the protein-structure models from DeepMind and the EBI — to obtain the three-dimensional form of the target, and we work with the protein's ordered, well-predicted core.

Geometry, fourth. We then compute the fit ourselves: using AutoDock Vina, an open molecular-docking engine, we dock each compound into its target structure and record the predicted binding geometry and energy. This is our own computational result — a prediction of how the pieces meet, reported alongside the measured affinities, never in place of them.

What we show, and what we never claim

Everything visual in this library is built from that real data. The molecules you can rotate are the actual three-dimensional structures from PubChem. The binding events in our films are real docked poses. The numbers are measured values with links to the assays that recorded them.

And the language stays exact. We describe what a compound is measured to engage and what a body system does — structure and function. We do not say a herb treats, cures, or prevents any disease, because that is a different kind of claim requiring a different kind of evidence, and making it loosely would betray the rigor that is the whole point. Where the classical record and the modern measurement point to the same plant for the same system, we say so — and we keep the two clearly apart, so you can see exactly where tradition ends and measurement begins.

Sources we build on

PubChem (U.S. National Library of Medicine) · ChEMBL & AlphaFold (European Bioinformatics Institute) · BindingDB · AutoDock Vina. Every figure in this library links to the record that supports it.

These statements describe structure and function — what compounds are measured to engage and what body systems do. They have not been evaluated by the Food and Drug Administration, and nothing here is intended to diagnose, treat, cure, or prevent any disease.