Causal DAG

Why it matters

A correlation tells you two things move together. It does not tell you whether one causes the other, whether a third thing causes both, or whether you have accidentally created the link yourself by how you collected the data. Most real decisions turn on the causal question — if we change this, will that change? — and most arguments about evidence are really arguments about which causal story the same numbers support. A causal DAG is a way to draw the story explicitly, as a map of variables and arrows, so that the assumptions you are quietly making become visible, and so that the math can tell you which of your questions the data can actually answer.

For example: a study finds that towns with more ice-cream sales have more drownings. Read carelessly, the correlation suggests ice cream is dangerous. Draw the map and the trap is obvious — summer heat drives both, separately. Heat is a confounder: a common cause sitting upstream of both ice cream and drowning, manufacturing a correlation between them that has nothing to do with one causing the other. Once heat is on the map you can see exactly what to do — compare ice-cream sales and drownings within days of the same temperature, and the spurious link dissolves. The diagram did not just describe the problem; it told you which variable to hold fixed to get a clean read.

What it reveals. The causal structure behind a correlation — which variables cause which, where the confounders sit, and therefore whether the effect you care about can be read off the data you have, or whether the data can only ever mislead you.
How it changes the read. You stop asking “are X and Y correlated?” and start asking “if we intervened on X, would Y change — and what exactly would we have to hold fixed to see that effect cleanly rather than a confounded shadow of it?”
When to foreground it. A genuinely causal question — will this policy work, can this observational study be read as evidence for action, what is driving this outcome — where confounding is plausible and getting the causal direction right matters more than estimating an exact number.
What you’d miss without it. That the controls in a regression are a causal claim in disguise: adjust for the wrong variable and you can create bias rather than remove it. The diagram is what tells you which variables to control for and, just as importantly, which ones to leave alone.
Where it misleads. The graph is only as good as the assumptions drawn into it; a missing arrow is a confident claim that no effect exists, and a missing variable can invalidate the whole verdict. It also cannot handle feedback loops, and it does not produce a number — it tells you whether the effect is answerable, not how big it is.

Realtime examples

See real, dated analyses where this mode mapped the causal structure behind a claim in the news → Causal DAG on Main Street Independent

How to invoke it in Ora

You have a causal question — whether an intervention would produce a target effect, or whether an observed correlation can honestly be read as cause and effect — and you want the confounding structure made explicit before anyone reaches for a number.

Describe the outcome and the candidate causes and ask:

“Causal DAG that separates confounders from the causal path — I want to know what would happen if we intervened on [X]. What confounders bias the existing observational evidence? Pearl-style with do-calculus.”

The phrases causal DAG, separates confounders from the causal path, what would happen if we intervened, backdoor criterion / identifiability, and Pearl-style / do-calculus are what route you here. Bring three things: the outcome you care about, the candidate causal variables (including the third factors you suspect are doing hidden work — parental income, prior schooling, the business cycle, whatever fits your domain), and the specific intervention or counterfactual you want answered. You do not have to name every variable; the mode will infer additional nodes and relations as it draws the graph.

Two boundaries worth knowing. If the system runs on feedback loops — vicious or virtuous cycles that feed on themselves — a DAG cannot represent it, because the apparatus is acyclic by definition; the systems-dynamics-causal mode fits. And if you are diagnosing a single past failure rather than reasoning about a general intervention, root-cause-analysis or process-tracing is the better tool. This mode produces the structural groundwork an estimation effort starts from; it does not itself estimate how large the effect is.

How it works

Start with a real fight that a graph settles. For years, studies showed that women taking hormone-replacement therapy had less heart disease, and the natural reading was that the therapy protected the heart. Then a randomized trial found the opposite — the therapy slightly raised the risk. How could the same direction of effect flip? The answer is that the women who took hormone therapy were, on average, wealthier and more health-conscious, and wealth and health-consciousness independently lower heart-disease risk. Those background traits were a common cause of both taking the therapy and having a healthy heart, and they had quietly inflated the apparent benefit. The observational studies were measuring the women, not the medicine.

That common-cause variable has a name — a confounder — and confounders are the reason a causal DAG exists. A DAG, a directed acyclic graph, is just a picture: each variable is a dot (a node), and an arrow from one dot to another is a claim that the first directly causes the second. “Directed” means the arrows have a direction, because causes come before effects. “Acyclic” means no loops — you cannot follow the arrows around and end up back where you started, because a thing cannot be its own ancestor. The discipline of the picture is that the missing arrows are claims too: leaving out an arrow between two nodes asserts there is no direct effect there. Drawing the graph forces every assumption into the open, which is exactly where you want them, because the assumptions are usually where the real disagreement lives.

