Definition
Cup-Driven Maturity describes a roast condition in which the determination of roast completion — the judgment that the coffee has reached the intended flavor state — is made through cup observation rather than by reference to machine-generated events such as first crack, development time ratio (DTR), or color measurement endpoints.
The roast profile generates data. That data informs the process. But the maturity call is confirmed by what the cup shows, not what the instrument reads.
Observable Conditions
When Cup-Driven Maturity is the confirmed standard for a given release:
- Multiple cup evaluations were conducted across batch conditions before the release was confirmed
- The research record notes which cup behaviors confirmed maturity (e.g., sweetness integration, acidity structure, absence of underdevelopment markers)
- Instrument data is present in the record but is not the primary maturity indicator
Relation to Conventional Framework
Conventional roast development is typically guided by first crack timing, development time ratio (DTR), and color measurement. These are instrument-based confirmation systems — the machine tells the roaster when the coffee is done.
Cup-Driven Maturity does not replace this data. It reassigns the final authority. The cup confirms whether the roast produced the intended flavor structure. The instrument records what happened.
This is a methodological position, not a claim that instrument data is irrelevant.
Common Misreadings
“Cup-Driven Maturity means the roast data is ignored.” The roast data is still recorded and referenced. The difference is that the cup, not the data, is the final arbiter of release decisions.
“This is just sensory evaluation.” Standard sensory evaluation typically uses instrument data to set the context for tasting. Cup-Driven Maturity means the cup is the primary confirmation system, with instrument data as supporting context.
“All good roasters taste their coffee.” Tasting is common practice. Cup-Driven Maturity as a documented phenomenon refers specifically to a system where this is formalized as the primary confirmation method and recorded as such in the release data.