Anthropic's CPO just killed the boundaries between three Claude products. you should kill them inside your prompt too. Mike Krieger dropped a line most builders skipped: > "we're shipping our harness strategy, not a product." he doubled down later: the separation between the three products is "a broken abstraction we need to fix." Anthropic spent a year separating Claude AI, Cowork, and Claude Code into distinct surfaces. their own CPO now says the separation was the bug. they're collapsing it into one harness. the same abstraction is broken inside every Claude prompt you've written. you ask Claude to predict, pick, size, exit, and audit: five jobs glued together pretending to be one workflow. then you wonder why nothing comes out clean. i ran into this on a Polymarket bot. the prediction-layer version asked Claude to do everything. it lost money. then i stripped the prompt down to one job: veto an entry i had already decided to take. nothing else. no picking, no sizing, no exit logic. over 90 days the new prompt blocked 128 trades: 44 of them would have lost me $5,360. the bot's blocked trades saved more dollars than its approved trades earned. Krieger's lesson at the product layer is the same lesson at the prompt layer. - one harness. - one job. - fewer broken abstractions stitched together. Anthropic is collapsing their stack. you can collapse yours tonight. stop stitching five jobs into one Claude call.