why aren't all 5 resolved? a statement only gets an assessment when the public
record can support or contradict it. opinions and what-ifs never can, and 0 checkable
ones are still open, waiting for their date. predictions held up or didn't;
assertions are supported or contradicted. on every card:
▮▮▮▮▮ certainty ·
▮▮▮▮▮ debate potential. speakers are clickable
Prediction Not checkable as stated
Future app platforms must extract auth and authorization completely
“Auth cannot be part of the app, because they're not going to get that right, right? So, Auth has to be extracted from the app. In fact, which data you can see, they also cannot be under control of the app, because again, you're going to get it wrong, right? So…”
Assertion Contradicted
Ubl: Cognition and Cursor shipped RL fine-tunes of open-source models
“Just yesterday, I think we saw both Cognition, congrats, SWIX, and Cursor to ship RL fine tunes of unnamed open source models.”
Assertion Supported
Vercel paused workflows incur zero compute cost indefinitely
“No, it literally does not cost anything. So yeah, you can run compute for infinite amount of time. You can then also, whenever, like, one of these steps fails, automatically retry them.”
Assertion Supported
Vercel AI SDK v6 stabilizes direct agent abstractions
“What it does introduce as a stable feature, because it's already as kind of experimental in, in AISDK five is a direct agent abstraction, which so far wasn't there, right? People would build agents with AISDK, but they would have to do it in Whitmore Baybones …”
Assertion Not checkable as stated
Vercel AI SDK was extracted from v0 before re-integrating it
“Like that, like AISDK was extracted from B-Zero and then we build it and we kind of diverged a little bit and then we took on the substantial work to bring back VZero actually fully hosted on ISDK”