Why This Site Exists
I have spent more than twenty years learning this work the hard way: building from the grain forward, solving malting and brewing problems, testing assumptions, making mistakes, and finding out where an early decision comes back to bite the finished beer.
That knowledge does not help anybody if it stays trapped in old notes, supplier conversations, production records, failed trials, or my head.
So I am putting it here.
The Problem
Gluten-free brewing information is still too fragmented.
Some of it is shallow. Some of it is outdated. Some of it treats brewing like a collection of isolated tricks instead of a connected system. That approach falls apart when real grain, real process, real scale, real flavor, and a real gluten-free claim all have to survive the same product.
This work is not just about recipes. It includes:
- raw-material identity and suitability;
- malting behavior and malt quality;
- starch access and enzyme timing;
- runoff, fermentation, and finished-beer structure;
- contamination risk and product trust;
- cost, scale, and the ugly tradeoffs that show up outside a laboratory.
Miss the mechanism upstream and you usually pay for it downstream.
What This Site Is Trying to Do
Gluten Free Brewer is an evidence-governed technical field manual and applied-research commons for truly gluten-free brewing. It publishes practical guidance, the evidence and uncertainty behind that guidance, and the open questions readers can help answer.
Three words in that sentence are doing work. Field manual, because the point is a better batch, not a better essay. Evidence-governed, because a recommendation here carries what backs it, what would overturn it, and who owns it — the authority is the evidence, not the byline. Commons, because the open questions are published as asks anyone can run, and results come back in.
In practice it turns scattered experience and evidence into a practical map.
The pages should help readers:
- find the real owner of a question;
- understand why the mechanism matters;
- separate proven guidance from experience, inference, and open questions;
- see where a process is likely to fail;
- make better brewing, malting, quality, supply, and product decisions;
- avoid rediscovering the same expensive lessons from scratch.
The docs are the product. A page earns its place by doing a useful job, not by making the site look complete.
Why Beer Is the Starting Point
Beer exposes weak assumptions fast.
Weak grain shows up. Weak malt shows up. Poor starch access, conversion, runoff, fermentation, and product structure show up. A claim that is not supported upstream eventually shows up too.
That makes beer a brutal but useful proving ground.
Beer is not the edge of the map. The same grain, malt, ingredient, quality, and process questions reach into a much larger gluten-free product landscape. Brewing is where much of this knowledge was pressure-tested.
Where AI Fits
Yes, AI helps with this site.
It helps organize material, compare pages, draft rough language, tighten explanations, and turn a large body of notes and experience into something people can actually navigate.
Here is the boundary:
- AI is a writing and organization tool.
- AI is not the source of the brewing knowledge.
- AI does not get to invent evidence, authority, experience, or certainty.
- AI can be useful, and AI can be wrong.
- Important guidance still has to survive the documents, the evidence, informed judgment, and reality.
The real source is the brewing, malting, Bard's history, testing, mistakes, records, and commercial experience behind the pages. The Knowledge Foundry exists to keep that distinction from getting blurred.
Future AI tools may come later if they genuinely help readers use the material. A chatbot is not the point.
What Kind of Site This Is
The formal name for what we're building is a participatory applied-research commons for truly gluten-free brewing — and since that's a mouthful, here's what each word buys. Participatory: outsiders can ask, contribute, criticize, test, and correct without joining anything; meaningful contributors get credited. Applied research: the questions come from real brewing problems and end in usable methods, data, and proposals — like the datasets we publish in full and the standards we propose for the field to tear apart. Commons: the resulting knowledge stays publicly useful, traceable, and open to improvement, while rights, privacy, and confidentiality stay protected. And it's governed: contributions get reviewed, evidence gets labeled honestly, and named humans stay accountable for what gets published — participation is not automatic publication.
That identity is earned by behavior, not claimed by a slogan. The Research Library, the criticizable proposals, and the corrections we publish are the proof or they're nothing.
The Standard
I want this site to be useful enough that somebody can make a better beer, diagnose a process problem faster, ask a sharper question, or stop wasting time on the wrong variable.
That means leaving the hard parts in. It means saying what is known, what is experience, what is uncertain, and what still needs work. It also means cutting polished nonsense when it is not helping the reader.
The short version is simple:
The knowledge matters. The field needs a better map. I am tired of watching useful information stay buried or get replaced by confident bullshit.
So I am documenting it.
Next: Start Here to use the site, How the System Works for the machinery behind it, or About Craig for the person and experience behind it.