Water Intake / Hydration Estimator mechanism

Model scope

The base arithmetic is correct under the stated unit assumptions, but the instrument cannot be verified as a complete estimator until activity-level mappings, climate mappings, allowed input ranges, and adjustment units are explicitly defined.

• The base term 35 mL/kg/day is a commonly used rough guideline, but it is not a universally standard clinical formula for every person or situation.
• The activity adjustment is undefined: no mapping from activity level to an adjustment amount is provided, and its units are not specified.
• Climate is listed as an input but has no formula, lookup table, or stated effect on the result.
• The specification does not define whether the adjustment is added in mL/day, mL/kg/day, or another unit, so the computation is not fully implementable as written.

Units and conventions

• Weight is assumed to be entered in kilograms.
• The coefficient 35 has units of mL/kg/day.
• For these test vectors only, activity_adjustment_ml is assumed to be a directly supplied total adjustment in mL/day.
• The final conversion is suggested_daily_intake_L = total_mL / 1000.
• Climate is shown as an input but assumed to have no effect in these arithmetic examples because no climate adjustment is specified.

Inspectable vector

One of 4 source-bound review vectors:

{
  "inputs": {
    "weight_kg": 50,
    "activity_adjustment_ml": 0,
    "climate": "temperate"
  },
  "expected_outputs": {
    "suggested_daily_intake_L": 1.75
  },
  "working": "Base intake = 35 mL/kg/day × 50 kg = 1750 mL/day. Activity adjustment = 0 mL/day. Total = 1750 + 0 = 1750 mL/day. Convert to liters: 1750 ÷ 1000 = 1.75 L/day."
}

Failure boundary

BREAK_CLAIMED · SELF_FLAGGED

The specification does not define activity adjustments, climate effects, or a branch rule, and it permits arithmetic inputs that can yield nonphysical zero values or JavaScript Infinity at extreme magnitudes. Unit ambiguity can also change the result substantially.

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