> For the complete documentation index, see [llms.txt](https://docs.brewfather.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brewfather.app/brewing-knowledge.md).

# Brewing Knowledge

- [Overview](https://docs.brewfather.app/brewing-knowledge/brewing-knowledge.md): Practical brewing science grounded in verified literature — built for Brewfather users.
- [Brewing Fundamentals](https://docs.brewfather.app/brewing-knowledge/fundamentals.md): Grain-to-glass process overview, core brewing metrics, and the most impactful process controls.
- [Ingredients Deep Dive](https://docs.brewfather.app/brewing-knowledge/ingredients.md): Fermentables, hops, yeast, adjuncts — ingredient science, quality, storage, and how to model choices in Brewfather.
- [Water Chemistry & Adjustments](https://docs.brewfather.app/brewing-knowledge/water-chemistry.md): Ions, alkalinity, mash pH, chloride:sulfate balance, and how to use the Brewfather Water Calculator for consistent results.
- [Mash & Lauter Science](https://docs.brewfather.app/brewing-knowledge/mash-and-lauter.md): Enzyme activity, mash temperature science, sparging strategies, and efficiency drivers for all-grain brewing.
- [Boil, Hop Utilization & Whirlpool](https://docs.brewfather.app/brewing-knowledge/boil-and-hopping.md): Boil objectives, DMS management, hop utilization science, whirlpool additions, and IBU model caveats.
- [Fermentation & Yeast Management](https://docs.brewfather.app/brewing-knowledge/fermentation.md): Comprehensive guide to fermentation and yeast management for homebrewers using Brewfather.
- [Packaging, Carbonation & Oxygen Control](https://docs.brewfather.app/brewing-knowledge/packaging-and-carbonation.md): Guide to packaging, carbonation, and oxygen control for homebrewers using Brewfather
- [Quality Control & Off-Flavor Diagnostics](https://docs.brewfather.app/brewing-knowledge/quality-control-and-off-flavors.md): Sensory evaluation, common off-flavor fault signatures, root-cause matrix, and how to use Brewfather batch data to accelerate diagnosis.
- [Cleaning, Sanitation & Safety](https://docs.brewfather.app/brewing-knowledge/cleaning-sanitation-safety.md): Cleaning versus sanitizing, chemical concentrations, contact times, material compatibility, process hygiene checkpoints, and brewery safety guidance.
- [Troubleshooting Playbooks](https://docs.brewfather.app/brewing-knowledge/troubleshooting.md): Step-by-step playbooks for the most common brewing problems, with root-cause decision trees, immediate containment actions, and next-batch prevention.
- [Brewfather Workflow Best Practices](https://docs.brewfather.app/brewing-knowledge/brewfather-workflow-best-practices.md): End-to-end guide to using Brewfather effectively for consistent, repeatable brewing outcomes.
- [Glossary](https://docs.brewfather.app/brewing-knowledge/glossary.md): Glossary of terms used in brewing and in the Brewfather app.
- [References & Further Reading](https://docs.brewfather.app/brewing-knowledge/references.md): Brewing literature and technical sources used throughout the Brewfather Knowledge Library.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.brewfather.app/brewing-knowledge.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.