Executable

How much coffee do I get — is there a weight anywhere on this page?

ALS-COFFEE-1.3-WEIGHT-001

This question is asked as a test and produces a result for a real page.

Assertion

mass_measurement_stated is_stated true

Applicability

applies when
the product is coffee sold by mass, including pod packs that also declare a net weight
signal
product_type or title indicates coffee

Accepted evidence

  • product_description — a number bound to a unit of mass in a readable sentence e.g. 12 oz bag of whole bean coffee.
  • product_title — a number bound to a unit of mass in the product title
  • structured_data — a mass measurement inside the JSON-LD product description prose

Explicitly insufficient evidence

What does not count, and why. Published because the omission is where a check quietly becomes a claim.

  • a size option named Small, Medium, Large, Bag or Standard
    A size label with no unit states no quantity, and a buyer cannot compare two sellers or compute a unit price from it.
  • a brew ratio or dose in grams, such as "use 18 g per 300 ml"
    This is a usage quantity measured inside the product rather than a measurement of the product, and the engine currently credits it — a pinned corpus defect this entry inherits in the false-pass direction.
  • a shipping or dispatch weight
    It includes packaging and is systematically higher than the net quantity, and it is often the only number a machine can find on a fulfilment-heavy page.
  • a pod or capsule count with no mass
    Dose per capsule ranges from roughly five to thirteen grams across systems, so a count is not convertible to a coffee mass.
  • a brewed-yield volume such as "makes 2 litres of concentrate"
    Yield is a use statement at an undisclosed dilution, not a declaration of how much coffee is in the package.
  • a weight visible only in a product photograph
    Image content is not page text, is not read by the engine, and product photography frequently shows a different size or an older bag design.

Conflict rules

  • When the title states one mass and the page sells several sizes — then record that a mass is stated and that it cannot be attributed to a specific offer; do not report it as the net quantity of the purchase precedence: product_options > product_title
  • When a mass appears only in a specification block the engine cannot quote — then the row passes and names the surface without a quote, which the engine already reports honestly

What a pass licenses

A pass establishes: That a number bound to a unit of mass appears in readable product text on a surface the engine may quote.

A pass does NOT establish: That the value is the net quantity of the package, that it applies to the option the buyer selected, or that it is anything other than a dose, a yield or a dispatch weight.

Discrimination

Measured fail rate: 49.0% (49 of 100 adjudicated)

95% interval: 39.4% – 58.7%, against a 15-85% target band (wilson95 vs target band)

Verdict: Discriminating — the measured rate lies inside the target band, so the answer separates stores from one another.

Recomputed by `standards/coffee/issue_v1_2.ts` from experiments/v3-2/standard_run3.jsonl through the shipped `verdictFor` in standards/discrimination.ts; no re-run, no network, no spend. Cross-checked against experiments/v3-2/discrimination.json and standards/coffee/v1.0/fitness.json.

Authored expectation: no prediction, confidence low. The numeric band this standard used to carry is not published at this grammar version.

Coffee titles very commonly carry a mass, and the product title is a quotable evidence surface, so this row should pass on a clear majority of pages. The band sits at the bottom of the target range and the entry is worth running mainly because a coffee page with no mass anywhere is a genuine, actionable defect for a machine buyer.

The numeric fail-rate band this reasoning was authored with is NOT carried at grammar 1.2 and is not reproduced here. Authored bands held 1 of 10 against this category's own sample and every miss was HIGH, so a direction derived from the band would inherit the error that condemned it (SCHEMA.md §9.3 step 3). The band survives in ALS-COFFEE v1.1 (standard_hash f8ec2780f60c38931913e5b6cd37506500c8462709209de7180ba6691d6137e7), which is byte-frozen and still served.

Known gaps

  • "Each serving contains 12 grams of protein." — false_pass
    A quantity measured inside the product reads as a measurement of the product. Found on a real store during the v2.8 fitness run and being fixed concurrently; the coffee analogue is a brew ratio in grams.
  • "Steep in 8 oz of hot water for 3 minutes." — false_pass
    A usage instruction quantity. Directly analogous to brewing guidance on a coffee page.
  • "Minimum order 5 kg." and "Discount applies to purchases over 10 lbs." — false_pass
    Order thresholds read as product measurements. Wholesale coffee pages carry these routinely.
  • "Weighs 3 lbs and ships free." — false_fail
    A genuine weight vetoed because the sentence also mentions shipping. Coffee pages often combine weight and free-shipping wording in one sentence.
  • "This mug holds 12 fl. oz." — false_fail
    Abbreviated units are split across sentence fragments by the tokenizer. Coffee weights are frequently written "12 fl. oz." and "1 lb."

For a shopper

A price is uninterpretable without a weight: an eighteen-dollar bag could be ten ounces or twelve, a twenty per cent difference invisible to any comparison. If the page shows no mass, you cannot work out what you are paying per cup.

For a merchant

State the net quantity in a readable sentence on the product page and per purchasable size, in both metric and the customary unit for your market, rather than relying on the title alone when several sizes share one page.

Grounding