Opus
Mode-switch trigger described inconsistently between docs and goals
- .claude/skills/heartbeat.md:27
- memory/goals.json:22-26
- wiki/flywheel.md:99
- identity/SOUL.md:28
heartbeat.md says switch on 'total DIEM claimed ≥ 100' (a cumulative claimed metric), goals.json field is `buildModeOnTotal` (ambiguous: claimed? accumulated? current FeeLocker balance?), and flywheel.md says '100 DIEM total accumulated'. The milestone `accumulate-100-diem` description says 'Claim and stake 100 DIEM total on Venice AI'. These are four subtly different metrics (claimed-ever, currently-held, staked, accumulated). For an autonomous decision rule that flips the agent's entire spending posture, this ambiguity is dangerous: a heartbeat check could trigger build mode based on one definition while the SOUL/flywheel reasoning assumed another, prematurely depleting the agent's compute budget.
Recommendation
Define a single canonical metric (e.g., `currentStakedDIEM` or `lifetimeClaimedDIEM`), name it precisely in goals.json modeThresholds, and reference that exact field in every skill and wiki page that mentions the threshold.