Opus finding
Mode field inconsistent with documented threshold semantics
lowapi-contractmedium
- memory/goals.json:5-6
- memory/goals.json:24-29
The milestone description says build mode triggers at 100 DIEM total, but modeThresholds also exposes buildModeOnDailyRate: 5 with no documented unit/window (per-day? in DIEM?) and no precedence rule between the two thresholds. A consumer that evaluates daily rate could flip to build mode well before the 100 DIEM milestone is met, contradicting the milestone description. The contract between mode, milestones[*].status, and the two thresholds is ambiguous.
Recommendation
Document in the file (or in an adjacent schema/spec) the precedence: e.g., 'mode becomes build when EITHER threshold is satisfied' vs. 'AND', and specify the time window/unit for buildModeOnDailyRate. Alternatively collapse to a single canonical trigger to avoid drift between mode and milestone.status.