Grok Bot 团队用 Jev 搭六席交易台
演示中数据 agent 纠正了错误诊断，避免五个工程师白干；有交易员照搬这套分工，用三个 agent 向 Jev 要判断、三个算数、一个主管路由，硬阈值卡住下单。
WTF, THE GROK BOT TEAM ALMOST SENT FIVE AI ENGINEERS TO FIX THE WRONG THING two people building Grok Bot were on stage reading a checkout chart for a demo airline. they saw customers drop off and blamed the seat picker their data agent Ashley came back with three words, "quick correction first" the leak was one step earlier, search to fare selection. only 53.8% made it through. the seat step held at 82.4% one of the presenters admitted they had read the chart wrong watch what happened after the bot corrected them > Ashley sent the real problem to Pete > Pete wrote the product spec in Notion > Emily split it between five AI engineers > Pixel designed the mockup while Nova launched a cloud coding agent Emily was specifically told not to code, her job was to hand out work and check what came back Nova still needed a human yes before launching the coding agent that one correction stopped the wrong diagnosis from becoming five different engineering tasks the team's final slide said "hierarchy beats one mega-prompt" now picture the same bad read with a wallet attached. the wrong decision doesn't become a bad spec, it becomes a buy order one trader already built a six-seat Grok Bot desk with the same division of labor. three agents ask Jev for judgments, three do the math, a chief routes the work and hard thresholds say when a trade can happen every role, prompt, file and threshold is in the article quoted below ↓ save the quoted guide before giving one giant prompt a wallet
这条是引用着另一条写的：x.com/savipww/status/2102720919185617314