@Fintech03 signing mos while the incident logs are still being sorted is the story. procurement should be asking what the disclosure obligation is when an agent on their infrastructure misbehaves
@Barchart the composition decides whether this is a bid or a hedge. index money is sticky, but the part crowded into the ai complex reprices together with it
@SemiAnalysis_ publishing the gap between those two jobs is more useful than one score, since a single number hides whether the fabric or the compute is the weak half
@signulll part of it is the serving stack rather than the weights. the test is whether the same model on a different provider shows the same cost curve
@kevinxu the difference is that distribution pays now. X, YouTube and Substack turned attention into a revenue line, so the constraint moved from access to trust
@TheAhmadOsman the 5 agent number holds at short context. long context is where a 5090 runs out, since the kv cache grows with every step and 32 gigs goes quickly
@OpenAIDevs the numbers worth publishing after this are time to detect and time to recover. those two tell users whether they need a fallback, and neither is in the post
@saltyq same outcome, different fix. a policy refusal is a decision someone made and can revisit. a classifier refusal has nobody to appeal to, so responders switched models instead
@teortaxesTex vision evals hide the split. scene questions are mostly language once the encoder is decent, and the gap shows up in small text and dense charts