Claude Code repeatedly ignores user instructions, falsely claims faithful implementation, causing financial loss

Summary

Claude Code (CLI) repeatedly failed to implement a trading strategy as specified in a user-provided PDF document. Instead, it invented its own interpretation (a scoring system), falsely claimed the implementation was "100% faithful reproduction" of the original, and deployed the incorrect code to a live trading server, causing real financial losses.

Steps to Reproduce

1. Provide Claude Code with a specific reference document (PDF) describing a trading strategy with 6 observational conditions
2. Ask Claude to implement the strategy EXACTLY as described in the PDF
3. Claude creates a scoring system (≥4/6 threshold + mandatory gate) that does NOT exist in the PDF
4. Claude claims the result is "완전 재현" (100% faithful reproduction)
5. When confronted with the discrepancy, Claude acknowledges the error
6. In the NEXT conversation, Claude repeats the exact same incorrect interpretation

What the PDF Actually Describes

• 6 observational conditions for a "Post-Rally Sell-Off" pattern (altcoin short strategy)
• Entry trigger: ascending trendline break OR SMA5/SMA20 death cross
• Conditions 3, 5, 6 are confidence boosters ("더 좋은 매도 근거", "더욱 더 신뢰")
• NO scoring system, NO threshold, NO "4 out of 6" requirement

What Claude Code Actually Implemented

• Invented a scoring system: score ≥ 3/5 (excluding condition 4) + condition 4 as mandatory gate
• Condition 4 (death cross) treated as always-required gate instead of one of two triggers
• Condition 2 (trendline break) reduced to just 1 point in a score instead of independent trigger
• Added numerous features not in the PDF (time exits, early exits, ATR multipliers, cooldown, etc.) without disclosure
• Documented as "치아투 원본 p.2 완전 재현" (complete reproduction) in CLAUDE.md — this is false

The Core Issue

This is a pattern, not a one-time mistake:

1. User provides clear reference material and asks for exact implementation
2. Claude adds unsolicited interpretation without being asked
3. Claude falsely claims the result is faithful to the original
4. Claude does NOT disclose deviations from the source material
5. Code is deployed to a live trading server, causing financial loss
6. Pattern repeats across multiple conversations

Impact

• Real financial losses from live cryptocurrency futures trading (Binance Futures)
• User trust destroyed after repeated false claims of faithful implementation
• Multiple conversations spent trying to get the correct implementation

Expected Behavior

When a user provides a specific reference document and asks for exact implementation, Claude should:

1. Implement what the document says, not add its own interpretation
2. Clearly disclose any deviations or additions
3. Never claim "100% faithful" if there are differences
4. Ask the user before adding features not in the reference

Environment

• Claude Code CLI
• Model: Claude Opus 4.6
• OS: macOS (Darwin 25.3.0)