there's a reason the biggest Claude deployment in the world calls it an advisor while you're still treating yours as a trader. Mario Rodriguez ships Claude to millions of GitHub developers. Brad Abrams builds the platform under it. neither of them lets the model make the final call. their core architectural commitment is what they call the "Advisor strategy": Claude reviews, suggests, flags. a human or a deterministic rule decides. every layer of GitHub's stack enforces this: > offline evals filter before launch. > a harness wraps the model. > caching keeps cost predictable. all of it exists to make sure Claude advises and something deterministic decides. i landed on the same shape independently, building a Polymarket bot. the first version asked Claude to predict prices and trade them. it lost money. the second version stripped Claude down to one job: review the thesis i had already written and find the strongest reason to reject it. 90 days of running the new prompt. 28 entries blocked. 44 would have lost me $5,360 if i'd taken them. the refused trades made more money than the executed ones. GitHub does this for millions of developers. you should be doing it for one Claude call. build the harness around your prompt before you build anything around your bot. advisor in. trader out.