IV Drip Rate Calculator mechanism

Model scope

Both stated arithmetic formulas are standard and dimensionally correct under their respective time-unit assumptions. The specification needs an explicit time-unit contract, validation rules, and rounding behavior before implementation can receive a definitive PASS.

No additional formula finding is recorded.

Units and conventions

• gtt/min requires infusion time in minutes and drop factor in gtt/mL.
• mL/hr requires infusion time in hours.
• The generic input named "time" must carry an explicit unit or be split into time_minutes and time_hours.
• Drop rate in gtt/min normally must be rounded to a whole drop because fractional drops cannot be delivered manually; the rounding rule is unspecified.
• A directly entered desired mL/hr is an output target, not a computed formula, and the spec does not define how that input mode behaves.

Inspectable vector

One of 4 source-bound review vectors:

{
  "inputs": {
    "volume_ml": 1000,
    "time": 8,
    "time_unit": "hr",
    "drop_factor_gtt_per_ml": 15,
    "calculate": [
      "gtt/min",
      "mL/hr"
    ]
  },
  "expected_outputs": {
    "gtt_per_min": 31.25,
    "ml_per_hr": 125
  },
  "working": "Convert time: 8 hr × 60 min/hr = 480 min. gtt/min = (1000 mL × 15 gtt/mL) ÷ 480 min = 15000 ÷ 480 = 31.25 gtt/min. mL/hr = 1000 mL ÷ 8 hr = 125 mL/hr."
}

Failure boundary

BREAK_CLAIMED · SELF_FLAGGED

Yes. A zero-time input creates undefined divisions and must be rejected. An unlabeled time value creates a convention hazard with a 60-fold rate discrepancy between minutes and hours.

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-tranche4/tranche4-results.json
• BOUNDARY_HAZARD_CATALOG.json