PatternBaseHow I Handle Knowledge
Permaculture knowledge draws on research, practitioner experience, and tradition. Here's how I handle that in PatternBase.
Where does the plant data come from?
The plant database draws from agricultural databases, seed catalogs, and permaculture reference materials. Companion planting relationships are sourced from a mix of published research, practitioner observation, and traditional knowledge. I try to be transparent about the difference.
Are companion planting claims scientifically proven?
Many aren't, and I don't pretend otherwise. Companion planting is one of permaculture's richest areas of practitioner wisdom, but controlled studies are limited. When I say "traditionally planted to deter pests," I mean generations of gardeners have found it useful. When research exists, I lean on it. When it doesn't, I say so.
How should I interpret guild recommendations?
Guild templates are starting points, not prescriptions. They reflect combinations that have worked for many practitioners in similar climates. Your soil, microclimate, pest pressure, and rainfall will shape what actually thrives. The best guild is the one you observe and adapt over seasons.
What does "evidence strength" mean on guild templates?
It reflects how well-documented a plant combination is, from peer-reviewed studies to "widely practiced but untested." A lower score doesn't mean it won't work; it means fewer people have formally documented results. Your garden is the experiment.
How accurate are yield and carbon projections?
They're estimates based on growth models and published benchmarks, not promises. Actual yields depend on soil biology, weather, management, and establishment time. I show them to help you think in systems, not to guarantee outcomes. Treat them as directional, not precise.
What if something doesn't match my experience?
Tell me. Seriously. If you've been growing food forests for 20 years and the data says something that contradicts your observations, your garden is the authority. I'm building community feedback loops so practitioner experience improves the platform over time.
Is PatternBase trying to replace experienced practitioners?
No. PatternBase is an observation and design tool. It helps you record, plan, and learn. It doesn't replace the knowledge that comes from watching a system evolve over years. I built this because I think the permaculture community deserves better tools, not because I think tools replace wisdom.
Why not just use peer-reviewed sources?
Because permaculture operates at an intersection of traditional knowledge, ecology, and agriculture that peer-reviewed research hasn't fully caught up with. I use research where it exists, honour practitioner experience where it doesn't, and try to be honest about which is which.
Still have questions?
I genuinely want to hear from you, especially if your experience contradicts something you see on PatternBase.
james@pattern-base.com