Page actions
instrument / verified-clean
Glycemic Load Calculator
The current ledger marks this instrument verified clean within the source-bound verification corpus.
Inspectable records
Ledger state
The current ledger marks this instrument verified clean within the source-bound verification corpus.
- Area
- Biology, Medicine & Pharmacology (educational estimates only — every panel labeled not-medical-advice)
- Tranche
- tranche-7
- Evidence ID
- t7-079
- Ledger rows
- 1
No ledger note is attached.
Review findings
The core arithmetic is correct, and the existing educational-not-medical-advice label is appropriate. Release requires explicit category thresholds, a definition of carbohydrate grams as available/digestible carbohydrate, a stated GI reference convention, and handling for missing or undefined GI values.
Formula and scope findings
- GL=(GI×carb_g)/100 is the standard glycemic-load formula when GI is the food's GI relative to the glucose reference scale (glucose=100) and carb_g means grams of available/digestible carbohydrate in the stated portion.
- The category thresholds are not specified. A common convention is low ≤10, medium 11–19, and high ≥20, but the instrument must explicitly publish its chosen boundary rules.
- The carbohydrate input is ambiguous: total carbohydrate versus available carbohydrate (total carbohydrate minus fiber and sometimes sugar alcohols). Standard GL calculations generally use available/digestible carbohydrate.
- GI is highly dependent on food variety, preparation, ripeness, processing, and test protocol; a lookup value must identify the food form and source convention.
Unit assumptions
- GI is dimensionless and uses the glucose-reference scale, with glucose assigned GI=100.
- carb_g is grams of available/digestible carbohydrate in exactly the portion being evaluated, not grams per 100 g unless the portion is 100 g.
- The worked category outputs assume the conventional thresholds low ≤10, medium 11–19, and high ≥20.
- GI should normally be constrained to 0–100; carbohydrate grams should be nonnegative.
Boundary hardening
BREAK_CLAIMED · SELF_FLAGGED
The extreme-magnitude vector causes mathematical overflow in ordinary floating-point arithmetic, yielding Infinity or a non-finite result unless inputs are rejected or arbitrary-precision arithmetic is used. Category thresholds are also unspecified, and unit ambiguity can change the result substantially.
Errata and corrections
No applied erratum is attached to this unique-name record.
Inspectable example
4 review vectors are recorded. One source-bound sample is shown below.
{
"inputs": {
"food": "glucose solution",
"glycemic_index": 100,
"carbohydrate_g": 25,
"portion_description": "portion containing 25 g available carbohydrate"
},
"expected_outputs": {
"glycemic_load": 25,
"category": "high"
},
"reference_data": {
"food": "glucose",
"glycemic_index": 100,
"source_convention": "International GI reference convention; glucose reference assigned GI=100 (widely tabulated standard value)"
},
"working": "GL=(GI×carb_g)/100=(100×25)/100=2500/100=25. Using low ≤10, medium 11–19, high ≥20: 25 is high."
}Related workflows
No source-defined multi-instrument workflow membership is recorded.
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
VERIFIED_LEDGER.json · VERIFIED_CLEANevidence-tranche7/tranche7-results.jsonBOUNDARY_HAZARD_CATALOG.json