TL;DR for operators The paper argues that trustworthy AI agents need more than accurate final answers. Once an agent can retrieve documents, call APIs, write memory, modify databases, send messages, or coordinate with other agents, trust depends on whether the organisation can reconstruct how the output or action happened. The useful mechanism is: ...
TL;DR for operators AI deployment is no longer mainly a question of whether a model can produce something plausible. That problem has been solved often enough to become boring, which is usually when businesses start wasting money at scale. The live problem is control. Which model should be trusted on this workload? When should a system query another model, pay more, or stop? When an LLM produces an analytical “insight”, is it finding the pattern you care about, or merely discovering an aggregate confound wearing a nice blazer? ...
TL;DR for operators A frontier LLM judge is an expensive way to inspect every agent trajectory for reward hacking. This paper asks whether a much smaller detector can do most of that monitoring job at much lower cost. The answer is: yes, under the same information condition, and with important caveats. A 13.8M-parameter transformer encoder plus a logistic regression probe detects reward hacking in cleaned Terminal-Wrench trajectories with 0.9467 AUC and 0.8296 TPR@5%FPR. In the authors’ matched comparison, a reproduced gpt-5.4 judge reaches 0.9510 AUC and 0.7130 TPR@5%FPR on the cleaned sanitized-vs-baseline split.1 ...
TL;DR for operators NICE is useful because it does not ask whether a model has “social intelligence” as one grand, vaguely flattering trait. It breaks social intelligence into a diagnostic structure: 4 categories, 11 dimensions, 34 facets, and 137 Chinese-context ranking items. That matters because a model can look socially competent in aggregate while failing on the interaction behaviours that make or break real deployments. ...
Feedback is expensive. Anyone who has managed a classroom, a content team, a training programme, or a junior analyst cohort knows the pattern. The first draft is rarely the problem. The problem is the second draft, because the second draft requires specific feedback, delivered in language the learner can act on, without exhausting the person giving it. Multiply that by thirty students, ten assignments, uneven ability levels, and a calendar that refuses to become more generous. Suddenly “just give everyone personalised feedback” becomes one of those ideas beloved by people who do not have to do it. ...
Everyone wants the grand AI replacement story. The model eats the stack, digests the workflow, and emits profit. Very tidy. Also, usually nonsense. The more interesting pattern emerging in applied AI is smaller, less theatrical, and considerably more useful: the model is not the system. It is an intervention inside the system. It edits one field. It predicts one missing signal. It routes one candidate generator. It enters through a side door, preferably wearing a badge. ...
The current AI industry has a strangely theatrical relationship with intelligence. We judge models by the visible performance: the answer they print, the image they reconstruct, the attention map they expose, the number of reasoning steps they perform, the architectural flourish in the diagram. If the output looks sophisticated, we call the system capable. If the output looks wrong, we assume the capability is missing. This is convenient, measurable, and often completely misleading. Naturally, it is popular. ...
Generative AI has become very good at producing things that look finished. That is useful. It is also the problem. A polished answer can quietly overuse the same words until every research abstract sounds like it was written by one over-caffeinated committee. A video model can obey an edit instruction and still damage the background, distort motion, or leave a ghost of the removed object behind. The output looks like a product feature. The failure behaves like a production-control problem. ...
The procurement meeting is where public leaderboards go to look useful Benchmark scores are comforting because they compress chaos into a number. One model is 87.3, another is 84.9, and suddenly the procurement meeting has the emotional texture of financial discipline. Very mature. Very measurable. Also, very possibly irrelevant. The problem is simple. A company rarely wants “the best model on average”. It wants the best model for contract review, support triage, clinical note summarisation, SQL repair, claims handling, product search, or whatever unglamorous workflow actually pays the cloud bill. Public benchmarks are often too generic for that decision. Worse, the benchmark items may already be floating inside model training data, turning evaluation into a memory test with better typography. ...
Money makes AI less philosophical. In a chatbot demo, a model can “explore” by producing a strange answer, and the worst immediate outcome is usually a screenshot, a complaint, or a manager discovering the word “guardrail” again. In advertising auctions, exploration means spending actual budget into a live market. Every slightly adventurous bid has a cost. Every mistimed bid can drain budget before good traffic arrives. Every beautiful policy improvement can become an expensive little bonfire if it reaches production without a fallback. ...