The sentence your project is already leaning on, and how to test it before you build
A biodesign promise is the sentence about what a living material does that a design project has come to rely on. “This mycelium heals its own cracks.” “This algae cleans the air.”
It says what the biology does, and it usually sounds settled and obvious. Most of the time you did not sit down and choose it. It formed while you were writing, or you picked it up from a paper, an exhibition, or a supervisor, and it has sat inside the project as an assumption ever since.
The promise matters because everything downstream leans on it: the wall text, the decision to fabricate, the answer you give in the crit. So before you build on a promise, it is worth taking it apart to see whether it holds.
A promise names an effect and hides the behaviour underneath it. And one word can hide several completely different behaviours.
Take “mycelium self-heals”. Slow it down and it could mean any of these.
the living fungus grows back across the damage
two cut surfaces fuse together again
the surface just closes over and looks mended
the material swells when it gets wet, so the gap pinches shut
a person feeds it or patches it by hand
That is five different things wearing one word. Each needs a different test, a different collaborator, and a different maintenance story. Each lets you say something completely different in public.
A designer who says “self-heals” without knowing which one they mean has not yet decided what they are making.
You take the loose promise and walk it down into something specific you can check.
You do not need a lab or a biology degree. You need the promise your project has come to rest on, and the willingness to ask the next question.
First, find the promise the project is already carrying: the sentence about what the material does that the work has come to lean on. Then, if it hides more than one behaviour, split it and pick one. Then ask plain questions about that one thing.
By the end, the promise lands in one of three places.
Sharp and shown, so you can build on it.
Sharp but unproven, so you test it before you commit.
It cannot be pinned down, which is not a failure: it is the exact list of what you would have to find out or invent to make the idea real.
Most projects answer the first question only, and treat that answer as though it covered all six.
Go as deep as the promise needs, and no deeper.
“The crack looks closed” is a question about a surface. “It senses lead in the water” is a question about molecules. You stop at the level where the real answer lives.
This is also not hostile to speculative or provocative work. If a project means to provoke rather than function, an unproven promise can be a deliberate choice. Testing the promise just makes sure it is a choice you are making on purpose, not one you have mistaken for a working material.
Biodesign Academy makes two free instruments for working a promise down.
The Biodesign Promise Worksheet. You bring a promise, split it, run it down the six questions, and see where it lands.
The Molecular Behaviour Reference is what you keep beside it for the second question: a short reference naming the small set of things a protein can actually do, and helping you tell whether the protein is the thing you are making or just the machine that makes it.
The biodesign promise is part of the vocabulary behind From the Molecule Up, the design-education project and forthcoming book from Biodesign Academy. Taking a promise apart is molecular reasoning in practice: tracing a design intention down to the biology it depends on. Molecular design literacy is the underlying ability; better design judgement is what grows from doing it over time.
