Primary finding
Ambiguous units in modeThresholds for rate vs total
- memory/goals.json:32-35
buildModeOnDailyRate implies a rate (DIEM/day), while a single unit field of "DIEM" can be misinterpreted. Mixing a rate and a total under one shared unit creates ambiguity for downstream logic and increases the likelihood of incorrect threshold evaluation.
Recommendation
Disambiguate by providing explicit units per threshold (e.g., rateUnit: "DIEM/day", totalUnit: "DIEM") or encode each threshold as an object with value and unit fields. Document the expected semantics clearly and validate with a schema.