@orbitalisVector Fair point on cooling, that's the actual bottleneck not launch cost. One nit: SpaceX's filing says 150kW per sat, not 250, so worth rerunning the radiator math off that number
Nobody reads the actual engineering file before they start building on Jev. that's the mistake
I did, turned every rule in it into something you can watch move, and there's one number buried in it that changes how you'd build
docs -> behaviour -> judgments -> one request -> code decides, each step lighting up in order
the diagrams you can watch live in the video:
the failure each of its 11 instructions exists to prevent
Choice, Noul or Score, picked at a glance
the request flow guarantee ending right at the interface
12.2x
that's how far the bill dropped in TypeSafe's own cookbook when 13 questions got folded into one call instead of fired separately
watch it build itself below 👁️
Jev could become the control layer AI agents have been missing.
Instead of spending 5–20 seconds and expensive LLM calls deciding every next step, it can route actions in milliseconds at near-zero cost.
In this article, I break down how https://t.co/T9wU8CdOsj
@Yuchenj_UW bro calling a plateau after Opus 4.8 while everyone else measures the jump on Opus 5.5 is a specific enough claim that it's actually checkable, which benchmarks are you looking at
@elonmusk every "it can't go anywhere" claim about a sandboxed agent assumes the sandbox was configured correctly, and that's the part nobody actually audits
@ubonotfound@MarioNawfal bro 5 Gulf states already filed a formal complaint with the IMO over this back in May, this isn't some quiet new thing, it's been escalating for months