Once the graph is drawn, the arrows fall into three structural roles, and telling them apart is the whole game. A confounder sits upstream of both the cause and the effect, with arrows pointing into both — like wealth pointing into both hormone therapy and heart health, or summer heat pointing into both ice cream and drowning. A mediator sits on the causal path, downstream of the cause and upstream of the effect — it carries the effect through itself, like “labor costs” sitting between a minimum-wage increase and employment. A collider is the sneaky one: it sits downstream of two causes, with arrows pointing into it from both. And here is the counter-intuitive rule that trips up careful people: you should control for confounders, but you must not control for colliders, because conditioning on a collider creates a spurious link between its two causes that was never there. The classic example is selection bias — if you only study hospitalized patients, and two unrelated conditions each independently raise your odds of being hospitalized, then among the hospitalized the two conditions will look negatively correlated, purely because you have conditioned on the collider “got admitted.” You manufactured the correlation by how you picked your sample.

So the graph gives you a rule for what to hold fixed. “Controlling for the right things” is not a matter of throwing every available variable into a regression — that is how you accidentally adjust for a collider and inject bias. The graph tells you which set of variables to adjust for in order to block every back-door path — every sneaky route from cause to effect that runs backward through a confounder — while leaving the genuine causal path and the colliders alone. Pearl’s machinery makes this mechanical: given the graph and the effect you want, the back-door criterion names the right adjustment set, and when the needed variables are unmeasured, the front-door criterion and the broader do-calculus can sometimes still recover the answer through a mediator you can measure.

The deepest idea is what the arrow really means, and it is captured by the do-operator. There is a world of difference between seeing and doing. P(recovery | took the drug) is what you observe — and it is contaminated by every reason a person had for taking the drug in the first place. P(recovery | do(took the drug)) is what would happen if you reached in and made everyone take it, severing the drug from all its usual causes — which is precisely what a randomized trial does, and precisely the quantity a policy-maker actually wants. The genius of the causal DAG is that it lets you compute that interventional “do” quantity, when it is computable at all, from ordinary observational “see” data — by reading off the graph which confounders to block. It tells you, before you spend a dollar collecting data, whether your causal question is even answerable from the kind of evidence you can get. That verdict — identifiable or not identifiable — is the diagram’s most valuable single output.

Framework & implementation

This section uses Ora’s own terms for the parts of an analysis, so that if you open the actual mode file they line up. Each is glossed in plain language on first use.

Pipeline execution

Causal DAG is an atomic mode in the causal-investigation territory — it is the territory’s depth-thorough, formalism-explicit member, the one that commits to a formal directed graph rather than an informal chain. It runs at Gear 4, Ora’s most thorough setting: a Depth analyst and a Breadth analyst work the causal structure in parallel and then critique each other (cross-adversarial evaluation) before a consolidator integrates the result — the breadth pass widens the variable inventory so confounders are not missed, the depth pass presses each structural claim and each identifiability verdict.

The pass runs five steps in sequence. It elicits the variables — the outcome of interest and the candidate causes. It constructs the causal graph, encoding the domain assumptions about which variable directly influences which, including the deliberate absent-arrow assumptions (the no-effect claims). It classifies the structural roles — sorting every node into confounder (a common cause of both treatment and outcome, which biases observational comparison), mediator (a node on the causal path, carrying part of the effect through it), collider (a descendant of two upstream variables, which induces spurious correlation if conditioned on), and instrument (an upstream variable that moves the treatment but not the outcome directly). It applies the identification criteria — the back-door criterion for the adjustment set, the front-door criterion when back-door variables are unmeasured, and do-calculus when neither standard criterion applies — and returns an explicit verdict on whether the effect is identifiable from observational data given the graph. Finally it locks the Pearl rung, naming which of the three causal questions — association, intervention, or counterfactual — the analysis actually supports, because the single most common error in applied causal reasoning is treating evidence for one rung as evidence for another.

The mode’s reasoning tools ride in its ANALYTICAL PERSPECTIVES block — the lenses it loads as it works. The load-bearing ones here are the confounder / mediator / collider classification (the discipline of sorting every node by its structural role before deciding what to adjust for), the back-door / front-door / do-calculus identification lens (the formal machinery that derives the right adjustment set rather than guessing it), and the ladder-of-causation lens (Pearl’s three-rung distinction between seeing, doing, and imagining, which keeps the analysis honest about which kind of claim it is making).

Output contract

