
The concept is not the design
Dear {{first_name | reader}},
Biodesign is full of promises. Here is where one of them meets the bench.
You have grown a slab of mycelium over a week or two, and it is finally in your hands. The whole project was built around a single promise: this material "self-heals." That promise carried you through the sketch, the precedents, the search for a lab that had grown something close, and the crit.
Now the material is in front of you, and you are testing it.
You score a crack into the surface, mist it, feed it, keep it warm, and wait to see whether the gap closes on its own. This is the moment the idea has to become a real material doing a real thing, and something is missing.

Ectomycorrhizal mycelium (white) associated with Picea glauca roots (brown). Photo: André-Ph. D. Picard. CC BY-SA 3.0, via Wikimedia Commons.
The word that first caught you named an effect. It never named the behaviour underneath that effect. And here at the bench, with the material in your hands, that behaviour is exactly what you now need.
Does the living fungus actually regrow across the damage? Or does the surface only close over and look mended? The word will not tell you. The material might, if you know what to ask it.
So let me show you what I mean, with the word that started all this.

“Self-healing concrete crack healing”. Images credit: Niranjan Prabhu K. CC BY-SA 4.0 via Wikimedia Commons
One word, several different promises
Take "self-heals." It sounds like a single property. It is really several different promises sharing one word.
It might mean the living fungus regrows across the damage. It might mean two living surfaces fuse back into one. It might mean the surface closes over and looks mended, or that the material swells when it gets wet so the gap pinches shut on its own. It might mean that a person has to feed it nutrients or pack in fresh mycelium by hand.
These are not shades of a single idea. Each one calls for a different test, a different collaborator and a different maintenance story. Each one also licenses a very different sentence in public.
The underlying science can be genuine. In one study of a pure mycelium leather, fungal cells that had gone dormant during processing revived when researchers fed them a nutrient broth. They grew back over punched holes and recovered most of the original strength at the wound.
That is real self-healing. It is worth being precise about what made it possible: living cells survived the making of the material, and were then given the moisture, food and time to resume what fungus does.
It is worth setting that beside a building-material story from last year that travelled a good deal further. The headline described a living fungal material that "repairs itself for over a month." The press release underneath was clear that self-healing had not actually been tested. What lasted a month was viability, which means the cells stayed alive longer than usual.
That is a real and useful result, but it is not repair. Somewhere between the laboratory and the coverage, a month of staying alive quietly became a month of healing.
Same word. Two completely different promises. Only one of them would let you honestly promise repair.
Why the gap suddenly matters
For most of biodesign's life this kind of slippage was survivable, because the biology stayed at arm's length: a metaphor in a manifesto, or a result in someone else's lab, and the designer rarely had to put a number on what a material actually did.
That distance has closed.
Biofabrication has put the living material directly in your hands, so the person making the promise is now also the person who has to grow the thing and stand behind what it does.
At the same time, AI tools answer biological questions on demand, in a register that sounds more grounded than it is. The promise now leaps straight from the organism to the public version, with nothing in between to say which behaviour is doing the work, or under what conditions.

Aspergillus structures in LPCB tease mount of culture showing conidia, sterigma, vesicle, conidiophores, foot cell, hyphae, and mycelium. Photo: Ajay Kumar Chaurasiya. CC BY-SA 4.0 via Wikimedia Commons.
How far down do you actually go?
None of this means you have to become a biochemist. It does not mean every promise has to be dragged down to chemistry. You go only as deep as the promise requires, and no shallower than it demands.
"The crack looks closed" is a question about a surface. "The material is alive" is a question about cells. Neither needs to be taken to the molecular level for its own sake.
This image shows a group of elongated cells (hyphae) from the filamentous fungus Podospora anserina. They are labeled with a fluorescent stain, JC-1, that labels areas of high metabolic activity (orange-red staining). It was taken by a high-resolution camera attached to a fluorescence microscope. The magnification is 630x. Photo: Christian Scheckhuber. CC BY-SA 4.0 via Wikimedia Commons.
But some promises reach that level faster than designers tend to expect. Take a material that "senses pollution and changes colour." That promise does not stay poetic for long.
Which molecule is being detected, and what binds it: a pigment, a protein, a receptor? What changes once it has bound, and how does that change become a colour the eye can actually see? How specific is it, and what might set it off by accident?

Protein Structure of NCAM1 (Neural Cell Adhesion Molecule 1). Image: Emw. CC BY-SA 3.0, via Wikimedia Commons.
Four questions in, and you are already working at the level of molecules, because that is where this particular promise turns out to live. The skill is not depth for its own sake. It is knowing where a promise lives, and going exactly that far.
With AI in the loop, that skill only sharpens. A predicted structure is not a proven function. A generated sequence is not a working protein. The literacy to tell a real result from a convincing depiction of one is quietly becoming the thing that matters most, and it is the one thing these tools cannot hand you along with their output.

The tool I am building
The practical instrument for this is the Biodesign Promise Worksheet. It begins where this email began, by taking the promise your project has come to lean on and laying out the different things it might actually mean, the way "self-heals" opened into several versions.
You choose one of those versions and put only that one to a short series of plain questions: what it does, exactly; what part of the living thing does the work; what sets it off; what you would see if it worked; how you would know it is real; and when it would break.
By the end, the version you started with has settled into one of three places. It is sharp and already shown, and you can build on it. It is sharp but not yet shown, and you now know what to test before you commit to it. Or it cannot be pinned down at all, which is not a failure. It becomes a brief, the list of what you would have to find out or invent to make it real.
The worksheet is free for subscribers. If you're already on the list, it's in the issue waiting for you. If you're not, subscribe here, and it's yours: we’ll include it in our welcome email.
That is what From the Molecule Up is for. It is a literacy project for designers and educators working with living materials, biofabrication, and AI biology. Its aim is to build the layer between metaphor and mechanism that living-materials biodesign still lacks, without asking anyone to become a biochemist. Enough, that is, to know where a biological promise actually lives, and what can honestly be promised once it has been found.
This email is where that gets built, in the open. This is the first issue. Each one will take a single biological promise apart the way we took "self-heals" apart today, and add one more piece to that missing layer, until the whole runs from the molecule up to the things we make from it.
I am writing the book as we go, and you are reading it before it is a book.
Before you go, I would like to ask you one thing. If a biological design promise has stayed with you, one that sounds wonderful but goes vague the moment you slow it down, reply and tell me what it is. A project, a press release, a tool, a studio brief, anything at all. I will work through the sharpest of them in a future issue.
Until next time,
Raphael

