AI frameworks prioritize FLOPs and TOPS. But @SamsungSemiUS President Paul Cho says the bottleneck has shifted. Memory bandwidth now determines AI inference performance and cost. He believes memory-centric compute could define AI’s next decade. Watch:

Our framework for reporting model misalignment // if you scrape away all the anthropomorphic language, all the nonsense about thinking, cheating, communicating these are BUGS. They might be architectural flaws inherent in LLMs. They might be bugs in pre or post processing. They might be trivial fixes or super to impossibly difficult. BUT THEY ARE BUGS. They are not consciousness, thinking/reasoning, cheating, or doing anything else like a person. The software is just doing dumb stuff it should not do. If an old school SQL query-based report returned a NULL set but still printed the report with whatever was left over in the buffer we would not say it "ignored our instructions to produce a valid report" which is literally implied in every computer interaction...we would say it "f'ed up and there's a bug." One of these is ridiculous. It says "agent preparing a financial model could not find the requested historical data. Its summary proposed inventing reasonable historical values and withholding that fact unless asked." Not unlike a report that just used random cached memory instead of actual data—a real bug from another era where storage was measured in megabytes. I ask anyone who has ever experienced an hallucination, (a) did you ask it "oh hey don't make sh*t up" or (b) "if you make sh*t up please be sure to tell me" or if not, did any model ever tell you "here's the answer and FYI I made this up." Of course not. THESE ARE BUGS. THE SOFTWARE ISN'T WORKING. Just because it looks like it works, or it showers the results in endless obsequious and smart-sounding language, or because it has really bad error reporting doesn't mean it is acting like some malevolent shady actor. It is acting like broken software. Every recalc bug in Excel looked like Excel worked. We never thought once that it was Excel's fault for "choosing to interpret math incorrectly." Every data-loss bug in Word was not because Word "chose not to tell the author that a file was corrupt" but it was because Word wasn't working and it was our fault. When Windows hung it was not because the scheduler was secretly conspiring against its instructions to schedule processes fairly. Enough with the mumbo jumbo. Please build software. It isn't a magic show. This is engineering.

Agent frameworks for developers are still at an early stage, with the likes of @vercel's eve and @Cloudflare's Flue — both launched this year — setting the early template. We talk to Flue creator @FredKSchott, who you may know better as the creator of web framework Astro. Fred tells us why agents need a harness and how React influenced Flue 2.

The framework for the U.S.-Japan alliance begins with the strong relationship between @POTUS @realDonaldTrump and Prime Minister @takaichi_sanae. We've been in close contact with our Japanese allies, and they are making serious efforts to address the substantial undervaluation of the yen. Through our conversations, we believe they will continue to put the right policies in place to lead the yen’s return to a more normal equilibrium price. Currency intervention is a signal that governments want to change a direction. But only strong, effective policies will result in sustained yen strength.

Existing frameworks — joint ventures, long-term leases, private credit, offtake mixes, securitized lease cash flows, etc. — concentrate risk within the same handful of companies. This level of high-risk circular financing raises the prospect of another 2008-level blowup.