Causal Sequence Map¶
Artifact — instantiates Narrative Construction Audit
Visualizes how the story links events into causes, consequences, turning points, background conditions, and uncertainty points.
Stories smuggle their strongest claims into the little word because. Causal Sequence Map is the artifact that draws the story's implied "because"-chain as explicit links between events and then labels each link by what kind of connection it really is — established cause, plausible inference, speculation, mere succession, or background condition that was always present. Its one defining move is that it treats every arrow as a claim requiring a warrant: an arrow is not allowed to exist just because two events sit next to each other in the telling. It says nothing about who the story centers or in what calendar order events fell; it is entirely about the logic of connection — which nodes cause which, which links are load-bearing, where the chain forks, and where an arrow is really a guess wearing the costume of a cause.
Example¶
An airline's account of a runway excursion reads as a clean chain: fatigue led the captain to misjudge the approach, which caused the overrun. Investigators build a Causal Sequence Map before the account is filed. Each event becomes a node; each because becomes a typed arrow. "Fatigue → misjudgment" is drawn but labeled inference — supported by duty-hours data but not by any direct evidence of impairment. "Misjudgment → overrun" is labeled established — the flight-data recorder anchors it. Then the map exposes what the linear story hid: a persistent background condition — a tailwind and a wet runway present the whole time — that the narrative had quietly dropped, and a fork where a late go-around decision could have broken the chain.
The output is not a rival explanation but a picture of where the causal story is solid and where it is a hopeful line. The finding — the fatigue link is the chain's weakest and least anchored arrow — sends investigators back for the crew-rest evidence that would either warrant that arrow or force it to be redrawn as speculation.
How it works¶
The distinguishing procedure is to separate the drawing of the chain from the belief in it. Lay out events as nodes; wherever the story implies causation, draw an arrow — then immediately type it (established, inferred, speculative, or plain succession) and anchor it to the specific evidence that licenses it, leaving the anchor blank where none exists. Add background conditions as standing inputs rather than points on the line, so conditions present throughout are not mistaken for triggers. Mark forks and uncertainty points where the chain could have gone otherwise or where the link is contested. Reading the finished map, the payload is any arrow whose anchor cell is empty: a link the story leans on that nothing supports.
Tuning parameters¶
- Link-type vocabulary — how many kinds of connection you distinguish. A rich set (necessary, sufficient, contributory, enabling) is precise but slow; a coarse set (caused / preceded / conditioned) is fast and legible.
- Anchor strictness — whether every arrow must cite evidence before it may be drawn solid. Strict anchoring catches unwarranted leaps but can stall a map where evidence is genuinely thin.
- Condition depth — how far back you carry standing background conditions. Deeper surfaces systemic causes but risks a map where everything conditions everything.
- Fork tolerance — how many counterfactual branch-points you mark. More forks show contingency; too many dissolve the story into a maze.
When it helps, and when it misleads¶
Its strength is refusing to let chronology or rhetoric masquerade as demonstrated causation: an unlabeled arrow becomes a visible, testable claim, and a background condition can no longer hide inside a linear plot. It is the fastest way to find the link a story cannot actually support.
Its classic misuse is drawing a satisfying chain and then treating the diagram itself as proof — a just-so story rendered as a flowchart, where the elegance of the picture stands in for evidence of the links.[n1] The chain-shaped format also biases toward single-line causation and can under-draw the messy web of contributory causes. The discipline that keeps it honest is to fill the evidence anchors before trusting any arrow, and to treat every empty anchor as an open question rather than an assumed cause.
How it implements the components¶
causal_sequence— the map is the story's causal chain made explicit: typed arrows, forks, and background conditions distinguishing cause from mere succession.evidence_anchor— each arrow carries the specific evidence that licenses it, and an empty anchor flags an unwarranted link.dissent_or_uncertainty_note— contested links and counterfactual fork-points are marked on the map as uncertainty rather than smoothed into a single confident line.
It does not test the calendar order and gaps that expose false sequencing — that is Timeline Review, whose temporal_frame_note this map deliberately sets aside to focus on logical connection — nor cast the parties as focal_actor roles, which is Actor Role Map.
Related¶
- Instantiates: Narrative Construction Audit — supplies the causal-labeling check that keeps a timeline from doing unearned explanatory work.
- Consumes: Timeline Review — the verified chronology on which causal links can honestly be drawn.
- Sibling mechanisms: Actor Role Map · Timeline Review · Selection / Omission Matrix · Narrative Audit Table · Counter-Narrative Workshop · Narrative Red Team · Media Framing Analysis · After-Action Story Review · Evidence-to-Claim Matrix
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: The mechanism diagrams events, causal arrows, background conditions, turning points, evidence anchors, and uncertainty types, so its operative form is a causal sequence representation.
Nearest alternative: Analysis, Modeling & Optimization — The map invites causal scrutiny, but its contribution is externalizing the proposed story rather than computing an inference.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: History & Historiography
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Historical method reconstructs event sequences, background conditions, turning points, and evidentiary uncertainty while distinguishing chronology from causal explanation.
Related originating lineages:
- Literature & Literary Theory — Narrative theory contributes analysis of how stories select turning points and convert temporal succession into causal plot.
- Philosophy — Logic and philosophy of causation contribute the rule that temporal succession alone is not causation and that each causal arrow needs warrant.
Review resolution: The reviewers split between history and literary theory. Historical event-structure analysis explicitly diagrams narrative sequences and requires reasons for causal judgments, while philosophy of history centers evidence, rigor, mechanisms, and constructed narrative. That evidence favors historiography, with narratology and causal logic materially shaping the synthesized map.
Attribution caveat: Narratology is a genuine parallel lineage because the artifact audits a story's implied plot; history is primary because source warrants and causal reconstruction, not narrative form alone, govern whether each link survives.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- Narrative, Event-Structure Analysis, and Causal Interpretation in Historical Sociology
- Stanford Encyclopedia of Philosophy: Philosophy of History
Notes¶
[n1] The phrase just-so story, borrowed from Kipling by Gould and Lewontin, names an explanation that is internally satisfying but constructed after the fact and immune to test. A causal map with every arrow drawn solid and no anchors is a just-so story with better production values. ↩