Causal-Inference

TL;DR for operators Bellot and Dhir’s Foundation Models for Partial Causal Identification1 targets a specific failure mode in automated causal analysis: observational data may narrow a causal answer without determining one unique value. The proposed model is trained once to return a distribution over still-compatible causal or counterfactual answers, rather than solving a new bound-optimization problem for every dataset and query. ...

TL;DR for operators A RAG system can fail even when retrieval looks superficially healthy: several top-ranked documents repeat the query vocabulary, while the document that actually contains the answer sits lower in the list. The paper studies a reranking rule designed specifically for that situation.1 Instead of rewarding more query-document overlap, it removes words that exactly or semantically echo the query and scores what remains. In an eight-theme controlled keyword-stuffing diagnostic, this semantic variant improves mean target rank from 2.88 to 1.25 and pushes stuffed distractors from mean rank 2.00 to 4.50. ...

The formula is not a clerical detail A business asks a causal question: What happens if we change X? The analytics team returns a formula. Everyone relaxes. The effect is identifiable, the notation looks official, and a graph somewhere has probably been blessed by someone with a PhD. Excellent. Time to move to dashboards. ...

A prediction looks harmless when it is presented as “just information.” A loan officer sees a default-risk score. A doctor sees a survival estimate. A welfare caseworker sees a predicted probability of program success. The model does not press the button. The human still decides. Everyone in the room can therefore relax, at least until the audit committee arrives with coffee and regrettable questions. ...

Causal claims are cheap now. A model can look at variable names such as advertising spend, web traffic, sales conversion, and customer churn, then produce a causal story in seconds. The story may even sound sensible. That is precisely the problem. In business analytics, “sensible” is often the polite costume worn by “untested.” ...

Teams are easy to draw and hard to govern. Put five AI agents in a workflow diagram and everything looks reassuringly corporate: one planner, one researcher, one coder, one critic, one manager. Give them arrows. Add a dashboard. Call it orchestration. Investors relax. Engineers nod. Consultants quietly increase the font size on the word “autonomous.” ...

Moderation teams do not usually lose because they see nothing. They lose because they see too much: thousands of accounts posting near the same topic, near the same time, with enough similarity to look suspicious and enough difference to remain deniable. Some are campaign assets. Some are enthusiastic humans. Some are bots. Some are people who simply saw the same trending story and behaved like everyone else, which is annoying for both democracy and data science. ...

Humidity looks harmless on a scatter plot. Actually, in this paper, it looks worse than harmless: it appears negatively correlated with electricity demand. That is the kind of result a busy forecasting team might quietly accept. Add humidity as a feature, let the model figure it out, move on. The grid will not wait politely while everyone debates Pearl diagrams. ...

A product team launches an AI assistant. The demo works. The benchmark looks respectable. The model even says “I’m confident” with the serene authority of a consultant who has never owned a pager. Then the real users arrive. Some ask ambiguous questions. Some ask adversarial questions. Some ask perfectly normal questions that happen to sit outside the model’s competence. The assistant still answers. Sometimes it refuses too often. Sometimes it refuses too late. Sometimes its confidence score is less a forecast and more a decorative sticker. ...

TL;DR for operators Clinical analytics teams already know the unpleasant truth: observational data is cheap, rich, and biased in ways that do not politely announce themselves. The paper behind this article proposes a way to make that bias-hunting process less artisanal. Instead of asking experts to manually inspect every causal-tree rule, the framework lets causal trees segment patients, asks medical LLM agents to suggest plausible confounders using decomposed prompting plus retrieval, sends those suggestions through expert validation, then recursively focuses on samples whose treatment-effect estimates still have wide confidence intervals.1 ...