The Knowledge We're Preserving
Hard-earned knowledge is easy to lose.
It gets trapped in old notes, batch memory, supplier conversations, failed trials, half-remembered process changes, and the heads of people who had to solve problems before there was a clean map.
That is dangerous because gluten-free brewing still has too many places where bad assumptions can look reasonable.
Bard's matters here because the work generated lessons that are still useful:
- gluten-free grain selection is not a naming exercise;
- malt quality affects flavor, body, process, and trust;
- sorghum can matter without pretending to be barley;
- external enzymes are tools for conversion, not excuses for weak malt thinking;
- QA starts before the brewery, not at the label;
- market trust depends on product truth, not soft language;
- the beer still has to be good.
Those are not museum pieces. They are working ideas.
What Needs To Survive
The knowledge worth preserving is not only the success story. It is the practical shape of the work:
| Area | What Needs To Survive |
|---|---|
| Grain | cultivar, lot identity, sourcing, storage, and suitability for brewing or malting |
| Malt | flavor, aroma, color, body, process behavior, and release judgment |
| Mash | starch access, gelatinization, enzyme strategy, temperature, time, and runoff |
| QA | supplier proof, cross-contact control, batch records, and release logic |
| Market | the difference between a real gluten-free beer and a product leaning on dietary sympathy |
| Judgment | knowing when a problem is grain, malt, mash, fermentation, QA, or expectation |
That is the reason for Gluten Free Brewer.
The site takes scattered experience and turns it into something another person can use. Not perfectly. Not completely. But plainly enough to keep the knowledge from disappearing.
What Still Needs Craig Review
Some Bard's-specific details should only be added from original records or Craig's direct memory:
- exact production milestones;
- specific malting partners or process details;
- early recipe details;
- original test results;
- names, dates, and documentation trails.
Those details can make the section stronger later. They should not be invented for launch.