How answers are worked out

The blend explorer answers one question: which way does changing the proportions push the blend? Adding more of a high-tannin, low-acid bittersweet raises tannin and lowers acid. Adding a sharp does the reverse, and drops the pH into a range where bacterial spoilage is less likely. That directional relationship is well evidenced, it is what blending decisions are actually made on, and it is the level of resolution the underlying cultivar data supports.

Each cultivar carries a blend profile of 1–5 bands on seven axes, not measured numbers, because most cultivars have no measured numbers — and where they do, the measurements come from different sites, decades and methods and cannot be averaged. The model weights those bands by the volume share of each component and reports the result as a band. Weighting a handful of historic Somerset acid figures against one modern New York figure and reporting a result to two decimal places would look more authoritative and would be false.

Pairing on CiderHQ is treated as sensory interaction rather than as suggestion. The question is what happens in the mouth when an acidic liquid meets a fatty food, when condensed tannin meets protein, or when residual sugar meets capsaicin — and every mechanism the site uses is written up separately, with its evidence graded, including the ones where the evidence is craft convention rather than measured effect.

Most pairing records are authored: someone wrote the interaction and named the mechanisms it rests on. Below those, each food page carries a derived section, produced mechanically from the same mechanisms. It reads the food’s property bands — fat, salt, heat, sweetness, protein, intensity — and each style’s sensory profile, and fires a rule where both sides meet a threshold. High fat against high acid fires the acid-cuts-fat mechanism; high fat against high carbonation fires the mechanical one, which works independently of acid; a dish sweeter than the drink fires nothing and raises a caution instead.

The rules return the mechanisms that fired, and those mechanisms are the explanation shown to the reader. That is the entire output: a style, the interactions that would apply, and any cautions. If no mechanism fires, there is no match — the function does not fall back to a similarity score, because “these are both quite intense” is not a reason.

The negative cases are surfaced as prominently as the positive ones, and they are the part almost no pairing content includes. Tannin and chilli heat reinforce each other: a heavily tannic cider with a very hot dish makes the heat worse, reproducibly. A cider served alongside something sweeter than itself tastes thin and sour by comparison. Both lower the score rather than being quietly omitted.

Temperature changes what you taste, for reasons that are physical rather than conventional. Cold suppresses aroma — volatile compounds are less volatile — and it accentuates the perception of acidity and carbonation while dulling the response to sweetness. The same cider at 4 °C and at 12 °C tastes drier, sharper and less fruity at the colder end, without anything in the liquid having changed.

That gives a working rule with a reason behind it: the more a drink depends on aroma and texture, the warmer it wants to be; the more it depends on freshness and fizz, the colder.

Where a style record carries a serving range from a source, that range is what is shown. Where it does not, CiderHQ derives one from the two dimensions temperature actually interacts with. The derivation starts at 6 °C, adds a degree for every step the style sits below the top of the carbonation scale, adds half a degree for every step it sits below the top of the sweetness scale, rounds the result, and spans four degrees from there. A still, dry cider therefore lands warmer than a sparkling sweet one, which is the direction the mechanism predicts.

Every derived range is marked as derived in the table it appears in, and it is offered as a starting point rather than as a figure anybody measured. The arithmetic is coarse on purpose: a serving temperature stated to the degree would be asserting a precision that no palate and no source supports.

A “similar cultivars” list is easy to generate badly. Put every cultivar in a vector space, compute distances, show the nearest six: the result is a tidy ranked list produced from a space nobody has validated, in which the ranking carries an authority the underlying data cannot support. Worse, it always returns six — including for a cultivar with nothing genuinely comparable to it.

CiderHQ does something narrower and defensible. Two cultivars are shown together when they share a classification under the same system, or when they share a blend role. Sharing a classification counts for more than sharing a role, sharing several of either counts for more than sharing one, and anything scoring nothing is not shown at all. Apples are only ever compared with apples and pears with pears.

The reason for insisting on the same system is the same reason every classification statement on the site names its system. A cultivar classed as bittersweet under the Long Ashton scheme and one classed as douce-amère under the French families are not established as comparable by those labels: the two schemes use different thresholds, set for fruit grown in different climates, and the French scheme has a bitter family the English one has no name for. Matching within a system is a relationship the data can justify. Matching across systems would be an assumption presented as a result.

The consequence is that the list is sometimes short and sometimes empty, and that is the correct behaviour. A cultivar with an unusual combination of classification and role genuinely has few peers, and saying so is more useful than filling the space.