← Case Study

Abduction Inspector

Healthcare Statins · Inspect how evidence anchors the latent U terms before any counterfactual intervention. Recommended opening view: Statins → Hospitalization.

Why abduction matters

Population-level causal effects answer "on average, what would happen under intervention?" — but individual-level counterfactuals require something more: the specific, unobserved background factors that made this case's outcome what it was. Abduction recovers those factors from what was actually observed, anchoring each U node to the value consistent with the facts of the case.

Without abduction, a counterfactual query uses population-average noise — which may be badly wrong for any particular individual. With it, you hold the individual's background fixed and ask what would have happened under different circumstances: the same case, different decision. This is the formal engine behind personalised medicine, individual legal liability, insurance coverage disputes, and any question that begins "but for this decision, what would have happened?"

Start here
  1. Open the recommended scenario for this case
  2. Adjust observed evidence or intervention settings
  3. Move to a second tool without losing context
  4. Compare obs() versus do() where available
  5. Inspect paths, blankets, or CPT structure to explain the shift
Abduction setup

This view highlights how an observed fact shifts the latent U nodes. In Pearl's ladder language, this is the anchoring step before a counterfactual intervention is applied.

Latent-node posterior shifts
Latent nodePriorPosteriorΔ
Most affected visible nodes
NodePriorPosteriorΔ
Model coverage

Visible nodes: 8 · Latent nodes: 8 · Total nodes: 16. Latent nodes are hidden by default except where they are the point of the analysis.