The deliverable is a fixed set of sections, so the causal reasoning is auditable rather than a persuasive narrative: Causal Question — Pearl Rung Locked (the question restated, the rung named — association, intervention, or counterfactual — and the formal do(...) operator written out), Variable Inventory with Roles (every variable tagged as treatment, outcome, confounder, mediator, collider, instrument, or post-treatment descendant), DAG Specification split into the arrows present (each a stated causal claim) and the absent-arrow assumptions (each a stated no-effect claim), Confounder / Mediator / Collider Classification (what to adjust for, what never to condition on, and why), Identifiability Verdict (identifiable or not, the criterion applied, the exact conditioning set, and the assumptions the verdict rides on), Intervention Answer (the qualitative direction of each effect under the do(...) intervention, with channels named), Assumption Inventory (Fragility-Ordered) (each assumption ranked by how easily it could break and what would falsify it), and Confidence per Finding (how strong each conclusion is and where it softens).

Origin and evidence

The apparatus is the work of Judea Pearl, who turned causation from a word philosophers argued about into a calculus a computer can run. Causality: Models, Reasoning, and Inference (2000) is the formal anchor — it introduces the do-operator, the back-door and front-door criteria, and do-calculus, the rules that decide when an interventional effect can be recovered from observational data. The Book of Why (Pearl & Mackenzie, 2018) is the accessible companion, and it names the organizing idea this mode is built on: the ladder of causation, three rungs — seeing (association), doing (intervention), and imagining (counterfactual) — each demanding strictly more than the one below it. The graphical tradition was developed in parallel by Peter Spirtes, Clark Glymour, and Richard Scheines, whose Causation, Prediction, and Search (1993) established the algorithms for discovering causal structure from data. On the counterfactual side there is an adjacent and formally equivalent tradition — the potential-outcomes framework associated with Donald Rubin — which reaches the same conclusions through a different vocabulary; this mode commits to the graphical language because the graph is what makes the structural assumptions visible.

Applications and common uses

Policy evaluation from observational data. The native use: asking what a minimum-wage change, a tuition policy, or a remote-work mandate would do, when a randomized trial is impossible and only observational evidence exists.
Epidemiology and public health. Deciding which variables to adjust for when estimating a treatment effect from a cohort study — the field where confounding and collider bias do the most damage and the DAG is now standard practice.
Reading a contested study honestly. When the same observational finding is being cited as proof of an intervention’s effect, the graph exposes whether that reading is licensed or whether confounding could fully explain it.
Experiment and study design. Drawn before data collection, the graph identifies which variables must be measured to make the eventual analysis identifiable — turning “which controls do we need?” from a guess into a derivation.
Settling causal disagreements. Two people who appear to disagree about an effect often agree once they have agreed on the graph; drawing it relocates the argument to where it actually lives — the assumed structure.

Failure modes and when not to use it

Garbage graph, confident verdict. The identifiability verdict is only as sound as the drawn graph; a wrong arrow or a missing confounder produces a clean-looking answer that is wrong. The mode states its absent-arrow assumptions explicitly and fragility-orders them precisely because the graph is the load-bearing assumption.
The over-adjustment trap. Throwing every variable into the adjustment set is not caution — it is how you condition on a collider or a mediator and introduce bias. The mode’s whole discipline is adjusting for the derived set, not the available one.
Rung confusion. Treating an association result as an intervention answer, or an intervention answer as a counterfactual one, is the most common applied error; the mode locks the rung up front to prevent it.
No effect sizes. The mode answers whether an effect is identifiable and in which direction it runs, not how big it is — magnitude requires data and statistical estimation the mode deliberately does not assume.

When not to reach for it. When the system runs on feedback loops — accumulation, delay, vicious or virtuous cycles — the acyclic apparatus cannot represent it, and the systems-dynamics-causal mode fits. When the task is diagnosing a single past failure rather than reasoning about a general intervention, root-cause-analysis (for a backward chain) or process-tracing (for one evidence-rich historical case) is the right tool. When the causal structure is settled and the live question is which of several competing causal hypotheses the evidence favors, that is a hypothesis problem — route to competing-hypotheses or a Bayesian hypothesis network. And when the disagreement is about which variables even belong in the graph, that is a substantive domain dispute the mode does not adjudicate; it makes the disagreement explicit rather than resolving it.

Root Cause Analysis — the complexity-simple sibling in the same territory: when the failure is a single backward chain to trace rather than a structure of confounders and mediators to map, the fishbone-and-five-whys mode fits.
Systems Dynamics (Causal) — the cyclic counterpart for when the system runs on feedback loops and delays; a DAG is acyclic by construction, so this is the mode the boundary hands off to when loops are central.
Process Tracing — the sibling for reconstructing the exact causal pathway of one specific historical case, where the question is what happened here rather than what would happen if we intervened.
Competing Hypotheses — the hypothesis-evaluation mode to reach for once the causal structure is settled but several rival causal explanations remain alive and must be weighed against the evidence.