Protein Requirement Estimator mechanism

Model scope

The arithmetic formula is sound, but the instrument is not fully specified because the activity/goal categories and their factor mappings are absent, and the meaning of recommended protein range is unclear. The honest-label wording is appropriate for an educational estimate, but the interface should clearly state that factors are general references and not individualized medical or nutritional advice.

• The multiplication formula protein_g = weight_kg × factor_g_per_kg is correct only when weight is in kilograms and the factor is in g/kg/day.
• The specification does not provide the required reference table mapping each activity/goal category to a specific factor or factor range, so the result cannot be determined from the declared inputs alone.
• It is ambiguous whether the output should be one value for the selected goal or a lower-to-upper range spanning 0.8-2.2 g/kg/day.

Units and conventions

• weight must be entered in kilograms; if entered in pounds, convert using 1 lb = 0.453592 kg before applying the formula.
• factor units are grams of protein per kilogram of body weight per day (g/kg/day).
• The test vectors use provisional factors solely to verify arithmetic; they do not validate an unstated clinical or nutritional reference table.

Inspectable vector

One of 4 source-bound review vectors:

{
  "inputs": {
    "weight_kg": 70,
    "goal_category": "sedentary/general adult",
    "factor_g_per_kg": 0.8
  },
  "expected_outputs": {
    "protein_g_per_day": 56
  },
  "working": "1. Start with weight = 70 kg and factor = 0.8 g/kg/day.\n2. protein_g_per_day = 70 × 0.8.\n3. 70 × 0.8 = 56.\n4. Expected output = 56 g/day."
}

Failure boundary

BREAK_CLAIMED · SELF_FLAGGED

The extreme-weight test produces Infinity in plain JavaScript arithmetic, and the zero-weight boundary can produce an invalid but numerically accepted 0 g/day unless validation rejects it. An unspecified weight unit can also change the result from 338.8 to approximately 153.677093 g/day.

Other records

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

• VERIFIED_LEDGER.json
• evidence-tranche5/tranche5-results.json
• BOUNDARY_HAZARD_CATALOG.json